From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>
Cc: Collin Walling <walling@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/s390x: Fix the function arguments in the pci stub file
Date: Thu, 31 Jan 2019 19:08:39 +0100 [thread overview]
Message-ID: <c60dd137-ca05-85cd-78ca-d22c79ccd85e@redhat.com> (raw)
In-Reply-To: <538ee62b-293d-f053-4bd2-76bf166388e1@redhat.com>
On 31/01/19 19:00, Thomas Huth wrote:
>>> (and the prototypes in the header) anymore, so if you try to compile s390x
>>> without CONFIG_PCI, the build currently fails.
>>>
>> Fixes: 468a93898a97 ("s390x/pci: pass the retaddr to all PCI instructions")
>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>> hw/s390x/s390-pci-stub.c | 16 +++++++++-------
>>> 1 file changed, 9 insertions(+), 7 deletions(-)
>> This file seems to be in danger of bitrot. Do you think it'll be easier
>> to test rarely used configs like that after we switch to Kconfig?
> I hope so, yes. There will be a new --without-default-devices options
> for "configure" (which matches "make allnoconfig" from the kernel) - if
> we do it right in the Kconfig file for s390x, it should be possible to
> catch this problem with that option.
Yes, it will be in .travis.yml too.
Right now there is a "select PCI" in the hw/s390x/Kconfig file, but
probably it's best to add a config S390_ZPCI with "default y if
S390_CCW_VIRTIO" and "select PCI" in it. Not a blocker, but I can
integrate it if you send me a fixup patch.
Paolo
next prev parent reply other threads:[~2019-01-31 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 17:47 [Qemu-devel] [PATCH] hw/s390x: Fix the function arguments in the pci stub file Thomas Huth
2019-01-31 17:56 ` Cornelia Huck
2019-01-31 18:00 ` Thomas Huth
2019-01-31 18:08 ` Paolo Bonzini [this message]
2019-02-01 6:14 ` Thomas Huth
2019-02-01 6:46 ` Thomas Huth
2019-02-01 8:23 ` Cornelia Huck
2019-02-11 10:48 ` Cornelia Huck
2019-02-11 10:54 ` Thomas Huth
2019-02-11 11:04 ` Cornelia Huck
2019-02-11 11:17 ` Thomas Huth
2019-02-11 11:20 ` 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=c60dd137-ca05-85cd-78ca-d22c79ccd85e@redhat.com \
--to=pbonzini@redhat.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--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).