search for: bootmem

...0.000000] #3 [0001933000 - 0001976000] XEN START INFO [ 0.000000] #4 [0000010000 - 0000012000] TRAMPOLINE [ 0.000000] #5 [0000012000 - 0000040000] PGTABLE [ 0.000000] #6 [0001912600 - 0001917600] NODE_DATA [ 0.000000] #7 [0001917600 - 0001918600] BOOTMEM [ 0.000000] #8 [0001918600 - 0001918618] BOOTMEM [ 0.000000] #9 [0001919000 - 000191a000] BOOTMEM [ 0.000000] #10 [000191a000 - 000191b000] BOOTMEM [ 0.000000] #11 [000191b000 - 000191c000] BOOTMEM [ 0.000000] #12 [0002200000 - 00023c0000]...

...0.000000] #3 [0001933000 - 0001976000] XEN START INFO [ 0.000000] #4 [0000010000 - 0000012000] TRAMPOLINE [ 0.000000] #5 [0000012000 - 0000040000] PGTABLE [ 0.000000] #6 [0001912600 - 0001917600] NODE_DATA [ 0.000000] #7 [0001917600 - 0001918600] BOOTMEM [ 0.000000] #8 [0001918600 - 0001918618] BOOTMEM [ 0.000000] #9 [0001919000 - 000191a000] BOOTMEM [ 0.000000] #10 [000191a000 - 000191b000] BOOTMEM [ 0.000000] #11 [000191b000 - 000191c000] BOOTMEM [ 0.000000] #12 [0002200000 - 00023c0000]...

...0.000000]?? #8 [00000f89a0 - 00000f8a90]??? MP-table mpc [??? 0.000000]?? #9 [0000010000 - 0000011000]????? TRAMPOLINE [??? 0.000000]?? #10 [0000011000 - 0000015000]???? ACPI WAKEUP [??? 0.000000]?? #11 [0000015000 - 0000016000]???????? PGTABLE [??? 0.000000]?? #12 [0001000000 - 0001001000]???????? BOOTMEM [??? 0.000000]?? #13 [0001001000 - 00013e9000]???????? BOOTMEM [??? 0.000000]?? #14 [00013e9000 - 00013e9004]???????? BOOTMEM [??? 0.000000]?? #15 [00013e9040 - 00013e9100]???????? BOOTMEM [??? 0.000000]?? #16 [00013e9100 - 00013e9130]???????? BOOTMEM [??? 0.000000]?? #17 [00013e9140 - 00013ea940]?...

...f780] BIOS reserved #8 [00000e3e10 - 00000e3f7c] MP-table mpc #9 [0000010000 - 0000012000] TRAMPOLINE #10 [0000012000 - 0000014000] PGTABLE #11 [0000014000 - 0000015000] PGTABLE #12 [0100000000 - 0100005000] NODE_DATA #13 [00017a8180 - 00017a9180] BOOTMEM #14 [00017a7940 - 00017a7c40] BOOTMEM #15 [0100005000 - 0100006000] BOOTMEM #16 [0100006000 - 0100007000] BOOTMEM #17 [0100200000 - 0103c00000] MEMMAP 0 #18 [00017a7c40 - 00017a7dc0] BOOTMEM #19 [00017a9180 - 00017c1180] BOOTMEM #20 [0001...

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

...Oct 8 02:35:04 (none) kernel: #10 [0000011000 - 0000015000] ACPI WAKEUP Oct 8 02:35:04 (none) kernel: #11 [0000015000 - 0000016000] PGTABLE Oct 8 02:35:04 (none) kernel: #12 [000157a000 - 0003d98000] NEW RAMDISK Oct 8 02:35:04 (none) kernel: #13 [0003d98000 - 0003d99000] BOOTMEM Oct 8 02:35:04 (none) kernel: #14 [0003d99000 - 0004589000] BOOTMEM Oct 8 02:35:04 (none) kernel: #15 [00015721c0 - 00015721c4] BOOTMEM Oct 8 02:35:04 (none) kernel: #16 [0001572200 - 00015722c0] BOOTMEM Oct 8 02:35:04 (none) kernel: #17 [00015722c0 - 0001572314]...

On 28.07.20 15:48, Baoquan He wrote: > On 06/30/20 at 04:26pm, David Hildenbrand wrote: >> Let's move the split comment regarding bootmem allocations and memory >> holes, especially in the context of ZONE_MOVABLE, to the PageReserved() >> check. >> >> Cc: Andrew Morton <akpm at linux-foundation.org> >> Cc: Michal Hocko <mhocko at suse.com> >> Cc: Michael S. Tsirkin <mst at redhat.com...

