All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: qemu patch for mb_clear
Date: Wed, 9 Jan 2019 22:44:59 +0100	[thread overview]
Message-ID: <2a833765-3d5a-3664-dd5e-3a256a29ff4b@redhat.com> (raw)
In-Reply-To: <20190109170919.GU23427@char.us.oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On 09/01/19 18:09, speck for Konrad Rzeszutek Wilk wrote:
> On Thu, Dec 20, 2018 at 04:31:01PM -0800, speck for Andi Kleen wrote:
>>
>> For reference here is the qemu patch needed for using MB_CLEAR in a KVM
>> guest.
> 
> I thought it was called 'MD_CLEAR' ?
> 
>>
>> -Andi
>>
>> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
>> index 677a3bd5fb25..77a1149e4bb3 100644
>> --- a/target/i386/cpu.c
>> +++ b/target/i386/cpu.c
>> @@ -1038,7 +1038,7 @@ static FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
>>          .feat_names = {
>>              NULL, NULL, "avx512-4vnniw", "avx512-4fmaps",
>>              NULL, NULL, NULL, NULL,
>> -            NULL, NULL, NULL, NULL,
>> +            NULL, NULL, "mbclear", NULL,
>>              NULL, NULL, NULL, NULL,
>>              NULL, NULL, "pconfig", NULL,
>>              NULL, NULL, NULL, NULL,

Are there any CPU families which will all have it (e.g. IceLake server,
Cascade Lake?).  Prerelease/prototype silicon does not count.

Paolo


  parent reply	other threads:[~2019-01-09 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21  0:31 [MODERATED] qemu patch for mb_clear Andi Kleen
2019-01-09 17:09 ` [MODERATED] " Konrad Rzeszutek Wilk
2019-01-09 17:33   ` Andi Kleen
2019-01-09 21:44   ` Paolo Bonzini [this message]
2019-01-09 21:55     ` Andi Kleen
2019-01-09 22:37       ` Paolo Bonzini
2019-03-01 14:37 ` Josh Poimboeuf
2019-03-01 15:11   ` Josh Poimboeuf

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=2a833765-3d5a-3664-dd5e-3a256a29ff4b@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=speck@linutronix.de \
    /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.