From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Yongji Xie <xyjxie@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, zhong@linux.vnet.ibm.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, gwshan@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] vfio: Add support for mmapping sub-page MMIO BARs
Date: Fri, 30 Sep 2016 18:05:55 +0200 [thread overview]
Message-ID: <68a8ddc4-6d43-9e81-f475-e12f6d4513d2@redhat.com> (raw)
In-Reply-To: <20160913165504.3e1b9707@t450s.home>
On 14/09/2016 00:55, Alex Williamson wrote:
> Paolo, as the reigning memory API expert, do you see any issues with
> this? Expanding the size of a container MemoryRegion and the contained
> mmap'd subregion and manipulating priorities so that we don't interfere
> with other MemoryRegions.
I guess it's fine if you are okay with maintaining it.
memory_region_set_size exists, might as well use it. :)
What I'm worried about, is what happens if two such regions end up in
the same guest page. Then the two priorities conflict.
Paolo
next prev parent reply other threads:[~2016-09-30 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 11:05 [Qemu-devel] [PATCH v2] vfio: Add support for mmapping sub-page MMIO BARs Yongji Xie
2016-08-11 11:09 ` no-reply
2016-09-05 10:25 ` Yongji Xie
2016-09-13 22:55 ` Alex Williamson
2016-09-14 5:04 ` Yongji Xie
2016-09-30 16:05 ` Paolo Bonzini [this message]
2016-10-04 6:57 ` Yongji Xie
-- strict thread matches above, loose matches on Subject: below --
2016-09-07 0:48 [Qemu-devel] [PATCH] hmp: Improve 'info mtree' with optional parm for mapinfo Thorsten Kohfeldt
2016-09-15 9:52 ` Paolo Bonzini
2016-09-20 0:16 ` Thorsten Kohfeldt
2016-09-20 0:51 ` Laszlo Ersek
2016-09-22 19:43 ` [Qemu-devel] [PATCH v2] vfio: Add support for mmapping sub-page MMIO BARs Thorsten Kohfeldt
2016-09-30 4:00 Thorsten Kohfeldt
2016-09-30 15:07 ` 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=68a8ddc4-6d43-9e81-f475-e12f6d4513d2@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=xyjxie@linux.vnet.ibm.com \
--cc=zhong@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).