qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Marc Hartmayer <mhartmay@linux.vnet.ibm.com>,
	libvir-list@redhat.com, qemu-devel@nongnu.org
Cc: Jiri Denemark <jdenemar@redhat.com>,
	Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
	"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [libvirt] Question about the host-model CPU mode
Date: Fri, 20 Oct 2017 17:14:09 +0200	[thread overview]
Message-ID: <b3aa4c20-cbcc-5757-06b1-eba1d3903778@redhat.com> (raw)
In-Reply-To: <c05abe6e-2ba6-a678-fe51-4c0c2f828b7e@linux.vnet.ibm.com>


> 
> I intend to put some brain-power in this too. Probably next week.
> 
> My general impression is, that I have a at places different understanding
> of how things should work compared to David. Especially when it comes
> to this concept of persistent copying, and also an end-user-digestible
> definition of what host-model does. (I think this with copying capabilities
> from whatever xml which is subject to convoluted caching is a bit too
> hard to digest for an end user not involved in the development of qemu
> and libvirt).

When reading the doc I was assuming that it would be a persistent copy.
But it would only fix part of the issue.

In the end, it specifies quite clearly what is copied. And if that is
not runnable with the selected machine, bad luck. Therefore ...

> 
> I had a conversation with Boris a couple of hours ago, and it seems, things
> are pretty convoluted.
> 
> If I understand the train of thought here (David) it can be summarized like this:
> For a certain QEMU binary no aspect of the cpu-models may depend on the
> machine type. In particular, compat properties and compat handling is
> not alowed to alter cpu-models (whether the available cpu models nor the
> capabilities of each of these).

... I always recommended avoiding such compatibility settings in the
machine. But before we had CPU models it was really all we had. No we
should let go of it.

We might be able to fix this one (gs) and take care of it in the future,
but ...

> 
> This we would have to make a part of the external interface. That way
> one could be sure that the 'cpu capabilities' are machine-type independent
> (that is, the same for all the machine types).

... the problem is once nasty stuff like zPCI comes in place. If we ever
have (other?) machine dependent stuff that toggles CPU features, we can
only try limit the damage.

> 
> Or did I get this completely wrong? (Based on the answer branches my
> think).

Not at all.

> 
> Halil
> 


-- 

Thanks,

David

      reply	other threads:[~2017-10-20 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y3oqugm7.fsf@marc-ibm.boeblingen.de.ibm.com>
     [not found] ` <20171005121115.GD3946746@orkuz.home>
     [not found]   ` <87y3ok7n2n.fsf@marc-ibm.boeblingen.de.ibm.com>
     [not found]     ` <20171012120714.GA314661@orkuz.home>
2017-10-20 11:09       ` [Qemu-devel] [libvirt] Question about the host-model CPU mode Marc Hartmayer
2017-10-20 11:37         ` David Hildenbrand
2017-10-20 12:50           ` Jiri Denemark
2017-10-20 13:04             ` David Hildenbrand
2017-10-23  7:25               ` Jiri Denemark
2017-10-20 12:43         ` Jiri Denemark
2017-10-20 13:16         ` David Hildenbrand
2017-10-20 13:36           ` Christian Borntraeger
2017-10-20 13:43             ` David Hildenbrand
2017-10-20 13:49               ` Christian Borntraeger
2017-10-20 13:51                 ` David Hildenbrand
2017-10-20 14:02                   ` Christian Borntraeger
2017-10-20 14:06                     ` David Hildenbrand
2017-10-20 14:12                       ` Christian Borntraeger
2017-10-20 14:58                         ` Halil Pasic
2017-10-20 15:14                           ` David Hildenbrand [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=b3aa4c20-cbcc-5757-06b1-eba1d3903778@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=fiuczy@linux.vnet.ibm.com \
    --cc=jdenemar@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=mhartmay@linux.vnet.ibm.com \
    --cc=mihajlov@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.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).