[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 4/4] hvmloader: add support to load extra ACPI tables from qemu
>>> On 20.01.16 at 12:04, <haozhong.zhang@xxxxxxxxx> wrote: > On 01/20/16 01:46, Jan Beulich wrote: >> >>> On 20.01.16 at 06:31, <haozhong.zhang@xxxxxxxxx> wrote: >> > Secondly, the driver implements a convenient block device interface to >> > let software access areas where NVDIMM devices are mapped. The >> > existing vNVDIMM implementation in QEMU uses this interface. >> > >> > As Linux NVDIMM driver has already done above, why do we bother to >> > reimplement them in Xen? >> >> See above; a possibility is that we may need a split model (block >> layer parts on Dom0, "normal memory" parts in the hypervisor. >> Iirc the split is being determined by firmware, and hence set in >> stone by the time OS (or hypervisor) boot starts. > > For the "normal memory" parts, do you mean parts that map the host > NVDIMM device's address space range to the guest? I'm going to > implement that part in hypervisor and expose it as a hypercall so that > it can be used by QEMU. To answer this I need to have my understanding of the partitioning being done by firmware confirmed: If that's the case, then "normal" means the part that doesn't get exposed as a block device (SSD). In any event there's no correlation to guest exposure here. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |