Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-03 Thread Igor Mammedov
On Wed, 2 Nov 2016 23:54:05 +0800 Xiao Guangrong wrote: > On 11/02/2016 09:56 PM, Igor Mammedov wrote: > > On Sat, 29 Oct 2016 00:35:39 +0800 > > Xiao Guangrong wrote: > > > >> _FIT is required for hotplug support, guest will inquire the updated > >> device info from it if a hotplug event is r

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-03 Thread Igor Mammedov
On Wed, 2 Nov 2016 23:40:56 +0800 Xiao Guangrong wrote: > On 11/02/2016 12:24 AM, Igor Mammedov wrote: > > On Sat, 29 Oct 2016 00:35:39 +0800 > > Xiao Guangrong wrote: > > > >> _FIT is required for hotplug support, guest will inquire the updated > >> device info from it if a hotplug event is r

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-02 Thread Xiao Guangrong
On 11/02/2016 09:56 PM, Igor Mammedov wrote: On Sat, 29 Oct 2016 00:35:39 +0800 Xiao Guangrong wrote: _FIT is required for hotplug support, guest will inquire the updated device info from it if a hotplug event is received As FIT buffer is not completely mapped into guest address space, so a

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-02 Thread Xiao Guangrong
On 11/02/2016 12:41 AM, Stefan Hajnoczi wrote: On Sat, Oct 29, 2016 at 12:35:39AM +0800, Xiao Guangrong wrote: +1) Read FIT + As we only reserved one page for NVDIMM ACPI it is impossible to map the + whole FIT data to guest's address space. This function is used by _FIT + method to read

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-02 Thread Xiao Guangrong
On 11/02/2016 12:24 AM, Igor Mammedov wrote: On Sat, 29 Oct 2016 00:35:39 +0800 Xiao Guangrong wrote: _FIT is required for hotplug support, guest will inquire the updated device info from it if a hotplug event is received As FIT buffer is not completely mapped into guest address space, so a

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-02 Thread Igor Mammedov
On Sat, 29 Oct 2016 00:35:39 +0800 Xiao Guangrong wrote: > _FIT is required for hotplug support, guest will inquire the updated > device info from it if a hotplug event is received > > As FIT buffer is not completely mapped into guest address space, so a > new function, Read FIT whose UUID is UU

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-01 Thread Stefan Hajnoczi
On Sat, Oct 29, 2016 at 12:35:39AM +0800, Xiao Guangrong wrote: > +1) Read FIT > + As we only reserved one page for NVDIMM ACPI it is impossible to map the > + whole FIT data to guest's address space. This function is used by _FIT > + method to read a piece of FIT data from QEMU. > + > + In

Re: [Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-11-01 Thread Igor Mammedov
On Sat, 29 Oct 2016 00:35:39 +0800 Xiao Guangrong wrote: > _FIT is required for hotplug support, guest will inquire the updated > device info from it if a hotplug event is received > > As FIT buffer is not completely mapped into guest address space, so a > new function, Read FIT whose UUID is UU

[Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

2016-10-28 Thread Xiao Guangrong
_FIT is required for hotplug support, guest will inquire the updated device info from it if a hotplug event is received As FIT buffer is not completely mapped into guest address space, so a new function, Read FIT whose UUID is UUID 648B9CF2-CDA1-4312-8AD9-49C4AF32BD62, handle 0x1, function ind