From: Kip Macy <kip.macy@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: softirq change was Re: domu_debug support removed on march 25th from traps.c in -unstable
Date: Wed, 13 Apr 2005 11:05:43 -0700 [thread overview]
Message-ID: <b1fa2917050413110565550855@mail.gmail.com> (raw)
In-Reply-To: <98f0605c58c187fcf208ffabd00cce56@cl.cam.ac.uk>
> You mean that the TF bit is not cleared by the domu_debug code when it
> should be? The correct place to fix this is in
> include/asm-x86/debugger.h in debugger_trap_entry().
Yes. Continuing after single-stepping no longer works.
> In general (not using domu_debug) it is not Xen's job to clear TF. We
> clear it when we 'bounce' the exception into the guest OS, but the
> saved application stack frame will include EFLAGS with the TF bit still
> set. This matches real hardware.
No it isn't Xen's job to clear it under normal circumstances as that
would break PTRACE_SINGLESTEP in user-space. However, it was what the
PDB code was doing and it seemed easy enough to clear it there to
emulate PTRACE_SINGLESTEP for the kernel.
I honestly don't care where it happens, it is easy enough to clear the
TF from xc_ptrace.c. I just happened to be *extremely* tired last
night and was dealing with other issues, so I was frustrated when that
didn't work. I'll just incorporate my fix to xc_ptrace.c in with the
FreeBSD fixes for -unstable.
-Kip
prev parent reply other threads:[~2005-04-13 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 5:39 domu_debug support removed on march 25th from traps.c in -unstable Kip Macy
2005-04-13 5:47 ` softirq change was " Kip Macy
2005-04-13 17:44 ` Keir Fraser
2005-04-13 17:48 ` Kip Macy
2005-04-13 17:59 ` Keir Fraser
2005-04-13 18:05 ` Kip Macy [this message]
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=b1fa2917050413110565550855@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.