From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Richard Henderson <rth@twiddle.net>,
David Hildenbrand <david@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>, Thomas Huth <thuth@redhat.com>,
Collin Walling <walling@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] s390x: always provide pci support
Date: Mon, 11 Feb 2019 15:57:14 +0100 [thread overview]
Message-ID: <20190211155714.0b657552.cohuck@redhat.com> (raw)
In-Reply-To: <8d2c66ce-fdc6-d12b-256c-1760330c4360@de.ibm.com>
On Mon, 11 Feb 2019 15:05:46 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 11.02.2019 12:32, Cornelia Huck wrote:
> > We tried to make pci support optional on s390x in the past;
> > unfortunately, we still require the s390 phb to be created
> > unconditionally due to backwards compatibility issues.
> >
> > Instead of sinking more effort into this (including compat
> > handling for older machines etc.) for non-obvious gains, let's
> > just make CONFIG_PCI something that is always set on s390x.
> >
> > Note that you can still fence off pci for the _guest_ if you
> > provide a cpu model without the zpci feature.
> >
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> The previous attempts of making it configurable caused more pain than
> benefit.
I think we've reaped all the benefits of the attempt already (making
relevant instructions check for the zpci feature bit).
next prev parent reply other threads:[~2019-02-11 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 11:32 [Qemu-devel] [PATCH] s390x: always provide pci support Cornelia Huck
2019-02-11 12:02 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-02-11 13:51 ` [Qemu-devel] " David Hildenbrand
2019-02-11 14:05 ` Christian Borntraeger
2019-02-11 14:57 ` Cornelia Huck [this message]
2019-02-11 15:01 ` Cornelia Huck
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=20190211155714.0b657552.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.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).