[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210714184301.GA543781@nvidia.com>
Date: Wed, 14 Jul 2021 15:43:01 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: Tony Krowiak <akrowiak@...ux.ibm.com>, alex.williamson@...hat.com,
Halil Pasic <pasic@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, cohuck@...hat.com,
pasic@...ux.vnet.ibm.com, jjherne@...ux.ibm.com,
kwankhede@...dia.com, frankja@...ux.ibm.com, david@...hat.com,
imbrenda@...ux.ibm.com, hca@...ux.ibm.com
Subject: Re: [PATCH] s390/vfio-ap: do not open code locks for
VFIO_GROUP_NOTIFY_SET_KVM notification
On Wed, Jul 14, 2021 at 07:56:42PM +0200, Christian Borntraeger wrote:
> > > In any event, I don't care anymore - please just get this merged, to
> > > AlexW's tree so I don't have conflicts with the rest of the ap changes
> > > for VFIO I've got queued up.
> >
> > Christian, can you merge this with AlexW's tree? Halil suggested
> > the 'fixes' and 'cc stable' tags ought to be removed, do I need
> > to post another version or can you take those out when merging?
>
> Normally this would go via the KVM/s390 or s390 tree (as Alex did
> not want to handle s390 vfio devices).
I would like to move the vfio driver(s) out of driver/s390 and over to
vfio. This is the normal kernel process and after some discussion we
decided with Thomas Gleixner that this is the right thing to do for
things like the new Intel mdev.
But that can be another discussion, thanks
> Alex, as Jason is waiting for this to be in your tree could you take
> this patch via your tree ?(please remove cc stable and Fixes for now
> I want this to settle a bit).
>
> To carry this patch in your tree with my kvm/s390 and s390 maintainer hat
> Acked-by: Christian Borntraeger <borntraeger@...ibm.com>
Great!
Jason
Powered by blists - more mailing lists