From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
David Hildenbrand <david@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.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 16:01:23 +0100 [thread overview]
Message-ID: <20190211160123.1bb4feaf.cohuck@redhat.com> (raw)
In-Reply-To: <20190211113255.3837-1-cohuck@redhat.com>
On Mon, 11 Feb 2019 12:32:55 +0100
Cornelia Huck <cohuck@redhat.com> 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>
> ---
> Follow-up patch to the discussion around "hw/s390x: Fix the function
> arguments in the pci stub file". I've done a quick sanity test with
> tcg only so far.
> ---
> hw/s390x/Makefile.objs | 3 +-
> hw/s390x/s390-pci-stub.c | 77 -------------------------------------
> hw/s390x/s390-virtio-ccw.c | 4 --
> target/s390x/cpu_models.c | 5 ---
> target/s390x/gen-features.c | 1 -
> target/s390x/kvm.c | 4 +-
> 6 files changed, 2 insertions(+), 92 deletions(-)
> delete mode 100644 hw/s390x/s390-pci-stub.c
Queued to s390-next.
prev parent reply other threads:[~2019-02-11 15:02 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
2019-02-11 15:01 ` Cornelia Huck [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=20190211160123.1bb4feaf.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).