qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Hetz Ben Hamo <hetz@hetz.biz>, qemu-devel@nongnu.org
Cc: libvir-list@redhat.com, Eduardo Habkost <ehabkost@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [libvirt] CPU Support
Date: Wed, 18 Jul 2018 10:50:34 +0100	[thread overview]
Message-ID: <20180718095034.GJ9812@redhat.com> (raw)
In-Reply-To: <CANhJxzwZny93TOTKTpEoThN8bnw1tXENPH_S60wczUAQodBMNw@mail.gmail.com>

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.

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-07-18  9:50 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 ` Daniel P. Berrangé [this message]
2018-07-18 10:18   ` [Qemu-devel] [libvirt] CPU Support Pavel Hrdina
2018-07-18 13:49     ` Eduardo Habkost
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=20180718095034.GJ9812@redhat.com \
    --to=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=hetz@hetz.biz \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@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).