From: "Alexandro Sanchez Bach" <alexaltea123@gmail.com>
To: qemu-devel@nongnu.org
Cc: 'Anthony Liguori' <aliguori@us.ibm.com>,
'Glauber Costa' <gcosta@redhat.com>
Subject: [Qemu-devel] Debugging on HAXM
Date: Sun, 1 Apr 2018 17:35:44 +0200 [thread overview]
Message-ID: <000001d3c9cf$19f0a190$4dd1e4b0$@gmail.com> (raw)
Hello,
A bit of context: I'm working on a QEMU fork adding support for PlayStation
4 hardware. It's still in development and debugging kernel drivers has
become everyday work. While TCG supports debugging, it cannot handle various
extensions like AVX/AVX2 that are extensively used by the guest applications
and performance has become quite a problem. This system is closed source and
wasn't built with kernel debugging support, so debugging it "from the
outside" is the only possibility and hence why debugging on accelerators
(specially HAXM/WHPX) has become absolutely necessary for my project.
I've noticed that `gdb_breakpoint_insert` only considers KVM so far. My
question is: Has anyone planned adding debugging support to HAXM? Or is
anyone actively working on QEMU's HAXM frontend at all? If not, I would like
to work on it myself. Are there any guidelines or things I should take into
consideration to work on this accelerator (pinging Anthony and Glauber)?
Would it be more reasonable to add debugging support to HAXM [1] directly
instead of trying to use the existing APIs from QEMU to achieve the same
thing (I was thinking in patching memory, e.g. with `hlt` instructions, to
trigger VM exits)?
Just want to hear your thoughts on the matter. :-)
Cheers,
Alexandro Sanchez
[1] https://github.com/intel/haxm/
next reply other threads:[~2018-04-01 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 15:35 Alexandro Sanchez Bach [this message]
2018-04-02 2:20 ` [Qemu-devel] Debugging on HAXM Paolo Bonzini
2018-04-12 9:09 ` Yu Ning
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='000001d3c9cf$19f0a190$4dd1e4b0$@gmail.com' \
--to=alexaltea123@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=gcosta@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).