From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
David Hildenbrand <david@redhat.com>,
Yi Min Zhao <zyimin@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, agraf@suse.de, pasic@linux.vnet.ibm.com,
jjherne@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/1] s390x: create a compat s390 phb for <=2.10
Date: Thu, 28 Sep 2017 14:27:45 +0200 [thread overview]
Message-ID: <20170928142745.2ab4da2a.cohuck@redhat.com> (raw)
In-Reply-To: <ebe58241-049a-bb4e-acee-8ef4c12e2d3a@de.ibm.com>
On Thu, 28 Sep 2017 14:17:54 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> I see no point if PCI disable machines. There is no non-PCI x86 machine
> besides the isapc. But this has no version whatsoever so it certainly
> is not made for being migrated.
> As far as I can see and we would make things much more complex.
>
> non-PCI will trigger other issues. e.g. zpci and aen is part of the z14 cpu model
> since 2.10. Really this is not helping, its making things worse.
What about creating the phb depending upon pci_available? Has no impact
for normal builds unless you muck around manually...
> If you really want to avoid PCI for whatever redhat is doing, can't you just hide
> it in a rhel specific machine (which you seem to have anyway for x86 and power)?
...but makes it easier to disable it correctly, if wanted.
next prev parent reply other threads:[~2017-09-28 12:28 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
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 [this message]
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=20170928142745.2ab4da2a.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 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.