[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9kqNnJ5ayCQSW9z@nvidia.com>
Date: Tue, 31 Jan 2023 10:48:22 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Anthony Krowiak <akrowiak@...ux.ibm.com>
Cc: Yi Liu <yi.l.liu@...el.com>, alex.williamson@...hat.com,
pbonzini@...hat.com, mjrosato@...ux.ibm.com, kevin.tian@...el.com,
cohuck@...hat.com, farman@...ux.ibm.com, pmorel@...ux.ibm.com,
borntraeger@...ux.ibm.com, frankja@...ux.ibm.com,
imbrenda@...ux.ibm.com, david@...hat.com, jjherne@...ux.ibm.com,
pasic@...ux.ibm.com, zhenyuw@...ux.intel.com, zhi.a.wang@...el.com,
seanjc@...gle.com, linux-s390@...r.kernel.org, kvm@...r.kernel.org,
intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm/vfio: Fix potential deadlock on vfio group_lock
On Tue, Jan 31, 2023 at 09:46:18AM -0500, Anthony Krowiak wrote:
> > Maybe you should split that lock and have a dedicated apcb lock?
>
> I don't think that would suffice for taking the vCPUs out of SIE.
Then I think we have to keep this patch and also do Matthew's patch to
keep kvm refs inside vfio as well.
Jason
Powered by blists - more mailing lists