All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhong Yang <yang.zhong@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: xiaoguangrong.eric@gmail.com, ehabkost@redhat.com,
	alex.williamson@redhat.com, anthony.xu@intel.com,
	yang.zhong@intel.com
Subject: Re: [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file
Date: Wed, 18 Oct 2017 17:56:42 +0800	[thread overview]
Message-ID: <20171018095642.GA5442@yangzhon-Virtual> (raw)
In-Reply-To: <1ecf42be-b0e6-43a1-8747-c94425ded449@redhat.com>

On Wed, Oct 18, 2017 at 11:48:11AM +0200, Paolo Bonzini wrote:
> On 18/10/2017 07:57, Zhong Yang wrote:
> >   Your suggestion can avoid DMA target to nvdimm if the nvdimm memory region
> >   was skipped during VFIO hotplug. It is valuable to try this solution. by the
> >   way, please share me some clue for PCI address space related with memory region,
> >   below address_space_mem is right?  Many thanks!
> > 
> >   static void pci_bus_init(PCIBus *bus, DeviceState *parent,
> >                          MemoryRegion *address_space_mem,
> >                          MemoryRegion *address_space_io,
> >                          uint8_t devfn_min)  
> 
> Yes.  You would have to add the region directly to the CPU address
> space, and not to address_space_memory (which is included in both the
> CPU and PCI address spaces).
> 
> Paolo
  
  Thanks Paolo for your great help! I will try this solution in next week, thanks again.

  Regards,

  Yang

  reply	other threads:[~2017-10-18  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  8:56 [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file Yang Zhong
2017-10-16  8:56 ` [Qemu-devel] [PATCH 1/2] hostmem-file: Add "nopin" option for memory-backend-file Yang Zhong
2017-10-16  8:56 ` [Qemu-devel] [PATCH 2/2] nvdimm: Add "nopin" for related documents Yang Zhong
2017-10-16 10:20 ` [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file Xiao Guangrong
2017-10-16 11:58   ` Paolo Bonzini
2017-10-18  5:57     ` Zhong Yang
2017-10-18  9:48       ` Paolo Bonzini
2017-10-18  9:56         ` Zhong Yang [this message]
2017-10-18  5:34   ` Zhong Yang
2017-10-16 15:47 ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171018095642.GA5442@yangzhon-Virtual \
    --to=yang.zhong@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=anthony.xu@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoguangrong.eric@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.