From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/traps: Avoid the #GP slowpath for guest #DB exceptions
Date: Fri, 9 Jan 2015 17:09:41 +0000 [thread overview]
Message-ID: <54B00B55.9020102@citrix.com> (raw)
In-Reply-To: <54AE9B770200007800052AE1@mail.emea.novell.com>
On 08/01/15 14:00, Jan Beulich wrote:
>>>> On 08.01.15 at 14:25, <andrew.cooper3@citrix.com> wrote:
>> do_debug() is capable of correctly dealing with #DB exceptions in guest
>> context, and indeed needs to be as the 'icebp' instruction skips the DPL
>> check anyway.
> I don't follow: ICEBP doesn't check DPL, right, but what does setting
> DPL to 3 buy us? Other than for INTO and INT3, we don't want to
> encourage use of INT $0x01 instructions, nor am I aware of anyone
> commonly using them. Yet afaict only they would be affected by your
> change. Actual #DB, just like any other hardware exceptions, don't
> consider DPL just like ICEBP doesn't.
>
> Jan
>
I noticed it as I was attempting to get my debugtraps test case working
for PV guests, which does indeed use 'int $0x1'. But as you point out,
it is only 'int $0x1' we would gain a fastpath for, which doesn't really
make it worthwhile.
~Andrew
prev parent reply other threads:[~2015-01-09 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 13:25 [PATCH] x86/traps: Avoid the #GP slowpath for guest #DB exceptions Andrew Cooper
2015-01-08 14:00 ` Jan Beulich
2015-01-09 17:09 ` Andrew Cooper [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=54B00B55.9020102@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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.