public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>,
	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, alex.williamson@redhat.com,
	cohuck@redhat.com
Subject: Re: [PATCH v2] KVM: s390: pci: Hook to access KVM lowlevel from VFIO
Date: Tue, 23 Aug 2022 13:54:21 +0200	[thread overview]
Message-ID: <62420273c48f2edecf12ec8784ef03adadea2a4b.camel@linux.ibm.com> (raw)
In-Reply-To: <6d11d3b5-a313-8e2b-2f38-44c5a4a63a28@linux.ibm.com>

On Tue, 2022-08-23 at 09:25 +0200, Janosch Frank wrote:
> On 8/19/22 14:29, 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>
> > Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
> > Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
> > Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> > Fixes: 09340b2fca007 ("KVM: s390: pci: add routines to start/stop interpretive execution")
> > Cc: <stable@vger.kernel.org>
> 
> Acked-by: Janosch Frank <frankja@linux.ibm.com>
> 
> @Niklas @Matt: Since the patches that introduced the PCI interpretation 
> went via the KVM tree I'll also move this patch via the KVM tree.

Sounds good, thanks.


      reply	other threads:[~2022-08-23 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 12:29 [PATCH v2] KVM: s390: pci: Hook to access KVM lowlevel from VFIO Pierre Morel
2022-08-19 21:10 ` Randy Dunlap
2022-08-22  8:36   ` Pierre Morel
2022-08-23  7:25 ` Janosch Frank
2022-08-23 11:54   ` Niklas Schnelle [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=62420273c48f2edecf12ec8784ef03adadea2a4b.camel@linux.ibm.com \
    --to=schnelle@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cohuck@redhat.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