From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Js1gQ-00048C-C8
	for qemu-devel@nongnu.org; Fri, 02 May 2008 16:16:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Js1gM-00045r-OX
	for qemu-devel@nongnu.org; Fri, 02 May 2008 16:16:41 -0400
Received: from [199.232.76.173] (port=56864 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Js1gM-00045o-JF
	for qemu-devel@nongnu.org; Fri, 02 May 2008 16:16:38 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1Js1gM-0001V8-8R
	for qemu-devel@nongnu.org; Fri, 02 May 2008 16:16:38 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] [PATCH] introduce QEMUAccel and fill it
	with interrupt specific driver
Date: Fri, 2 May 2008 21:16:28 +0100
References: <12097505533742-git-send-email-gcosta@redhat.com>
	<20080502181607.GA2827@shareable.org> <481B705A.8010203@redhat.com>
In-Reply-To: <481B705A.8010203@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200805022116.29278.paul@codesourcery.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: kvm-devel@lists.sourceforge.net, mtosatti@redhat.com, Glauber Costa <gcosta@redhat.com>

> > Maybe 'VCPU' would be a clearer name?  QEMU provides its own VCPU, and
> > KQEMU+QEMU also provide one toegether.  While KVM provides essentially
> > one or more whole VCPUs by itself and uses QEMU's drivers only doesn't
> > it?
> >
> > -- Jamie
>
> VCPU is rather confusing with the vcpus themselves. KVM, for instance,
> has its own structures called "vcpu".
>
> If it is preferred, however, we can name the structure VCPUOperations,
> and change the function names that involves accel_yyy to vcpu_op_yyy()

kvm wants to hook into more than just the CPU doesn't it?

Paul