From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [6684] Fix "info registers" under kvm.
Date: Sun, 08 Mar 2009 17:32:51 +0100 [thread overview]
Message-ID: <49B3F333.4060504@web.de> (raw)
In-Reply-To: <49B3EE01.3090402@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
Anthony Liguori wrote:
> Jan Kiszka wrote:
>> Andrzej Zaborowski wrote:
>>
>>> Revision: 6684
>>> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6684
>>> Author: balrog
>>> Date: 2009-03-04 21:00:07 +0000 (Wed, 04 Mar 2009)
>>> Log Message:
>>> -----------
>>> Fix "info registers" under kvm.
>>>
>>> Modified Paths:
>>> --------------
>>> trunk/target-i386/helper.c
>>>
>>> Modified: trunk/target-i386/helper.c
>>> ===================================================================
>>> --- trunk/target-i386/helper.c 2009-03-04 19:25:22 UTC (rev 6683)
>>> +++ trunk/target-i386/helper.c 2009-03-04 21:00:07 UTC (rev 6684)
>>> @@ -578,6 +578,9 @@
>>> char cc_op_name[32];
>>> static const char *seg_name[6] = { "ES", "CS", "SS", "DS", "FS",
>>> "GS" };
>>>
>>> + if (kvm_enabled())
>>> + kvm_arch_get_registers(env);
>>> +
>>> eflags = env->eflags;
>>> #ifdef TARGET_X86_64
>>> if (env->hflags & HF_CS64_MASK) {
>>>
>>>
>>
>> On the one hand, this patch also takes care of sync'ing with KVM in case
>> of cpu_dump_state on fatal exists. On the other hand, it only solves one
>> part of monitor issue. See [1] for a more complete sync.
>>
>> 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.
>>
>
> I really don't have a great suggestion. I've been hoping we could come
> up with something better than if (kvm_enabled()) foo(). If we can't, we
> can't.
We could do
static inline void kvm_get_registers(CPUState *env)
{
if (kvm_enabled())
kvm_arch_get_registers(env);
}
in kvm.h (and kvm_put_registers analogously). That would still be
kvm-specific, though, but it would reduce the impact on the code that
has to be extended this way.
Generic hooks is something I would really like to postpone here until we
start working on some accelerator abstraction.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-03-08 16:33 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 [this message]
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
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=49B3F333.4060504@web.de \
--to=jan.kiszka@web.de \
--cc=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 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.