From: Jason Gunthorpe <jgg@nvidia.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com,
kevin.tian@intel.com, alex.williamson@redhat.com,
kvm@vger.kernel.org, dave.jiang@intel.com, jing2.liu@intel.com,
ashok.raj@intel.com, fenghua.yu@intel.com,
tom.zanussi@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] vfio/ims: Support emulated interrupts
Date: Thu, 24 Aug 2023 13:33:06 -0300 [thread overview]
Message-ID: <ZOeGQrRCqf87Joec@nvidia.com> (raw)
In-Reply-To: <7a08c41e1825095814f8c35854d3938c084b2368.1692892275.git.reinette.chatre@intel.com>
On Thu, Aug 24, 2023 at 09:15:21AM -0700, Reinette Chatre wrote:
> Access from a guest to a virtual device may be either 'direct-path',
> where the guest interacts directly with the underlying hardware,
> or 'intercepted path' where the virtual device emulates operations.
>
> Support emulated interrupts that can be used to handle 'intercepted
> path' operations. For example, a virtual device may use 'intercepted
> path' for configuration. Doing so, configuration requests intercepted
> by the virtual device driver are handled within the virtual device
> driver with completion signaled to the guest without interacting with
> the underlying hardware.
Why does this have anything to do with IMS? I thought the point here
was that IMS was some back end to the MSI-X emulation - should a
purely emulated interrupt logically be part of the MSI code, not IMS?
Jason
next prev parent reply other threads:[~2023-08-24 16:33 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 [this message]
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
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=ZOeGQrRCqf87Joec@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.