All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	paul.c.lai@intel.com, sherry.hurwitz@amd.com
Cc: Jan Beulich <JBeulich@suse.com>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/2] x86/hvm: Correct the position of the %cs L/D checks
Date: Fri, 14 Oct 2016 10:10:00 -0400	[thread overview]
Message-ID: <20161014141000.GC11500@localhost.localdomain> (raw)
In-Reply-To: <1476439616-17287-1-git-send-email-andrew.cooper3@citrix.com>

On Fri, Oct 14, 2016 at 11:06:55AM +0100, Andrew Cooper wrote:
> Contrary to the description in the software manuals, in Long Mode, attempts to
> load %cs check that D is not set in combination with L before the present flag
> is checked.
> 
> This can be observed because the L/D check fails with #GP before the presence
> check failes with #NP

CC-ing Paul and Sherry.

Perhaps the SDMs should mention this as well?

> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> ---
>  xen/arch/x86/x86_emulate/x86_emulate.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/xen/arch/x86/x86_emulate/x86_emulate.c b/xen/arch/x86/x86_emulate/x86_emulate.c
> index 793ce30..b23cd99 100644
> --- a/xen/arch/x86/x86_emulate/x86_emulate.c
> +++ b/xen/arch/x86/x86_emulate/x86_emulate.c
> @@ -1405,6 +1405,14 @@ protmode_load_seg(
>                 /* Non-conforming segment: check RPL and DPL against CPL. */
>                 : rpl > cpl || dpl != cpl )
>              goto raise_exn;
> +        /*
> +         * 64-bit code segments (L bit set) must have D bit clear.
> +         * Experimentally in long mode, the L and D bits are checked before
> +         * the Present bit.
> +         */
> +        if ( in_longmode(ctxt, ops) &&
> +             (desc.b & (1 << 21)) && (desc.b & (1 << 22)) )
> +            goto raise_exn;
>          sel = (sel ^ rpl) | cpl;
>          break;
>      case x86_seg_ss:
> @@ -1444,11 +1452,6 @@ protmode_load_seg(
>          goto raise_exn;
>      }
>  
> -    /* 64-bit code segments (L bit set) must have D bit clear. */
> -    if ( seg == x86_seg_cs && in_longmode(ctxt, ops) &&
> -         (desc.b & (1 << 21)) && (desc.b & (1 << 22)) )
> -        goto raise_exn;
> -
>      /* Ensure Accessed flag is set. */
>      if ( a_flag && !(desc.b & a_flag) )
>      {
> -- 
> 2.1.4
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-10-14 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 10:06 [PATCH 1/2] x86/hvm: Correct the position of the %cs L/D checks Andrew Cooper
2016-10-14 10:06 ` [PATCH 2/2] x86/hvm: Clobber %cs.L when LME becomes set Andrew Cooper
2016-10-14 10:29   ` Jan Beulich
2016-10-14 10:28 ` [PATCH 1/2] x86/hvm: Correct the position of the %cs L/D checks Jan Beulich
2016-10-14 10:32   ` Andrew Cooper
2016-10-14 14:10 ` Konrad Rzeszutek Wilk [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=20161014141000.GC11500@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=paul.c.lai@intel.com \
    --cc=sherry.hurwitz@amd.com \
    --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.