From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LF5hm-0003Re-0M
	for qemu-devel@nongnu.org; Tue, 23 Dec 2008 06:45:42 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LF5hk-0003QA-Vf
	for qemu-devel@nongnu.org; Tue, 23 Dec 2008 06:45:41 -0500
Received: from [199.232.76.173] (port=45734 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LF5hk-0003Q1-SR
	for qemu-devel@nongnu.org; Tue, 23 Dec 2008 06:45:40 -0500
Received: from mail-bw0-f12.google.com ([209.85.218.12]:46726)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1LF5hk-0003w6-BN
	for qemu-devel@nongnu.org; Tue, 23 Dec 2008 06:45:40 -0500
Received: by bwz5 with SMTP id 5so47336bwz.10
	for <qemu-devel@nongnu.org>; Tue, 23 Dec 2008 03:45:38 -0800 (PST)
Message-ID: <f43fc5580812230343x4970d059wec310f0f4f7f8aef@mail.gmail.com>
Date: Tue, 23 Dec 2008 13:43:30 +0200
From: "Blue Swirl" <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem
In-Reply-To: <5d6222a80812220900x1d5e6301x7a6686ec56d25c61@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1229619702-26315-1-git-send-email-glommer@redhat.com>
	<1229619702-26315-2-git-send-email-glommer@redhat.com>
	<1229619702-26315-3-git-send-email-glommer@redhat.com>
	<1229619702-26315-4-git-send-email-glommer@redhat.com>
	<1229619702-26315-5-git-send-email-glommer@redhat.com>
	<1229619702-26315-6-git-send-email-glommer@redhat.com>
	<f43fc5580812191157n3b56d7b6hf6d0e049a64898e@mail.gmail.com>
	<494C096D.1050902@codemonkey.ws>
	<f43fc5580812200328i7874be90i5073ab5b0252f3f1@mail.gmail.com>
	<5d6222a80812220900x1d5e6301x7a6686ec56d25c61@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Ian.Jackson@eu.citrix.com, avi@redhat.com, kvm@vger.kernel.org, stefano.stabellini@eu.citrix.com

On 12/22/08, Glauber Costa <glommer@gmail.com> wrote:
> >>  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.

But something new can still come and replace TCG.

>  >>  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.

I vote for "default".