From: Christopher Caulfield <ctcaulfield@gmail.com>
To: qemu-devel@nongnu.org
Cc: alexsmendez@live.com
Subject: QEMU on x64
Date: Fri, 30 Jul 2021 10:36:01 -0700 [thread overview]
Message-ID: <CAGu1Vjjot17roFD-YTWmQcDhhMD=Lzi3b3Q51cHNRnz+6JT_HQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi QEMU community,
This is Christopher from the debugging experiences team at Microsoft
focused on kernel debugging. I am reaching out with a few questions about
QEMU on x64.
1. Is it possible for the QEMU-x86-64 GDB Server to send the full set of
x64 system registers (whether they are included in a separated system xml
file or as part of the core registers xml file)?
- e.g. System registers missing from i386-64bit.xml file
DWORD64 IDTBase;
DWORD64 IDTLimit;
DWORD64 GDTBase;
DWORD64 GDTLimit;
DWORD SelLDT;
SEG64_DESC_INFO SegLDT;
DWORD SelTSS;
SEG64_DESC_INFO SegTSS;
2. How can I access x64 MSR registers by using the QEMU-x86-64 GDB
server?
- #define MSR_EFER 0xc0000080 // extended function enable register
#define MSR_STAR 0xc0000081 // system call selectors
#define MSR_LSTAR 0xc0000082 // system call 64-bit entry
#define MSR_CSTAR 0xc0000083 // system call 32-bit entry
3. Going off of #2 - can you access it via reading GDB memory command?
if not - is there any plan to support reading/writing to MSRs via
QEMU-x86-64 GDB server?
Thank you for taking time to answer our questions! :)
-Christopher
LinkedIn <https://www.linkedin.com/in/ctcaulfield/> | Twitter
<https://twitter.com/ctcaulfield>
[-- Attachment #2: Type: text/html, Size: 1435 bytes --]
next reply other threads:[~2021-07-30 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 17:36 Christopher Caulfield [this message]
2021-07-30 18:13 ` QEMU on x64 Peter Maydell
2021-08-02 17:27 ` Alex Bennée
2021-08-03 1:34 ` Christopher Caulfield
2021-11-12 23:18 ` Christopher Caulfield
2021-08-02 9:05 ` Paolo Bonzini
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='CAGu1Vjjot17roFD-YTWmQcDhhMD=Lzi3b3Q51cHNRnz+6JT_HQ@mail.gmail.com' \
--to=ctcaulfield@gmail.com \
--cc=alexsmendez@live.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).