All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [patch 1/3] target-i386: print EFER in cpu_dump_state
Date: Mon, 08 Mar 2010 22:53:44 -0300	[thread overview]
Message-ID: <20100309015644.133975091@redhat.com> (raw)
In-Reply-To: 20100309015343.901738854@redhat.com

[-- Attachment #1: print-efer --]
[-- Type: text/plain, Size: 606 bytes --]

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);



WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [Qemu-devel] [patch 1/3] target-i386: print EFER in cpu_dump_state
Date: Mon, 08 Mar 2010 22:53:44 -0300	[thread overview]
Message-ID: <20100309015644.133975091@redhat.com> (raw)
In-Reply-To: 20100309015343.901738854@redhat.com

[-- Attachment #1: print-efer --]
[-- Type: text/plain, Size: 604 bytes --]

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);

  reply	other threads:[~2010-03-09  1:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09  1:53 [patch 0/3] misc uq/master updates Marcelo Tosatti
2010-03-09  1:53 ` [Qemu-devel] " Marcelo Tosatti
2010-03-09  1:53 ` Marcelo Tosatti [this message]
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   ` Avi Kivity
2010-03-11  8:35     ` [Qemu-devel] " Avi Kivity
2010-03-11 18:53     ` Marcelo Tosatti
2010-03-11 18:53       ` [Qemu-devel] " Marcelo Tosatti
2010-03-14  7:36       ` Avi Kivity
2010-03-14  7:36         ` [Qemu-devel] " Avi Kivity
2010-03-09  1:53 ` [patch 2/3] kvm: handle internal error Marcelo Tosatti
2010-03-09  1:53   ` [Qemu-devel] " Marcelo Tosatti
2010-03-11  8:42   ` Avi Kivity
2010-03-11  8:42     ` [Qemu-devel] " Avi Kivity
2010-03-09  1:53 ` [patch 3/3] kvm: allow qemu to set EPT identity mapping address Marcelo Tosatti
2010-03-09  1:53   ` [Qemu-devel] " Marcelo Tosatti
2010-03-11  8:42   ` Avi Kivity
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=20100309015644.133975091@redhat.com \
    --to=mtosatti@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 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.