From: Glauber Costa <glommer@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2] introduce on_vcpu
Date: Thu, 16 Jul 2009 18:59:42 -0300 [thread overview]
Message-ID: <20090716215942.GC4019@poweredge.glommer> (raw)
In-Reply-To: <4A5F9D32.9060700@us.ibm.com>
On Thu, Jul 16, 2009 at 04:35:46PM -0500, Anthony Liguori wrote:
> Glauber Costa wrote:
>> on_vcpu is a qemu-kvm function that will make sure that a specific
>> piece of code will run on a requested cpu. We don't need that because
>> we're restricted to -smp 1 right now, but those days are likely to end soon.
>>
>> So for the benefit of having qemu-kvm share more code with us, I'm
>> introducing our own version of on_vcpu(). Right now, we either run
>> a function on the current cpu, or abort the execution, because it would
>> mean something is seriously wrong.
>>
>> As an example code, I "ported" kvm_update_guest_debug to use it,
>> with some slight differences from qemu-kvm.
>>
>> This is probably 0.12 material
>>
>> Signed-off-by: Glauber Costa <glommer@redhat.com>
>> CC: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> kvm-all.c | 37 +++++++++++++++++++++++++++++++------
>> 1 files changed, 31 insertions(+), 6 deletions(-)
>>
>> diff --git a/kvm-all.c b/kvm-all.c
>> index 61194b8..0c881e8 100644
>> --- a/kvm-all.c
>> +++ b/kvm-all.c
>> @@ -39,6 +39,8 @@
>> do { } while (0)
>> #endif
>>
>> +CPUState *current_env;
>> +
>>
>
> That shouldn't be there anymore...
oops ;-)
>
> --
> Regards,
>
> Anthony Liguori
>
prev parent reply other threads:[~2009-07-16 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 21:25 [Qemu-devel] [PATCH v2] introduce on_vcpu Glauber Costa
2009-07-16 21:35 ` [Qemu-devel] " Anthony Liguori
2009-07-16 21:59 ` Glauber Costa [this message]
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=20090716215942.GC4019@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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).