From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Handle init/sipi in a main cpu exec loop.
Date: Wed, 17 Jun 2009 14:54:08 -0500 [thread overview]
Message-ID: <4A3949E0.4040007@codemonkey.ws> (raw)
In-Reply-To: <20090617151557.GE19508@redhat.com>
Gleb Natapov wrote:
> Currently INIT/SIPI is handled in the context of CPU that sends IPI.
> This patch changes this to handle them like all other events in a main
> cpu exec loop. When KVM will gain thread per vcpu capability it will
> be much more clear to handle those event by cpu thread itself and not
> modify one cpu's state from the context of the other.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
This breaks the linux-user build.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-17 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 15:15 [Qemu-devel] [PATCH] Handle init/sipi in a main cpu exec loop Gleb Natapov
2009-06-17 19:54 ` Anthony Liguori [this message]
2009-06-17 20:26 ` [Qemu-devel] [PATCH] Handle init/sipi in a main cpu exec loop. (v2) Gleb Natapov
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=4A3949E0.4040007@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gleb@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).