From: Avi Kivity <avi@redhat.com>
To: hollis@alumni.cmu.edu
Cc: qemu-devel@nongnu.org, Glauber Costa <glommer@gmail.com>,
Glauber Costa <glommer@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 3/3] Add KVM support to QEMU
Date: Wed, 29 Oct 2008 16:09:26 +0200 [thread overview]
Message-ID: <49086E96.80809@redhat.com> (raw)
In-Reply-To: <fb412d760810290651l5edf6c8cq1acf6a7be406f8eb@mail.gmail.com>
Hollis Blanchard wrote:
> On Tue, Oct 28, 2008 at 6:36 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Something I was thinking about this morning, and I think the first place
>> where we'll definitely need a hook, is how to deal with
>> kvm_load_registers(). I think there's overlap between KVM and the IO thread
>> here.
>>
>> There are two reasons (I can think of) that most of the device model code
>> can't run in conjunction with TCG. The first is that TCG may modify
>> CPUState in a non-atomic way. The device model may need to access CPUState
>> although there are very few places that it does.
>>
>
> Out of curiosity, where are those places?
>
local apic -- needs to access interrupt disable flag
acpi sleep -- halts the current processor, so tied to cpustate
vmport -- bad ABI requires access to registers
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: hollis@alumni.cmu.edu
Cc: Glauber Costa <glommer@gmail.com>,
Glauber Costa <glommer@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 3/3] Add KVM support to QEMU
Date: Wed, 29 Oct 2008 16:09:26 +0200 [thread overview]
Message-ID: <49086E96.80809@redhat.com> (raw)
In-Reply-To: <fb412d760810290651l5edf6c8cq1acf6a7be406f8eb@mail.gmail.com>
Hollis Blanchard wrote:
> On Tue, Oct 28, 2008 at 6:36 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Something I was thinking about this morning, and I think the first place
>> where we'll definitely need a hook, is how to deal with
>> kvm_load_registers(). I think there's overlap between KVM and the IO thread
>> here.
>>
>> There are two reasons (I can think of) that most of the device model code
>> can't run in conjunction with TCG. The first is that TCG may modify
>> CPUState in a non-atomic way. The device model may need to access CPUState
>> although there are very few places that it does.
>>
>
> Out of curiosity, where are those places?
>
local apic -- needs to access interrupt disable flag
acpi sleep -- halts the current processor, so tied to cpustate
vmport -- bad ABI requires access to registers
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-29 14:09 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 20:13 [PATCH 1/3] Add additional CPU flag definitions Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] " Anthony Liguori
2008-10-28 20:13 ` [PATCH 2/3] Split CPUID from op_helper Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] " Anthony Liguori
2008-10-28 20:13 ` [PATCH 3/3] Add KVM support to QEMU Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] " Anthony Liguori
2008-10-28 20:49 ` Hollis Blanchard
2008-10-28 20:49 ` Hollis Blanchard
2008-10-28 20:49 ` Hollis Blanchard
[not found] ` <fb412d760810281349q2572acf0j4a3f5eff9e8a55a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 20:57 ` Andreas Färber
2008-10-28 21:04 ` Glauber Costa
2008-10-28 21:16 ` Anthony Liguori
2008-10-28 21:05 ` Anthony Liguori
2008-11-04 13:25 ` Avi Kivity
2008-10-28 21:41 ` Gerd Hoffmann
2008-10-28 21:41 ` [Qemu-devel] " Gerd Hoffmann
2008-10-28 21:51 ` Anthony Liguori
2008-10-28 21:51 ` [Qemu-devel] " Anthony Liguori
2008-10-28 23:04 ` Glauber Costa
2008-10-28 23:04 ` Glauber Costa
2008-10-28 23:36 ` Anthony Liguori
2008-10-28 23:36 ` Anthony Liguori
2008-10-29 9:54 ` Avi Kivity
2008-10-29 9:54 ` Avi Kivity
2008-10-29 12:35 ` Glauber Costa
2008-10-29 12:35 ` Glauber Costa
2008-10-29 12:39 ` Avi Kivity
2008-10-29 12:39 ` Avi Kivity
2008-10-29 12:56 ` Glauber Costa
2008-10-29 12:56 ` Glauber Costa
2008-10-29 13:07 ` Anthony Liguori
2008-10-29 13:07 ` Anthony Liguori
2008-10-29 13:23 ` Avi Kivity
2008-10-29 13:23 ` Avi Kivity
2008-10-29 13:32 ` Anthony Liguori
2008-10-29 13:32 ` Anthony Liguori
2008-10-29 13:51 ` Hollis Blanchard
2008-10-29 14:09 ` Avi Kivity [this message]
2008-10-29 14:09 ` Avi Kivity
2008-10-29 14:16 ` Fabrice Bellard
2008-10-29 14:16 ` [Qemu-devel] " Fabrice Bellard
2008-10-29 14:23 ` Anthony Liguori
2008-10-29 19:13 ` Blue Swirl
2008-10-29 19:13 ` Blue Swirl
2008-11-01 16:25 ` Blue Swirl
2008-11-01 16:25 ` Blue Swirl
2008-10-29 14:58 ` Glauber Costa
2008-10-29 14:58 ` [Qemu-devel] " Glauber Costa
2008-10-29 17:41 ` Glauber Costa
2008-10-29 17:41 ` [Qemu-devel] " Glauber Costa
2008-10-29 19:01 ` Anthony Liguori
2008-10-29 19:01 ` [Qemu-devel] " Anthony Liguori
2008-11-04 13:24 ` Avi Kivity
2008-11-04 13:24 ` [Qemu-devel] " Avi Kivity
2008-11-04 14:02 ` Anthony Liguori
2008-11-04 14:02 ` [Qemu-devel] " Anthony Liguori
2008-11-04 14:46 ` Avi Kivity
2008-11-04 14:46 ` [Qemu-devel] " Avi Kivity
2008-11-04 14:50 ` Anthony Liguori
2008-11-04 14:50 ` [Qemu-devel] " 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=49086E96.80809@redhat.com \
--to=avi@redhat.com \
--cc=glommer@gmail.com \
--cc=glommer@redhat.com \
--cc=hollis@alumni.cmu.edu \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.