qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Eric Blake <eblake@redhat.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: Li Zhang <zhlcindy@linux.vnet.ibm.com>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Hong-Hua.Yin@freescale.com" <Hong-Hua.Yin@freescale.com>,
	"david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] QEMU: PCI bus name on PowerPC platforms
Date: Fri, 11 Apr 2014 14:29:05 +0200	[thread overview]
Message-ID: <5347E011.9080308@suse.de> (raw)
In-Reply-To: <5347DFB9.1070401@redhat.com>


On 11.04.14 14:27, Eric Blake wrote:
> On 04/11/2014 05:40 AM, Alexey Kardashevskiy wrote:
>
>>> but AFAICT nothing got merged to change this for all the other boards as
>>> discussed here :-(  This is painful for libvirt since we have todo even
>>> more hacks triggered off machine names now, instead of being able to
>>> rely on pci.0 naming as we hoped.
>> Sorry, I am missing the point.
>> How could making a platform similar to many others force you to do more
>> hacks, not less?
> As mentioned in the thread here:
> https://lists.gnu.org/archive/html/qemu-devel/2014-04/threads.html#01565
>
> If there is a way to query via QMP to see which naming scheme is in
> effect, there are no hacks involved - we just ask and get it right.
>
> If ALL platforms behave identically as of a certain release, we have a
> minimal hack - catering to releases older than that, where a downstream
> backport may have to tweak how we detect older releases, but it is only
> a single place to be hacked.
>
> But with just this patch, you have caused the situation where it is
> neither introspectible, nor consistent across qemu versions.  The only
> way to code that up in libvirt is to do MULTIPLE version checks and
> correlate it with architecture checks - and that's the hack we don't
> want to have to support.  Every single version check done in lieu of
> proper feature introspection is yet one more pain point when features
> get backported across version numbers downstream.

So how do you support -M ppce500 which also uses pci.0 and runs on 
(booke) ppc64?


Alex

  reply	other threads:[~2014-04-11 12:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 10:42 [Qemu-devel] QEMU: PCI bus name on PowerPC platforms Hong-Hua.Yin
2014-03-05 11:43 ` Alexey Kardashevskiy
2014-03-05 13:35   ` Paolo Bonzini
2014-03-05 13:40     ` Daniel P. Berrange
2014-03-05 14:12       ` Paolo Bonzini
2014-03-05 14:21         ` Daniel P. Berrange
2014-03-05 14:33           ` Paolo Bonzini
2014-03-05 14:40             ` Daniel P. Berrange
2014-04-10  9:24             ` Daniel P. Berrange
2014-04-11 11:40               ` Alexey Kardashevskiy
2014-04-11 12:27                 ` Eric Blake
2014-04-11 12:29                   ` Alexander Graf [this message]
2014-03-05 14:35           ` Andreas Färber
2014-03-05 14:38             ` Andreas Färber
2014-03-05 14:44               ` Paolo Bonzini
2014-03-05 15:15     ` Alexey Kardashevskiy
2014-03-06  2:25       ` Hong-Hua.Yin
2014-03-06  7:04       ` Hong-Hua.Yin
2014-03-06  7:07         ` Alexey Kardashevskiy
2014-03-06  7:21           ` Hong-Hua.Yin

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=5347E011.9080308@suse.de \
    --to=agraf@suse.de \
    --cc=Hong-Hua.Yin@freescale.com \
    --cc=aik@ozlabs.ru \
    --cc=berrange@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=zhlcindy@linux.vnet.ibm.com \
    /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).