Re: [Qemu-devel] [PATCH v2 06/11] nvdimm acpi: initialize the resource used by NVDIMM ACPI

[Michael S. Tsirkin]

On Thu, Feb 18, 2016 at 12:03:36PM +0800, Xiao Guangrong wrote:
> 
> 
> On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
> >On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
> >>>>>As for the rest could that commands go via MMIO that we usually
> >>>>>use for control path?
> >>>>
> >>>>So both input data and output data go through single MMIO, we need to
> >>>>introduce a protocol to pass these data, that is complex?
> >>>>
> >>>>And is any MMIO we can reuse (more complexer？) or we should allocate this
> >>>>MMIO page （the old question - where to allocated?）?
> >>>Maybe you could reuse/extend memhotplug IO interface,
> >>>or alternatively as Michael suggested add a vendor specific PCI_Config,
> >>>I'd suggest PM device for that (hw/acpi/[piix4.c|ihc9.c])
> >>>which I like even better since you won't need to care about which ports
> >>>to allocate at all.
> >>
> >>Well, if Michael does not object, i will do it in the next version. :)
> >
> >Sorry, the thread's so long by now that I'm no longer sure what does "it" 
> >refer to.
> 
> Never mind i saw you were busy on other loops.
> 
> "It" means the suggestion of Igor that "map each label area right after each
> NVDIMM's data memory" so we do not emulate it in QEMU and is good for the 
> performance
> of label these are the points i like. However it also brings 
> complexity/limitation for
> later DSM commands supports since both dsm input & output need to go through 
> single MMIO.
> 
> Your idea?

I think mapping right after data is problematic since it might
use 1G of address space if alignment is used (and alignment is
good for performance, so we typically do want people to use it).
Given you will add more DSM commands anyway,
I don't see a reason not to pass label data this way too.

I don't care much how are commands passed exactly.
Igor, do you have a preference or if it's not MMIO beyong DIMM
then you don't care?

-- 
MST