From: Richard Henderson <rth@twiddle.net>
To: Julian Kirsch <git@kirschju.re>, qemu-devel@nongnu.org
Cc: Julian Kirsch <mail@kirschju.re>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] X86/HMP: Expose x86 model specific registers via human monitor
Date: Wed, 8 Mar 2017 14:09:58 +1100 [thread overview]
Message-ID: <a01a515b-4296-4f5f-0509-2227a68e6770@twiddle.net> (raw)
In-Reply-To: <20170308001637.9838-1-git@kirschju.re>
On 03/08/2017 11:16 AM, Julian Kirsch wrote:
> For instance, many modern x86-64 operating systems maintain access to internal
> data structures via the MSR_GSBASE/MSR_KERNELGSBASE MSRs. Giving
> introspection utilities (such as a remotely attached gdb) a way of
> accessing these registers improves analysis results drastically.
If this is just for gdb, then we should provide access via the normal gdbstub,
plus appropriate xml files. There are plenty of examples of this for other cpus.
r~
next prev parent reply other threads:[~2017-03-08 3:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170308001637.9838-1-git@kirschju.re>
2017-03-08 2:36 ` [Qemu-devel] [PATCH] X86/HMP: Expose x86 model specific registers via human monitor Eric Blake
2017-03-08 8:26 ` Julian Kirsch
2017-03-10 14:09 ` Igor Mammedov
2017-03-10 16:11 ` Julian Kirsch
2017-03-08 3:09 ` Richard Henderson [this message]
2017-03-08 11:34 ` Julian Kirsch
2017-03-08 11:59 ` Dr. David Alan Gilbert
2017-03-08 13:57 ` Eduardo Habkost
2017-03-08 16:08 ` Julian Kirsch
2017-03-08 18:44 ` Eduardo Habkost
2017-03-09 16:32 ` Paolo Bonzini
2017-03-09 17:27 ` Eduardo Habkost
2017-03-09 18:05 ` Julian Kirsch
2017-03-08 15:40 ` Julian Kirsch
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=a01a515b-4296-4f5f-0509-2227a68e6770@twiddle.net \
--to=rth@twiddle.net \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=git@kirschju.re \
--cc=mail@kirschju.re \
--cc=pbonzini@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).