qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Boqun Feng <boqun.feng@intel.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] i386: add KNM cpu model
Date: Fri, 16 Mar 2018 09:42:28 +0000	[thread overview]
Message-ID: <20180316094228.GC3066@redhat.com> (raw)
In-Reply-To: <20180316021157.GB3734@dragonstone.sh.intel.com>

On Fri, Mar 16, 2018 at 10:11:57AM +0800, Boqun Feng wrote:
> On Wed, Mar 14, 2018 at 01:01:30PM +0000, Daniel P. Berrangé wrote:
> > On Wed, Mar 14, 2018 at 03:29:59PM +0800, Boqun Feng wrote:
> > > A new cpu model called "KNM" is added to model Knights Mill processors.
> > 
> > Why the obscure acryonym? Can't we just call it KnightsMill so it is
> > obvious what it is to everyone, as we've done for all other Intel
> > CPU model names in the past.
> > 
> 
> Ah.. my bad, good point! I will rename to "KnightsMill" in the next
> version.
> 
> > > Compared to "Skylake-Server" cpu model, the following features are
> > > added:
> > > 
> > > 	avx512_4vnniw avx512_4fmaps avx512pf avx512er avx512_vpopcntdq
> > > 
> > > and the following features are removed:
> > > 
> > > 	pcid invpcid clflushopt avx512dq avx512bw axv512cd clwb smap rtm
> > > 	mpx xsavec xgetbv1 hle
> > 
> > "pcid" was one of the features critical to mitigate performance
> > downside of the Meltdown bug fix in guests. Will Knights Mill have
> > a fix for Meltdown in hardware, to avoid the need for split table
> > pages and thus avoid the perf hit in guests ?
> > 
> 
> I got the confirmation the Knights Mill doesn't have PCID at all. For
> the alternative fix for Meltdown in hardware, I will ask around and info
> you if I get something.

No need to wait for an answer to that question - if 'pcid' is not
in hardware, we simply have to accept whatever the answer is. So
just repost with the changed name.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      reply	other threads:[~2018-03-16  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  7:29 [Qemu-devel] [PATCH] i386: add KNM cpu model Boqun Feng
2018-03-14 13:01 ` Daniel P. Berrangé
2018-03-16  2:11   ` Boqun Feng
2018-03-16  9:42     ` Daniel P. Berrangé [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=20180316094228.GC3066@redhat.com \
    --to=berrange@redhat.com \
    --cc=boqun.feng@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).