qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
	qemu-s390x@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Alex Williamson" <alex.williamson@redhat.com>
Subject: Re: [PATCH for-5.2] s390x: fix build for --without-default-devices
Date: Tue, 3 Nov 2020 09:06:01 -0500	[thread overview]
Message-ID: <7653f62a-61fa-139b-4702-85045fac72ad@linux.ibm.com> (raw)
In-Reply-To: <deff16f8-028e-32dc-89d1-29a5881f07be@linux.ibm.com>

On 11/3/20 8:21 AM, Matthew Rosato wrote:
> On 11/3/20 7:32 AM, Cornelia Huck wrote:
>> s390-pci-vfio.c calls into the vfio code, so we need it to be
>> built conditionally on vfio (which implies CONFIG_LINUX).
>>
>> Reported-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Fixes: cd7498d07fbb ("s390x/pci: Add routine to get the vfio dma 
>> available count")
>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> 
> Good catch.  Did a test compile and this clearly works, but I'm 
> wondering if it should be checking against CONFIG_VFIO_PCI?
> 

I guess looking at it again, there's nothing in s390-vfio-pci today that 
strictly needs it, just the VIOPCIDevice struct defined in hw/vfio/pci.h 
and that should still be available even if CONFIG_VFIO_PCI=n (not like 
you'll be able to create these devices without CONFIG_VFIO or 
CONFIG_VFIO_PCI anyway).

Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>

>> ---
>>   hw/s390x/meson.build             | 2 +-
>>   include/hw/s390x/s390-pci-vfio.h | 3 ++-
>>   2 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/s390x/meson.build b/hw/s390x/meson.build
>> index f4663a835514..2a7818d94b94 100644
>> --- a/hw/s390x/meson.build
>> +++ b/hw/s390x/meson.build
>> @@ -27,7 +27,7 @@ s390x_ss.add(when: 'CONFIG_KVM', if_true: files(
>>   ))
>>   s390x_ss.add(when: 'CONFIG_S390_CCW_VIRTIO', if_true: 
>> files('s390-virtio-ccw.c'))
>>   s390x_ss.add(when: 'CONFIG_TERMINAL3270', if_true: files('3270-ccw.c'))
>> -s390x_ss.add(when: 'CONFIG_LINUX', if_true: files('s390-pci-vfio.c'))
>> +s390x_ss.add(when: 'CONFIG_VFIO', if_true: files('s390-pci-vfio.c'))
>>   virtio_ss = ss.source_set()
>>   virtio_ss.add(files('virtio-ccw.c'))
>> diff --git a/include/hw/s390x/s390-pci-vfio.h 
>> b/include/hw/s390x/s390-pci-vfio.h
>> index c7984905b3b7..ff708aef500f 100644
>> --- a/include/hw/s390x/s390-pci-vfio.h
>> +++ b/include/hw/s390x/s390-pci-vfio.h
>> @@ -13,8 +13,9 @@
>>   #define HW_S390_PCI_VFIO_H
>>   #include "hw/s390x/s390-pci-bus.h"
>> +#include CONFIG_DEVICES
>> -#ifdef CONFIG_LINUX
>> +#ifdef CONFIG_VFIO
>>   bool s390_pci_update_dma_avail(int fd, unsigned int *avail);
>>   S390PCIDMACount *s390_pci_start_dma_count(S390pciState *s,
>>                                             S390PCIBusDevice *pbdev);
>>
> 



  reply	other threads:[~2020-11-03 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 12:32 [PATCH for-5.2] s390x: fix build for --without-default-devices Cornelia Huck
2020-11-03 13:21 ` Matthew Rosato
2020-11-03 14:06   ` Matthew Rosato [this message]
2020-11-03 13:42 ` Philippe Mathieu-Daudé

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=7653f62a-61fa-139b-4702-85045fac72ad@linux.ibm.com \
    --to=mjrosato@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.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).