From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org
Cc: avi@redhat.com, Ian.Jackson@eu.citrix.com, kvm@vger.kernel.org,
stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem
Date: Mon, 22 Dec 2008 15:00:12 -0200 [thread overview]
Message-ID: <5d6222a80812220900x1d5e6301x7a6686ec56d25c61@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580812200328i7874be90i5073ab5b0252f3f1@mail.gmail.com>
>> It really does though. The way physical memory is registered and managed
>> is TCG specific right now. It has deep hooks for invalidating
>> TranslationBlock's, and the table structure is designed to be conducive to
>> the access patterns of TCG.
>
> Yes, but also dyngen stuff used the same structures, so it's a bit
> more generic than TCG-only.
yeah, but dyngen is gone now. So tcg really stands for "whatever qemu
does", in here.
>
>> If you think of a higher level CPU API, I think registering physical memory
>> and reading/writing physical memory would end up being part of that API.
>
> Thanks, I was looking for something like this. CPU emulator is more
> than just TCG or dyngen and it is also ~KVM. So how about
> cpu_emu_register_physical_memory_offset?
>
> Also noaccel_register_physical_memory_offset would fit.
After this revision, I must say I'm less happy with the name "accel".
It's really a cpu model. I'm even thinking about changing the name of it
to QEMUCPUModel or whatever. (suggestions welcome)
So "default" or "qemu" would be good choices IMHO.
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2008-12-22 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 17:01 [Qemu-devel] [PATCH 0/6] bypass tcg memory functions -v2 Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 1/6] remove smaller slots if registering a bigger one Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 2/6] re-register whole area upon lfb unmap Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 3/6] isolate io handling routine Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 6/6] cache slot lookup Glauber Costa
2008-12-19 19:57 ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Blue Swirl
2008-12-19 20:14 ` Laurent Desnogues
2008-12-19 20:51 ` Anthony Liguori
2008-12-20 11:28 ` Blue Swirl
2008-12-22 17:00 ` Glauber Costa [this message]
2008-12-23 11:43 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 18:50 [Qemu-devel] [PATCH 0/6] Bypass tcg memory functions -v1.0-2009 Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 1/6] remove smaller slots if registering a bigger one Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 2/6] re-register whole area upon lfb unmap Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 3/6] isolate io handling routine Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Glauber Costa
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=5d6222a80812220900x1d5e6301x7a6686ec56d25c61@mail.gmail.com \
--to=glommer@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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).