[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOjd+7TxunlKSjTA@nvidia.com>
Date: Fri, 25 Aug 2023 13:59:39 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Reinette Chatre <reinette.chatre@...el.com>
Cc: "Tian, Kevin" <kevin.tian@...el.com>,
"yishaih@...dia.com" <yishaih@...dia.com>,
"shameerali.kolothum.thodi@...wei.com"
<shameerali.kolothum.thodi@...wei.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Jiang, Dave" <dave.jiang@...el.com>,
"Liu, Jing2" <jing2.liu@...el.com>,
"Raj, Ashok" <ashok.raj@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"tom.zanussi@...ux.intel.com" <tom.zanussi@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 2/3] vfio/ims: Support emulated interrupts
On Fri, Aug 25, 2023 at 09:55:52AM -0700, Reinette Chatre wrote:
> Thank you very much for your guidance. Instead of Jason's expectation that
> IMS would be a backend of MSI-X this will change to IMS and MSI-X both being
> a backend to a new interface. It is difficult for me to envision the end
> result so I will work on an implementation based on my understanding of
> your proposal that we can use for further discussion.
I think the point is that emulating MSI-X is kind of tricky and should
be common VFIO code, regardless of what path it takes.
So I would expect some library code to do this, entry points the
vfio_device can hook into its callbacks (eg config space and rw of a
page)
Then the other side would connect to the physical implementation,
sw,ims,msi-x,future
Jason
Powered by blists - more mailing lists