From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@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 10:35:21 +0200 [thread overview]
Message-ID: <4B98AB49.4030209@redhat.com> (raw)
In-Reply-To: <20100309015644.133975091@redhat.com>
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?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-11 8:35 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 ` Avi Kivity [this message]
2010-03-11 18:53 ` [Qemu-devel] " Marcelo Tosatti
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=4B98AB49.4030209@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).