From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [patch 1/3] target-i386: print EFER in cpu_dump_state
Date: Thu, 11 Mar 2010 15:53:23 -0300 [thread overview]
Message-ID: <20100311185323.GC17264@amt.cnet> (raw)
In-Reply-To: <4B98AB49.4030209@redhat.com>
On Thu, Mar 11, 2010 at 10:35:21AM +0200, Avi Kivity wrote:
> On 03/09/2010 03:53 AM, Marcelo Tosatti wrote:
> >Signed-off-by: Marcelo Tosatti<mtosatti@redhat.com>
> >
> >Index: qemu-kvm-uq/target-i386/helper.c
> >===================================================================
> >--- qemu-kvm-uq.orig/target-i386/helper.c
> >+++ qemu-kvm-uq/target-i386/helper.c
> >@@ -1176,6 +1176,7 @@ void cpu_dump_state(CPUState *env, FILE
> > cpu_x86_dump_seg_cache(env, f, cpu_fprintf, "TR",&env->tr);
> >
> > #ifdef TARGET_X86_64
> >+ cpu_fprintf(f, "EFER= %016" PRIx64 "\n", env->efer);
> > if (env->hflags& HF_LMA_MASK) {
> > cpu_fprintf(f, "GDT= %016" PRIx64 " %08x\n",
> > env->gdt.base, env->gdt.limit);
> >
>
> Better to do this for i386 too, no?
"On systems that support IA-32e mode, the extended feature enable
register (IA32_EFER) is available. This model-specific register controls
activation of IA-32e mode and other IA-32e mode operations."
Can it be useful for i386 too?
next prev parent reply other threads:[~2010-03-11 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 1:53 [Qemu-devel] [patch 0/3] misc uq/master updates Marcelo Tosatti
2010-03-09 1:53 ` [Qemu-devel] [patch 1/3] target-i386: print EFER in cpu_dump_state Marcelo Tosatti
2010-03-11 8:35 ` [Qemu-devel] " Avi Kivity
2010-03-11 18:53 ` Marcelo Tosatti [this message]
2010-03-14 7:36 ` Avi Kivity
2010-03-09 1:53 ` [Qemu-devel] [patch 2/3] kvm: handle internal error Marcelo Tosatti
2010-03-11 8:42 ` [Qemu-devel] " Avi Kivity
2010-03-09 1:53 ` [Qemu-devel] [patch 3/3] kvm: allow qemu to set EPT identity mapping address Marcelo Tosatti
2010-03-11 8:42 ` [Qemu-devel] " 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=20100311185323.GC17264@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@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 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).