qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Pavel Hrdina <phrdina@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Hetz Ben Hamo" <hetz@hetz.biz>,
	qemu-devel@nongnu.org, libvir-list@redhat.com,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Babu Moger" <babu.moger@amd.com>,
	"Brijesh Singh" <brijesh.singh@amd.com>
Subject: Re: [Qemu-devel] [libvirt] CPU Support
Date: Wed, 18 Jul 2018 10:49:02 -0300	[thread overview]
Message-ID: <20180718134902.GY31657@localhost.localdomain> (raw)
In-Reply-To: <20180718101844.GB22954@antique-laptop>

CCing the AMD people who worked on this.

On Wed, Jul 18, 2018 at 12:18:45PM +0200, Pavel Hrdina wrote:
> On Wed, Jul 18, 2018 at 10:50:34AM +0100, Daniel P. Berrangé wrote:
> > On Wed, Jul 18, 2018 at 12:41:48PM +0300, Hetz Ben Hamo wrote:
> > > Hi,
> > > 
> > > I've been looking at the CPU list and although I see lots of CPU's, I
> > > cannot find 2 CPU families:
> > > 
> > > * AMD Ryzen
> > > * AMD Threadripper
> > > 
> > > Although EPYC has been added recently.
> > > 
> > > Are there any missing details which preventing adding those CPU's to the
> > > list?
> > 
> > Libvirt adds CPU models based on what QEMU supports. So from libvirt side the
> > answer is simply that QEMU doesn't expose any models for Ryzen/Threadripper,
> > but I'm not clear why it doesn't...
> > 
> > For a while I thought Ryzen/Threadripper would have same feature set as
> > EPYC, but I've seen bugs recently suggesting that is not in fact the
> > case. So it does look like having those models exposed by QEMU might
> > be useful.
> > 
> > Copy'ing QEMU devel & the CPU model maintainers for opinions.
> 
> I think that QEMU should figure out some pattern for naming CPU models
> because it's one big mess.  EPYC and Ryzen are bad names for QEMU as
> Core/Xeon would be for Intel CPUs.  It's the name of a model families
> and it will probably remain the same but with different
> microarchitecture.
> 
> Better name would be similarly like for the latest Inter CPUs,
> Skylake-Client and Skylake-Server.  Currently AMD has already two
> microarchitectures, Zen and Zen+ and there is third one Zen 2 planned.
> 
> Zen has AMD Ryzen, AMD Ryzen Threadripper and AMD Epyc.
> Zen+ has AMD Ryzen, AMD Ryzen Threadripper
> 
> And I bet that Zen 2 will follow the same model families.
> 
> We probably cannot rename EPYC now, but before we introduce Ryzen and
> Threadripper let's thing about it and come up with better names, for
> example Zen-Client/Zen-Server Zen+-Client or something like that.
> 
> Pavel

-- 
Eduardo

  reply	other threads:[~2018-07-18 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANhJxzwZny93TOTKTpEoThN8bnw1tXENPH_S60wczUAQodBMNw@mail.gmail.com>
2018-07-18  9:50 ` [Qemu-devel] [libvirt] CPU Support Daniel P. Berrangé
2018-07-18 10:18   ` Pavel Hrdina
2018-07-18 13:49     ` Eduardo Habkost [this message]
2018-07-19  2:15       ` Brijesh Singh

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=20180718134902.GY31657@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=babu.moger@amd.com \
    --cc=berrange@redhat.com \
    --cc=brijesh.singh@amd.com \
    --cc=hetz@hetz.biz \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=phrdina@redhat.com \
    --cc=qemu-devel@nongnu.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 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).