All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] x86emul: don't read mask register on AVX512F-incapable platforms
Date: Thu, 28 Mar 2019 18:03:40 +0000	[thread overview]
Message-ID: <baef5f45-98ca-a53b-daac-6c0f7884eb26@citrix.com> (raw)
In-Reply-To: <232d7494-4976-4028-4cef-76f9bef85981@citrix.com>

On 28/03/2019 17:44, George Dunlap wrote:
> On 3/28/19 5:03 PM, Jan Beulich wrote:
>> Reported-by: George Dunlap <george.dunlap@citrix.com>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> That seems to fix all the ones related to the crashes I was seeing:
>
> Tested-by: George Dunlap <george.dunlap@citrix.com>
>
>> ---
>> This is surely a stable tree candidate, unless it could still make it
>> into 4.12 before the release.
>>
>> --- a/xen/arch/x86/x86_emulate/x86_emulate.c
>> +++ b/xen/arch/x86/x86_emulate/x86_emulate.c
>> @@ -3511,7 +3511,7 @@ x86_emulate(
>>      }
>>  
>>      /* With a memory operand, fetch the mask register in use (if any). */
>> -    if ( ea.type == OP_MEM && evex.opmsk )
>> +    if ( ea.type == OP_MEM && cpu_has_avx512f && evex.opmsk )

So, this certainly will fix the crash as reported, you need an %xcr0
check, to prevent other ways of this stub faulting.

~Andrew

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

  reply	other threads:[~2019-03-28 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 17:03 [PATCH] x86emul: don't read mask register on AVX512F-incapable platforms Jan Beulich
2019-03-28 17:44 ` George Dunlap
2019-03-28 18:03   ` Andrew Cooper [this message]
2019-03-29  6:59     ` Jan Beulich
2019-03-29  7:42 ` [PATCH v2] " Jan Beulich
2019-03-29  9:19   ` Andrew Cooper
2019-03-29  9:36     ` Jan Beulich
2019-03-29 10:02       ` Andrew Cooper
2019-03-29 10:56         ` Jan Beulich
2019-04-01 14:14           ` Andrew Cooper
2019-04-01 15:02             ` Jan Beulich

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=baef5f45-98ca-a53b-daac-6c0f7884eb26@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@citrix.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --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.