Re: [Qemu-devel] [PATCH v2 08/18] nvdimm: init backend memory mapping and config data area

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 07/09/2015 16:11, Igor Mammedov wrote:
> 
> here is common concepts that could be reused.
>   - on physical system both DIMM and NVDIMM devices use
>     the same slots. We could share QEMU's '-m slots' option between
>     both devices. An alternative to not sharing would be to introduce
>     '-machine nvdimm_slots' option.
>     And yes, we need to know number of NVDIMMs to describe
>     them all in ACPI table (taking in amount future hotplug
>     include in this possible NVDIMM devices)
>     I'd go the same way as on real hardware on make them share the same slots.
>   - they share the same physical address space and limits
>     on how much memory system can handle. So I'd suggest sharing existing
>     '-m maxmem' option and reuse hotplug_memory address space.

I agree, and the slot number also provide a nice way to build a
consistent memory region name across multiple systems.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux