From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [6684] Fix "info registers" under kvm.
Date: Sun, 08 Mar 2009 11:36:40 -0500 [thread overview]
Message-ID: <49B3F418.4090805@codemonkey.ws> (raw)
In-Reply-To: <49B3F0F5.8020202@redhat.com>
Avi Kivity wrote:
> Avi Kivity wrote:
>> Jan Kiszka wrote:
>>> I'm just still waiting for a reply from Anthony on how to embed best
>>> all
>>> the "if (kvm_enabled()) foo();" patterns [2]. That would also allow us
>>> to merge gdbstub support for upstream kvm.
>>>
>>>
>>
>> Wouldn't 'if (!kvm_enabled()) return;' inside the callees suffice?
>
> Rather,
>
> static inline void kvm_foo(...)
> {
> if (!kvm_enabled()) {
> return;
> }
>
> #ifdef CONFIG_KVM
> kvm_do_foo();
> #endif
> }
In the case of save/load registers, I'd prefer wrapper functions like:
cpu_state_update(CPUState *env, int is_dirty)
That could be hooked by something like Xen. The implementation would be:
static void cpu_state_update(CPUState *env, int is_dirty)
{
if (kvm_enabled()) {
if (is_dirty)
kvm_arch_save_registers(env);
else
kvm_arch_load_registers(env);
}
}
Regards,
Anthony Liguori
>
>
next prev parent reply other threads:[~2009-03-08 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:00 [Qemu-devel] [6684] Fix "info registers" under kvm Andrzej Zaborowski
2009-03-08 15:56 ` [Qemu-devel] " Jan Kiszka
2009-03-08 16:10 ` Anthony Liguori
2009-03-08 16:32 ` Jan Kiszka
2009-03-08 16:40 ` Anthony Liguori
2009-03-09 7:46 ` Gerd Hoffmann
2009-03-08 16:35 ` Andreas Färber
2009-03-09 9:42 ` Avi Kivity
2009-03-08 16:18 ` Avi Kivity
2009-03-08 16:23 ` Avi Kivity
2009-03-08 16:36 ` Blue Swirl
2009-03-09 9:42 ` Avi Kivity
2009-03-08 16:36 ` Anthony Liguori [this message]
2009-03-09 9:41 ` Avi Kivity
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=49B3F418.4090805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).