From: Eduardo Habkost <ehabkost@redhat.com>
To: Jiri Denemark <jdenemar@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] CPU model versioning separate from machine type versioning ?
Date: Fri, 29 Jun 2018 10:53:37 -0300 [thread overview]
Message-ID: <20180629135337.GK7451@localhost.localdomain> (raw)
In-Reply-To: <20180629060604.GA5072@orkuz.home>
On Fri, Jun 29, 2018 at 08:06:04AM +0200, Jiri Denemark wrote:
> On Thu, Jun 28, 2018 at 16:23:53 -0300, Eduardo Habkost wrote:
> > On Thu, Jun 28, 2018 at 07:59:38PM +0100, Dr. David Alan Gilbert wrote:
[...]
> > > Would you restrict the combinations to cut down the test matrix - e.g.
> > > not allow Haswell-3.0.0 on anything prior to a 2.12 machine type?
> >
> > Not sure if it would be worth the extra complexity: we would need
> > an interface to tell libvirt which CPU models are usable on which
> > machine-types.
>
> In case we do this, libvirt should already by ready for it on the API
> level for both reporting capabilities and CPU comparison/baseline. All
> these APIs already accept machine type as an optional parameter so that
> different results can be provided depending on machine type.
Does it have an abstraction that can already represent "CPU model
$C can/can't be used with machine-type $M"?
--
Eduardo
next prev parent reply other threads:[~2018-06-29 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 15:45 [Qemu-devel] CPU model versioning separate from machine type versioning ? Daniel P. Berrangé
2018-06-28 18:59 ` Dr. David Alan Gilbert
2018-06-28 19:23 ` Eduardo Habkost
2018-06-29 6:06 ` [Qemu-devel] [libvirt] " Jiri Denemark
2018-06-29 13:53 ` Eduardo Habkost [this message]
2018-06-29 10:10 ` [Qemu-devel] " Daniel P. Berrangé
2018-06-28 19:52 ` Eduardo Habkost
2018-06-29 8:53 ` Dr. David Alan Gilbert
2018-06-29 10:19 ` Daniel P. Berrangé
2018-06-29 17:36 ` Eduardo Habkost
2018-06-29 10:14 ` Daniel P. Berrangé
2018-06-29 12:12 ` Jiri Denemark
2018-06-29 12:16 ` Daniel P. Berrangé
2018-06-29 14:06 ` Eduardo Habkost
2018-06-29 17:42 ` Eduardo Habkost
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=20180629135337.GK7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@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 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.