From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net, mtosatti@redhat.com,
Glauber Costa <gcosta@redhat.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 [thread overview]
Message-ID: <200805022116.29278.paul@codesourcery.com> (raw)
In-Reply-To: <481B705A.8010203@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
next prev parent reply other threads:[~2008-05-02 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 17:49 [Qemu-devel] [PATCH 0/4] Presenting accelerators for better abstraction Glauber Costa
2008-05-02 17:49 ` [Qemu-devel] [PATCH 1/4] [PATCH] introduce QEMUAccel and fill it with interrupt specific driver Glauber Costa
2008-05-02 17:49 ` [Qemu-devel] [PATCH 2/4] [PATCH] exec interrupt made abstract by accel_yyy() Glauber Costa
2008-05-02 17:49 ` [Qemu-devel] [PATCH 3/4] [PATCH] init env made accel driver Glauber Costa
2008-05-02 17:49 ` [Qemu-devel] [PATCH 4/4] [PATCH] wrap cache flushing functions into accel drivers Glauber Costa
2008-05-02 18:16 ` [Qemu-devel] [PATCH 1/4] [PATCH] introduce QEMUAccel and fill it with interrupt specific driver Jamie Lokier
2008-05-02 19:49 ` Glauber Costa
2008-05-02 20:16 ` Paul Brook [this message]
2008-05-02 20:17 ` 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=200805022116.29278.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@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).