From: Cornelia Huck <cohuck@redhat.com>
To: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org, borntraeger@de.ibm.com, agraf@suse.de,
pasic@linux.vnet.ibm.com, jjherne@linux.vnet.ibm.com,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] s390x: create a compat s390 phb for <=2.10
Date: Wed, 27 Sep 2017 12:56:06 +0200 [thread overview]
Message-ID: <20170927125606.65dc514d.cohuck@redhat.com> (raw)
In-Reply-To: <e8bef299-5501-a59d-aba3-5a338227966e@linux.vnet.ibm.com>
On Wed, 27 Sep 2017 18:25:00 +0800
Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
> 在 2017/9/27 下午5:47, Cornelia Huck 写道:
> > On Tue, 26 Sep 2017 20:40:25 +0200
> > David Hildenbrand <david@redhat.com> wrote:
> >> I'd really really really (did I mention really?) favor something like a
> >> dummy device, because we could easily handle the !CONFIG_PCI case then.
> >>
> >> All these compat options and conditions will kill us someday... we're
> >> already patching around that whole stuff way too much.
> >>
> >> If we ever unconditionally created a device, we should keep doing so.
> > Yes, that whole thing is horrible, especially interaction with compat
> > machines.
> >
> > Do you have an idea on how to create such a dummy device (without
> > having to effectively copy a lot of configured-out code)?
> >
> >
> How about in s390_pcihost_hot_plug() we check s390_has_feat(zpci)?
> If no zpci feature, we avoid plugging any pci device.
> Then we could always create phb.
> I think pcibus's vmstate is only data to migrate.
That's still problematic if CONFIG_PCI is off. I currently don't have a
better idea than either disallowing compat machines on builds without
pci, or using a dummy device...
next prev parent reply other threads:[~2017-09-27 10:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 16:20 [Qemu-devel] [PATCH 0/1] s390x: more zpci compat fun Cornelia Huck
2017-09-26 16:20 ` [Qemu-devel] [PATCH 1/1] s390x: create a compat s390 phb for <=2.10 Cornelia Huck
2017-09-26 17:07 ` Christian Borntraeger
2017-09-26 18:40 ` David Hildenbrand
2017-09-27 9:47 ` Cornelia Huck
2017-09-27 10:25 ` Yi Min Zhao
2017-09-27 10:56 ` Cornelia Huck [this message]
2017-09-27 10:59 ` Christian Borntraeger
2017-09-27 12:21 ` David Hildenbrand
2017-09-27 12:26 ` Christian Borntraeger
2017-09-27 14:28 ` Dr. David Alan Gilbert
2017-09-27 14:46 ` Cornelia Huck
2017-09-27 14:49 ` Dr. David Alan Gilbert
2017-09-27 15:03 ` Cornelia Huck
2017-09-28 10:34 ` Christian Borntraeger
2017-09-28 10:41 ` Christian Borntraeger
2017-09-28 12:07 ` Cornelia Huck
2017-09-28 12:17 ` Christian Borntraeger
2017-09-28 12:27 ` Cornelia Huck
2017-09-28 12:33 ` David Hildenbrand
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=20170927125606.65dc514d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zyimin@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).