From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC PATCH qemu 2/4] memory: Prepare for shared flat views
Date: Sat, 9 Sep 2017 17:18:46 +1000 [thread overview]
Message-ID: <20170909071846.GU2735@umbus.fritz.box> (raw)
In-Reply-To: <20170907092010.3605-3-aik@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Thu, Sep 07, 2017 at 07:20:08PM +1000, Alexey Kardashevskiy wrote:
> We are going to share flat views and dispatch trees between address
> spaces. This moves bits around but no change in behaviour is expected
> here. The following patch will implement sharing.
>
> This switches from AddressSpace to AddressSpaceDispatch as in many
> places this is what is used actually. Also, since multiple address
> spaces will be sharing a flat view, MemoryRegionSection cannot store
> the address space pointer, this changes it to AddressSpaceDispatch
> as well. As a not very obvious result, IOMMUTLBEntry also switched
> from AddressSpace to AddressSpaceDispatch to make
> address_space_get_iotlb_entry() work.
So, mostly this seems to be exposing AddressSpaceDispatch in more
places. It's not obvious to me why that's useful.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-09 7:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 9:20 [Qemu-devel] [RFC PATCH qemu 0/4] memory: Reduce memory use Alexey Kardashevskiy
2017-09-07 9:20 ` [Qemu-devel] [RFC PATCH qemu 1/4] memory: Postpone flatview and dispatch tree building till all devices are added Alexey Kardashevskiy
2017-09-07 9:30 ` Peter Maydell
2017-09-07 14:27 ` Alexey Kardashevskiy
2017-09-07 14:30 ` Peter Maydell
2017-09-08 6:21 ` Alexey Kardashevskiy
2017-09-07 9:20 ` [Qemu-devel] [RFC PATCH qemu 2/4] memory: Prepare for shared flat views Alexey Kardashevskiy
2017-09-09 7:18 ` David Gibson [this message]
2017-09-10 9:17 ` Alexey Kardashevskiy
2017-09-07 9:20 ` [Qemu-devel] [RFC PATCH qemu 3/4] memory: Share flat views and dispatch trees between address spaces Alexey Kardashevskiy
2017-09-07 20:53 ` Philippe Mathieu-Daudé
2017-09-07 22:18 ` Alexey Kardashevskiy
2017-09-11 7:40 ` Paolo Bonzini
2017-09-11 9:06 ` Alexey Kardashevskiy
2017-09-11 9:37 ` Paolo Bonzini
2017-09-11 12:08 ` Alexey Kardashevskiy
2017-09-11 15:30 ` Paolo Bonzini
2017-09-12 5:55 ` Alexey Kardashevskiy
2017-09-12 7:12 ` Paolo Bonzini
2017-09-12 9:47 ` Alexey Kardashevskiy
2017-09-07 9:20 ` [Qemu-devel] [RFC PATCH qemu 4/4] memory: Add flat views to HMP "info mtree" Alexey Kardashevskiy
2017-09-07 9:51 ` [Qemu-devel] [RFC PATCH qemu 0/4] memory: Reduce memory use Dr. David Alan Gilbert
2017-09-07 10:08 ` David Gibson
2017-09-07 14:44 ` Alexey Kardashevskiy
2017-09-07 14:54 ` Dr. David Alan Gilbert
2017-09-08 2:08 ` Alexey Kardashevskiy
2017-09-08 4:04 ` Alexey Kardashevskiy
2017-09-08 11:12 ` Dr. David Alan Gilbert
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=20170909071846.GU2735@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).