From: Alex Smith <alex@alex-smith.me.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Resume Flag support on i386/x86_64?
Date: Tue, 17 Feb 2009 08:27:57 +0000 [thread overview]
Message-ID: <309a0db40902170027s75a1505fn6de64be94a82e05e@mail.gmail.com> (raw)
Hi,
Recently support for hardware breakpoint support on i386/x86_64 was
added (revision 5747 -
http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg01025.html).
I've been using hardware breakpoints while writing a debugger for my
hobby OS kernel, however I've discovered that despite support being
added for them in QEMU, the Resume Flag (bit 16 in EFLAGS) is not
supported. When this flag is set on return from an interrupt, the CPU
should ignore instruction breakpoints for the next instruction, and
then clear the flag after checking for breakpoints (there's a
description on page 18-10 of the Intel Software Developer's Manual
Volume 3B).
Would it be possible to implement support for this?
Thanks,
Alex
next reply other threads:[~2009-02-17 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 8:27 Alex Smith [this message]
2009-02-17 9:18 ` [Qemu-devel] Re: Resume Flag support on i386/x86_64? Jan Kiszka
2009-02-17 9:39 ` Alex Smith
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=309a0db40902170027s75a1505fn6de64be94a82e05e@mail.gmail.com \
--to=alex@alex-smith.me.uk \
--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).