From: Paolo Bonzini <pbonzini@redhat.com>
To: CheneyLin <linzc@zju.edu.cn>, qemu-devel@nongnu.org
Cc: aik@ozlabs.ru
Subject: Re: [Qemu-devel] question about share flatviews
Date: Mon, 15 Jan 2018 10:29:00 +0100 [thread overview]
Message-ID: <be21e8c9-651d-a11c-fffa-53e47c5abc3f@redhat.com> (raw)
In-Reply-To: <2f3d36f8.1ce36.160f49d0471.Coremail.linzc@zju.edu.cn>
On 14/01/2018 13:20, CheneyLin wrote:
> I'm wondering why we have to shares flatviews between different ASes. In
> my opinion, arch like x86 only have two ASes(memory AS and io AS), each
> AS is related with only one flatview. Their ASes are definitely different.
Every PCI device has its own AddressSpace. A PCI device's is either the
same as the memory AS or the same as the empty AS, hence sharing the
FlatView can provide substantial memory usage improvements.
Paolo
prev parent reply other threads:[~2018-01-15 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 12:20 [Qemu-devel] question about share flatviews CheneyLin
2018-01-15 3:37 ` Alexey Kardashevskiy
2018-01-15 9:29 ` Paolo Bonzini [this message]
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=be21e8c9-651d-a11c-fffa-53e47c5abc3f@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=linzc@zju.edu.cn \
--cc=qemu-devel@nongnu.org \
/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).