From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] directory hierarchy
Date: Thu, 20 Sep 2012 14:31:36 +0300 [thread overview]
Message-ID: <505AFE98.10906@redhat.com> (raw)
In-Reply-To: <CAAu8pHs2TJqcivNipefx-RmbJ=bvM22s9DuvDZ77CbF6H5otFA@mail.gmail.com>
On 09/19/2012 10:57 PM, Blue Swirl wrote:
> On Wed, Sep 19, 2012 at 12:54 PM, Avi Kivity <avi@redhat.com> wrote:
>> On 09/14/2012 10:51 PM, Blue Swirl wrote:
>>>>
>>>> exec:
>>>
>>> These files need cleanup so that TCG code gets into tcg/. Maybe also
>>> TB and CPUTLB handling.
>>
>> Some of that could be done by adding a separate MemoryListener for tcg.
>
> But the TBs and CPUTLB are based on virtual mappings, it would mean
> that MMU maps would have to be modeled using memory API. Is that fast
> enough?
No. The memory API is designed to be fast on reads at the expense of
being slow on writes, and this will get worse as rcu is added.
I meant that the various calls to invalidate tcg-specific caches can use
a tcg-specific MemoryListener.
> This could have nice cleanup effects though and for example enable
> generic 'info vmtree' to discover VA->PA mappings for any target
> instead of current MMU table walkers.
How? That's in a hardware defined format that's completely invisible to
the memory API.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-20 11:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 13:17 [Qemu-devel] directory hierarchy Paolo Bonzini
2012-09-14 13:36 ` Peter Maydell
2012-09-14 13:53 ` Paolo Bonzini
2012-09-16 14:40 ` Anthony Liguori
2012-09-17 7:47 ` Paolo Bonzini
2012-09-14 13:44 ` Luiz Capitulino
2012-09-14 14:03 ` Paolo Bonzini
2012-09-14 13:47 ` Daniel P. Berrange
2012-09-14 13:57 ` Paolo Bonzini
2012-09-14 13:48 ` Peter Maydell
2012-09-14 13:55 ` Paolo Bonzini
2012-09-14 14:00 ` Peter Maydell
2012-09-14 14:37 ` Stefan Weil
2012-09-14 16:36 ` Paolo Bonzini
2012-09-14 16:09 ` Kevin Wolf
2012-09-14 16:45 ` Paolo Bonzini
2012-09-14 19:51 ` Blue Swirl
2012-09-14 21:28 ` Paolo Bonzini
2012-09-19 12:54 ` Avi Kivity
2012-09-19 19:57 ` Blue Swirl
2012-09-20 11:31 ` Avi Kivity [this message]
2012-09-22 13:15 ` Blue Swirl
2012-09-23 8:25 ` Avi Kivity
2012-09-23 16:07 ` Blue Swirl
2012-09-24 9:54 ` Avi Kivity
2012-09-16 14:44 ` Anthony Liguori
2012-09-17 7:52 ` Paolo Bonzini
2012-09-17 13:04 ` Anthony Liguori
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=505AFE98.10906@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--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).