From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v2 4/4] x86/traps: honor EXT bit in error codes
Date: Wed, 11 Nov 2015 15:50:21 +0000 [thread overview]
Message-ID: <564363BD.5040207@citrix.com> (raw)
In-Reply-To: <5643170802000078000B3ABA@prv-mh.provo.novell.com>
On 11/11/15 09:23, Jan Beulich wrote:
> The specification does not explicitly limit the use of this bit to
> exceptions that can have selector style error codes, so to be on the
> safe side we should deal with it being set even on error codes formally
> documented to be always zero (if they're indeed always zero, the change
> is simply dead code in those cases).
>
> Introduce and use (where suitable) X86_XEC_* constants to make the code
> easier to read.
>
> To match the placement of the "hardware_trap" label, the "hardware_gp"
> one gets moved slightly too.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2015-11-11 15:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 17:35 [PATCH 0/4] x86: XSA-156 follow-ups Jan Beulich
2015-11-10 17:38 ` [PATCH 1/4] x86/HVM: don't inject #DB with error code Jan Beulich
2015-11-10 17:42 ` Andrew Cooper
2015-12-03 7:46 ` Tian, Kevin
2015-12-03 8:14 ` Jan Beulich
2015-12-03 8:38 ` Tian, Kevin
2015-12-03 9:09 ` Jan Beulich
2015-11-10 17:39 ` [PATCH 2/4] x86/HVM: unify and fix #UD intercept Jan Beulich
2015-11-10 17:51 ` Andrew Cooper
2015-12-03 7:49 ` Tian, Kevin
2015-11-10 17:40 ` [PATCH 3/4] x86/SVM: don't exceed segment limit when fetching instruction bytes Jan Beulich
2015-11-10 18:27 ` Boris Ostrovsky
2015-11-11 16:01 ` Andrew Cooper
2015-11-10 17:40 ` [PATCH 4/4] x86/traps: honor EXT bit in error codes Jan Beulich
2015-11-10 18:20 ` Andrew Cooper
2015-11-11 8:50 ` Jan Beulich
2015-11-11 9:23 ` [PATCH v2 " Jan Beulich
2015-11-11 15:50 ` Andrew Cooper [this message]
2015-12-03 9:04 ` Tian, Kevin
2015-11-11 8:33 ` [PATCH RFC 5/4] x86: #PF error code adjustments Jan Beulich
2015-11-11 16:30 ` Andrew Cooper
2015-11-12 10:12 ` Jan Beulich
2015-11-11 8:39 ` [PATCH 6/4] x86/event: correct debug event generation Jan Beulich
2015-11-11 8:47 ` Razvan Cojocaru
2015-11-11 16:09 ` Andrew Cooper
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=564363BD.5040207@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.