2019-05-27 08:55:01 +02:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-30 15:09:49 -07:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
2019-10-14 20:31:03 +02:00
|
|
|
|
2024-05-05 19:06:24 +03:00
|
|
|
|
2024-03-21 09:36:23 -07:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2022-03-29 17:27:33 +02:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2011-12-02 12:26:23 +00:00
|
|
|
|
2020-01-14 17:54:00 +00:00
|
|
|
|
2020-08-18 19:11:26 -03:00
|
|
|
|
2021-09-13 17:17:26 +02:00
|
|
|
|
2022-05-16 12:44:22 +05:30
|
|
|
|
2024-10-23 19:27:06 +03:00
|
|
|
|
2022-06-11 18:55:15 +02:00
|
|
|
|
2023-09-25 20:31:21 +02:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2026-03-01 00:17:59 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-29 09:59:59 +00:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2024-04-22 21:52:31 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
2023-09-22 10:04:58 +02:00
|
|
|
|
|
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
|
|
|
|
|
2023-09-22 10:04:58 +02:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2005-10-28 17:46:18 -07:00
|
|
|
|
2008-12-18 19:13:51 +00:00
|
|
|
|
|
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
|
|
|
|
|
2023-09-22 10:04:58 +02:00
|
|
|
|
2005-09-26 16:04:21 +10:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2021-02-19 17:56:48 +01:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2006-06-27 02:53:30 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-29 16:13:55 +10:00
|
|
|
|
2006-06-27 02:53:30 -07:00
|
|
|
|
|
|
|
|
|
2020-04-10 14:33:32 -07:00
|
|
|
|
|
|
|
|
|
2016-07-05 15:07:54 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
|
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2016-02-09 13:32:42 +10:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2006-03-21 23:00:05 -08:00
|
|
|
|
2020-11-11 15:53:18 +01:00
|
|
|
|
mm/memory_hotplug: add pgprot_t to mhp_params
devm_memremap_pages() is currently used by the PCI P2PDMA code to create
struct page mappings for IO memory. At present, these mappings are
created with PAGE_KERNEL which implies setting the PAT bits to be WB.
However, on x86, an mtrr register will typically override this and force
the cache type to be UC-. In the case firmware doesn't set this
register it is effectively WB and will typically result in a machine
check exception when it's accessed.
Other arches are not currently likely to function correctly seeing they
don't have any MTRR registers to fall back on.
To solve this, provide a way to specify the pgprot value explicitly to
arch_add_memory().
Of the arches that support MEMORY_HOTPLUG: x86_64, and arm64 need a
simple change to pass the pgprot_t down to their respective functions
which set up the page tables. For x86_32, set the page tables
explicitly using _set_memory_prot() (seeing they are already mapped).
For ia64, s390 and sh, reject anything but PAGE_KERNEL settings -- this
should be fine, for now, seeing these architectures don't support
ZONE_DEVICE.
A check in __add_pages() is also added to ensure the pgprot parameter
was set for all arches.
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: David Hildenbrand <david@redhat.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Acked-by: Dan Williams <dan.j.williams@intel.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Eric Badger <ebadger@gigaio.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Will Deacon <will@kernel.org>
Link: http://lkml.kernel.org/r/20200306170846.9333-7-logang@deltatee.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-04-10 14:33:36 -07:00
|
|
|
|
|
|
|
|
|
2020-11-11 15:53:18 +01:00
|
|
|
|
2016-02-09 13:32:42 +10:00
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
2016-02-09 13:32:42 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
2014-01-27 10:54:06 -06:00
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
2014-10-14 22:17:47 +11:00
|
|
|
|
|
|
|
|
|
2019-11-04 13:32:57 +11:00
|
|
|
|
2020-11-11 15:53:18 +01:00
|
|
|
|
2014-10-14 22:17:47 +11:00
|
|
|
|
2020-11-11 15:53:18 +01:00
|
|
|
|
2020-11-11 15:53:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-14 22:17:47 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
2022-06-29 10:39:25 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-13 17:21:26 -07:00
|
|
|
|
2020-04-10 14:33:21 -07:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-09 13:32:42 +10:00
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-29 10:39:25 +05:30
|
|
|
|
2020-11-11 15:53:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-31 13:37:12 +11:00
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
mm/sparse-vmemmap: pass @pgmap argument to memory deactivation paths
Currently, the memory hot-remove call chain -- arch_remove_memory(),
__remove_pages(), sparse_remove_section() and section_deactivate() -- does
not carry the struct dev_pagemap pointer. This prevents the lower levels
from knowing whether the section was originally populated with vmemmap
optimizations (e.g., DAX with vmemmap optimization enabled).
Without this information, we cannot call vmemmap_can_optimize() to
determine if the vmemmap pages were optimized. As a result, the vmemmap
page accounting during teardown will mistakenly assume a non-optimized
allocation, leading to incorrect memmap statistics.
To lay the groundwork for fixing the vmemmap page accounting, we need to
pass the @pgmap pointer down to the deactivation location. Plumb the
@pgmap argument through the APIs of arch_remove_memory(), __remove_pages()
and sparse_remove_section(), mirroring the corresponding *_activate()
paths.
Link: https://lore.kernel.org/20260428081855.1249045-4-songmuchun@bytedance.com
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Acked-by: Liam R. Howlett <liam@infradead.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: Joao Martins <joao.m.martins@oracle.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2026-04-28 16:18:52 +08:00
|
|
|
|
|
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mm/sparse-vmemmap: pass @pgmap argument to memory deactivation paths
Currently, the memory hot-remove call chain -- arch_remove_memory(),
__remove_pages(), sparse_remove_section() and section_deactivate() -- does
not carry the struct dev_pagemap pointer. This prevents the lower levels
from knowing whether the section was originally populated with vmemmap
optimizations (e.g., DAX with vmemmap optimization enabled).
Without this information, we cannot call vmemmap_can_optimize() to
determine if the vmemmap pages were optimized. As a result, the vmemmap
page accounting during teardown will mistakenly assume a non-optimized
allocation, leading to incorrect memmap statistics.
To lay the groundwork for fixing the vmemmap page accounting, we need to
pass the @pgmap pointer down to the deactivation location. Plumb the
@pgmap argument through the APIs of arch_remove_memory(), __remove_pages()
and sparse_remove_section(), mirroring the corresponding *_activate()
paths.
Link: https://lore.kernel.org/20260428081855.1249045-4-songmuchun@bytedance.com
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Acked-by: Liam R. Howlett <liam@infradead.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: Joao Martins <joao.m.martins@oracle.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2026-04-28 16:18:52 +08:00
|
|
|
|
2020-11-11 15:53:17 +01:00
|
|
|
|
2013-02-22 16:32:58 -08:00
|
|
|
|
|
|
|
|
|
2008-02-05 00:10:18 -08:00
|
|
|
|
2021-06-28 19:43:01 -07:00
|
|
|
|
2018-02-14 01:08:16 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
2010-07-12 14:36:09 +10:00
|
|
|
|
2014-09-17 22:15:33 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
2008-04-16 05:52:22 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
2013-01-09 12:40:18 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-14 15:28:02 -07:00
|
|
|
|
2018-02-14 01:08:16 +10:00
|
|
|
|
2006-09-27 01:49:49 -07:00
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-13 16:58:03 -07:00
|
|
|
|
|
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
2020-10-13 16:58:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
2020-10-13 16:58:03 -07:00
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
|
|
|
|
|
2021-06-28 19:43:01 -07:00
|
|
|
|
2014-09-18 14:05:02 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
2016-05-11 19:22:18 +10:00
|
|
|
|
2018-12-16 17:53:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-11 10:09:35 +03:00
|
|
|
|
2019-10-14 20:31:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-11 19:22:18 +10:00
|
|
|
|
2026-01-11 10:20:49 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-08 18:40:42 -05:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-04 18:44:19 +00:00
|
|
|
|
2010-07-12 14:36:09 +10:00
|
|
|
|
2024-08-11 10:09:35 +03:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
2019-11-28 07:59:22 +00:00
|
|
|
|
|
|
|
|
|
2008-04-23 23:05:20 +10:00
|
|
|
|
|
|
|
|
|
2018-10-09 13:51:45 +00:00
|
|
|
|
2008-04-23 23:05:20 +10:00
|
|
|
|
2018-10-09 13:51:45 +00:00
|
|
|
|
2008-04-23 23:05:20 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
2011-07-04 18:44:19 +00:00
|
|
|
|
2008-07-31 13:51:42 +10:00
|
|
|
|
2006-04-12 15:25:01 -05:00
|
|
|
|
2008-07-10 01:09:23 +10:00
|
|
|
|
2014-08-08 18:40:42 -05:00
|
|
|
|
2019-10-14 20:31:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-11 10:09:35 +03:00
|
|
|
|
|
|
|
|
|
2007-05-08 19:25:00 +10:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
2025-03-13 15:50:02 +02:00
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
2026-03-01 00:17:59 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-11 19:22:38 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-16 13:16:25 +00:00
|
|
|
|
2019-12-04 14:35:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-28 13:36:57 +02:00
|
|
|
|
2010-03-16 13:16:25 +00:00
|
|
|
|
|
|
|
|
|
2020-01-14 17:54:00 +00:00
|
|
|
|
|
|
|
|
|
2022-09-19 19:01:38 +02:00
|
|
|
|
2011-06-28 14:54:47 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-10-06 12:23:33 +10:00
|
|
|
|
|
|
|
|
|
2011-06-18 07:36:39 +00:00
|
|
|
|
|
|
|
|
|
2011-06-18 07:36:40 +00:00
|
|
|
|
2017-07-14 16:51:23 +10:00
|
|
|
|
2013-04-29 15:06:47 -07:00
|
|
|
|
2022-05-16 12:44:22 +05:30
|
|
|
|
2011-06-18 07:36:39 +00:00
|
|
|
|
|
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-09-15 11:39:36 +02:00
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
2020-10-13 16:58:08 -07:00
|
|
|
|
|
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
2020-10-13 16:58:08 -07:00
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
|
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-13 16:58:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 21:57:22 +01:00
|
|
|
|
powerpc: insert System RAM resource to prevent crashkernel conflict
The next patch in the series with title "powerpc/crash: use generic
crashkernel reservation" enables powerpc to use generic crashkernel
reservation instead of custom implementation. This leads to exporting of
`Crash Kernel` memory to iomem_resource (/proc/iomem) via
insert_crashkernel_resources():kernel/crash_reserve.c or at another place
in the same file if HAVE_ARCH_ADD_CRASH_RES_TO_IOMEM_EARLY is set.
The add_system_ram_resources():arch/powerpc/mm/mem.c adds `System RAM` to
iomem_resource using request_resource(). This creates a conflict with
`Crash Kernel`, which is added by the generic crashkernel reservation
code. As a result, the kernel ultimately fails to add `System RAM` to
iomem_resource. Consequently, it does not appear in /proc/iomem.
There are multiple approches tried to avoid this:
1. Don't add Crash Kernel to iomem_resource:
- This has two issues.
First, it requires adding an architecture-specific hook in the
generic code. There are already two code paths to choose when to
add `Crash Kernel` to iomem_resource. This adds one more code path
to skip it.
Second, what if `Crash Kernel` is required in /proc/iomem in the
future? Many architectures do export it.
2. Don't add `System RAM` to iomem_resource by reverting commit
c40dd2f766440 ("powerpc: Add System RAM to /proc/iomem"):
- It's not ideal to export `System RAM` via /proc/iomem, but since
it already done ealier and userspace tools like kdump and
kdump-utils rely on `System RAM` from /proc/iomem, removing it
will break userspace.
3. Add Crash Kernel along with System RAM to /proc/iomem:
This patch takes the third approach by updating add_system_ram_resources()
to use insert_resource() instead of the request_resource() API to add the
`System RAM` resource to iomem_resource. insert_resource() allows
inserting resources even if they overlap with existing ones. Since `Crash
Kernel` and `System RAM` resources are added to iomem_resource early in
the boot, any other conflict is not expected.
With the changes introduced here and in the next patch, "powerpc/crash:
use generic crashkernel reservation," /proc/iomem now exports `System RAM`
and `Crash Kernel` as shown below:
$ cat /proc/iomem
00000000-3ffffffff : System RAM
10000000-4fffffff : Crash kernel
The kdump script is capable of handling `System RAM` and `Crash Kernel` in
the above format. The same format is used in other architectures.
Link: https://lkml.kernel.org/r/20250131113830.925179-7-sourabhjain@linux.ibm.com
Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: Baoquan he <bhe@redhat.com>
Cc: Hari Bathini <hbathini@linux.ibm.com>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2025-01-31 17:08:29 +05:30
|
|
|
|
2011-11-02 14:56:12 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-30 09:19:17 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-21 21:45:31 +05:30
|
|
|
|
|
|
|
|
|
2015-04-17 16:17:14 -05:00
|
|
|
|
2011-08-30 09:19:17 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-01 10:46:52 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-05 19:06:24 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-20 19:23:55 +02:00
|
|
|
|
2024-08-20 19:23:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-05 19:06:24 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-20 19:23:51 +02:00
|
|
|
|
|
|
|
|
|
2024-05-05 19:06:24 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|