On 29.07.20 12:47, Baoquan He wrote: > On 07/28/20 at 04:07pm, David Hildenbrand wrote: >> On 28.07.20 15:48, Baoquan He wrote: >>> On 06/30/20 at 04:26pm, David Hildenbrand wrote: >>>> Let's move the split comment regarding bootmem allocations and memory >>>> holes, especially in the context of ZONE_MOVABLE, to the PageReserved() >>>> check. >>>> >>>> Cc: Andrew Morton <akpm at linux-foundation.org> >>>> Cc: Michal Hocko <mhocko at suse.com> >>>&...

I'm running CentOS 5.1 with all updates, and the xen kernel. For some reason the OS is not seeing the full amount of ram. #uname -a Linux CentOS-VM-A 2.6.18-53.1.21.el5xen #1 SMP Tue May 20 10:03:27 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux # free total used free shared buffers cached Mem: 6104064 3445136 2658928 0 1412236

Hi Folks, I need some large chunk of physical memory, so I allocate it early using alloc_bootmem_low_pages and use it later (akin to bigphysarea patch). The trouble I am having is the following. Suppose the virtual address for the memory area is 0xc14d6000. After xen_create_contiguous_region call, I do a virt_to_bus and the bus address comes out to be 0x18000000. So far so good. However, l...

...0.000000] init_memory_mapping [ 0.000000] last_map_addr: 1e0000000 end: 1e0000000 [ 0.000000] RAMDISK: 009b9000 - 08cc2000 [ 0.000000] DMI not present or invalid. [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-00000001e0000000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000001e0000000 [ 0.000000] NODE_DATA [0000000000001000 - 0000000000005fff] [ 0.000000] bootmap [0000000000008000 - 0000000000043fff] pages 3c [ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 01e0000000] [ 0.000000] #0 [0000000000 - 0...

Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising for users (especially, if onlining suddenly fails). Let's support partially plugged memory

Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising for users (especially, if onlining suddenly fails). Let's support partially plugged memory

On 10/20/2016 11:24 PM, Liang Li wrote: > Expose the function to get the max pfn, so it can be used in the > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > is not enough, if the device driver is built to a module, directly > refer the max_pfn lead to build failed. I'm not sure the rest of the set is worth reviewing. I think a lot of it will change pretty fundamentally once you have those improved data structures in place.

On 10/20/2016 11:24 PM, Liang Li wrote: > Expose the function to get the max pfn, so it can be used in the > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > is not enough, if the device driver is built to a module, directly > refer the max_pfn lead to build failed. I'm not sure the rest of the set is worth reviewing. I think a lot of it will change pretty fundamentally once you have those improved data structures in place.

...t __pv_init_lock_hash(void) > >>+{ > >>+ int pv_hash_size = 4 * num_possible_cpus(); > >>+ > >>+ if (pv_hash_size< (1U<< LFSR_MIN_BITS)) > >>+ pv_hash_size = (1U<< LFSR_MIN_BITS); > >>+ /* > >>+ * Allocate space from bootmem which should be page-size aligned > >>+ * and hence cacheline aligned. > >>+ */ > >>+ pv_lock_hash = alloc_large_system_hash("PV qspinlock", > >>+ sizeof(struct pv_hash_bucket), > >>+ pv_hash_size, 0, HASH_EARLY, > &g...

...t __pv_init_lock_hash(void) > >>+{ > >>+ int pv_hash_size = 4 * num_possible_cpus(); > >>+ > >>+ if (pv_hash_size< (1U<< LFSR_MIN_BITS)) > >>+ pv_hash_size = (1U<< LFSR_MIN_BITS); > >>+ /* > >>+ * Allocate space from bootmem which should be page-size aligned > >>+ * and hence cacheline aligned. > >>+ */ > >>+ pv_lock_hash = alloc_large_system_hash("PV qspinlock", > >>+ sizeof(struct pv_hash_bucket), > >>+ pv_hash_size, 0, HASH_EARLY, > &g...

...e use many Debian 6.0 Xen Server on different HP Hardware - never seen before... I found some difference in the dmesg output on the two servers: on the non working DL585: [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000180000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000180000000 [ 0.000000] NODE_DATA [0000000000008000 - 000000000000ffff] [ 0.000000] bootmap [0000000000010000 - 000000000003ffff] pages 30 [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0180000000] [ 0.000000] #0 [0000000000 - 0...

...E_SC3 0x00000001 DELL 0x00000001) @ 0x00000000cfb6a9a4 ACPI: TCPA (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000cfb834bc ACPI: DSDT (v001 DELL PE_SC3 0x00000001 INTL 0x20050624) @ 0x0000000000000000 No NUMA configuration found Faking a node at 0000000000000000-0000000230000000 Bootmem setup node 0 0000000000000000-0000000230000000 Memory for crash kernel (0x0 to 0x0) notwithin permissible range ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ any input about this issue? -- Your search - madunix - did not match any documents. -------------- next part...

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >