From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, mjrosato@linux.ibm.com
Cc: rdunlap@infradead.org, linux-kernel@vger.kernel.org,
lkp@intel.com, borntraeger@linux.ibm.com, farman@linux.ibm.com,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
gor@linux.ibm.com, hca@linux.ibm.com, frankja@linux.ibm.com
Subject: Re: [PATCH] KVM: s390: pci: Hook to access KVM lowlevel from VFIO
Date: Fri, 19 Aug 2022 12:42:48 +0200 [thread overview]
Message-ID: <ae19135f580e1f510e99d1567514cc2dfe3571be.camel@linux.ibm.com> (raw)
In-Reply-To: <0d7d055d-f323-acba-cb79-f859b5e182b4@linux.ibm.com>
On Fri, 2022-08-19 at 10:44 +0200, Pierre Morel wrote:
>
> On 8/19/22 09:14, Niklas Schnelle wrote:
> > On Thu, 2022-08-18 at 18:46 +0200, Pierre Morel wrote:
> > > We have a cross dependency between KVM and VFIO when using
> > > s390 vfio_pci_zdev extensions for PCI passthrough
> > > To be able to keep both subsystem modular we add a registering
> > > hook inside the S390 core code.
> > >
> > > This fixes a build problem when VFIO is built-in and KVM is built
> > > as a module.
> > >
> > > Reported-by: Randy Dunlap <rdunlap@infradead.org>
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> > > Fixes: 09340b2fca007 ("KVM: s390: pci: add routines to start/stop inter..")
> >
> > Please don't shorten the Fixes tag, the subject line is likely also
> > checked by some automated tools. It's okay for this line to be over the
> > column limit and checkpatch.pl --strict also accepts it.
> >
>
> OK
>
> > > Cc: <stable@vger.kernel.org>
> > > ---
> > > arch/s390/include/asm/kvm_host.h | 17 ++++++-----------
> > > arch/s390/kvm/pci.c | 10 ++++++----
> > > arch/s390/pci/Makefile | 2 ++
> > > arch/s390/pci/pci_kvm_hook.c | 11 +++++++++++
> > > drivers/vfio/pci/vfio_pci_zdev.c | 8 ++++++--
> > > 5 files changed, 31 insertions(+), 17 deletions(-)
> > > create mode 100644 arch/s390/pci/pci_kvm_hook.c
> > >
> > >
> > ---8<---
> > >
> > > kvm_put_kvm(kvm);
> > > }
> > > -EXPORT_SYMBOL_GPL(kvm_s390_pci_unregister_kvm);
> > >
> > > void kvm_s390_pci_init_list(struct kvm *kvm)
> > > {
> > > @@ -678,6 +678,8 @@ int kvm_s390_pci_init(void)
> > >
> > > spin_lock_init(&aift->gait_lock);
> > > mutex_init(&aift->aift_lock);
> > > + zpci_kvm_hook.kvm_register = kvm_s390_pci_register_kvm;
> > > + zpci_kvm_hook.kvm_unregister = kvm_s390_pci_unregister_kvm;
> > >
> > > return 0;
> > > }
> > > diff --git a/arch/s390/pci/Makefile b/arch/s390/pci/Makefile
> > > index bf557a1b789c..c02dbfb415d9 100644
> > > --- a/arch/s390/pci/Makefile
> > > +++ b/arch/s390/pci/Makefile
> > > @@ -7,3 +7,5 @@ obj-$(CONFIG_PCI) += pci.o pci_irq.o pci_dma.o pci_clp.o pci_sysfs.o \
> > > pci_event.o pci_debug.o pci_insn.o pci_mmio.o \
> > > pci_bus.o
> > > obj-$(CONFIG_PCI_IOV) += pci_iov.o
> > > +
> > > +obj-y += pci_kvm_hook.o
> >
> > I thought we wanted to compile this only for CONFIG_PCI?
>
> Ah sorry, that is indeed what I understood with Matt but then I
> misunderstood your own answer from yesterday.
> I change to
> obj-$(CONFIG_PCI) += pci_kvm_hook.o
>
> > > diff --git a/arch/s390/pci/pci_kvm_hook.c b/arch/s390/pci/pci_kvm_hook.c
> > > new file mode 100644
> > > index 000000000000..ff34baf50a3e
> > ---8<---
> >
Ok with the two things above plus the comment by Matt incorporated:
Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
next prev parent reply other threads:[~2022-08-19 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:46 [PATCH] KVM: s390: pci: Hook to access KVM lowlevel from VFIO Pierre Morel
2022-08-18 20:38 ` Matthew Rosato
2022-08-18 20:54 ` Pierre Morel
2022-08-19 7:14 ` Niklas Schnelle
2022-08-19 8:44 ` Pierre Morel
2022-08-19 10:42 ` Niklas Schnelle [this message]
2022-08-19 11:42 ` Pierre Morel
2022-08-19 11:49 ` Niklas Schnelle
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 20:22 [PATCH] vfio-pci/zdev: require KVM to be built-in Pierre Morel
2022-08-18 10:23 ` [PATCH] KVM: s390: pci: Hook to access KVM lowlevel from VFIO Pierre Morel
2022-08-18 13:33 ` Matthew Rosato
2022-08-18 14:06 ` Pierre Morel
2022-08-18 14:20 ` Niklas Schnelle
2022-08-18 15:13 ` Matthew Rosato
2022-08-18 15:22 ` Niklas Schnelle
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=ae19135f580e1f510e99d1567514cc2dfe3571be.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mjrosato@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=rdunlap@infradead.org \
/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