From: Jason Gunthorpe <jgg@nvidia.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"yishaih@nvidia.com" <yishaih@nvidia.com>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Liu, Jing2" <jing2.liu@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"tom.zanussi@linux.intel.com" <tom.zanussi@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 2/3] vfio/ims: Support emulated interrupts
Date: Fri, 25 Aug 2023 13:59:39 -0300 [thread overview]
Message-ID: <ZOjd+7TxunlKSjTA@nvidia.com> (raw)
In-Reply-To: <f46f44cd-2961-7731-d5a2-483c9e5189d1@intel.com>
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
next prev parent reply other threads:[~2023-08-25 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 16:15 [RFC PATCH 0/3] vfio/ims: Back guest interrupts from Interrupt Message Store (IMS) Reinette Chatre
2023-08-24 16:15 ` [RFC PATCH 1/3] vfio/pci: Introduce library allocating " Reinette Chatre
2023-08-24 16:15 ` [RFC PATCH 2/3] vfio/ims: Support emulated interrupts Reinette Chatre
2023-08-24 16:33 ` Jason Gunthorpe
2023-08-24 17:19 ` Reinette Chatre
2023-08-25 3:05 ` Tian, Kevin
2023-08-25 16:55 ` Reinette Chatre
2023-08-25 16:59 ` Jason Gunthorpe [this message]
2023-08-25 17:14 ` Reinette Chatre
2023-08-24 16:15 ` [RFC PATCH 3/3] vfio/ims: Add helper that returns IMS index Reinette Chatre
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=ZOjd+7TxunlKSjTA@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=dave.jiang@intel.com \
--cc=fenghua.yu@intel.com \
--cc=jing2.liu@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=tom.zanussi@linux.intel.com \
--cc=yishaih@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.