From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dominik Behr <dbehr@chromium.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Grzegorz Jaszczyk <jaz@semihalf.com>,
linux-kernel@vger.kernel.org, dmy@semihalf.com, tn@semihalf.com,
upstream@semihalf.com, dtor@google.com, kevin.tian@intel.com,
cohuck@redhat.com, abhsahu@nvidia.com, yishaih@nvidia.com,
yi.l.liu@intel.com, kvm@vger.kernel.org, libvir-list@redhat.com
Subject: Re: [PATCH] vfio/pci: Propagate ACPI notifications to the user-space
Date: Thu, 9 Mar 2023 14:25:13 -0400 [thread overview]
Message-ID: <ZAokiR4EC3gFAuJ1@ziepe.ca> (raw)
In-Reply-To: <CABUrSUAbJJJfGYQuXe-k+partE8UebEvK47zuGXEAtdAjg-yPA@mail.gmail.com>
On Wed, Mar 08, 2023 at 05:51:32PM -0800, Dominik Behr wrote:
> All other ACPI events that are available to userspace are on netlink already.
> As for translation of ACPI paths. It is sort of a requirement for VMM
> to translate the PCI path from host to guest because the PCI device
> tree in the guest is totally different already. The same follows for
> ACPI paths.
>
> What would you propose instead of netlink?
> Sysfs entry for VFIO PCI device that accepts eventfd and signals the
> events via eventfd? Or moving it into ACPI layer entirely and adding
> eventfd sysfs interface for all ACPI devices?
I think Alex is asking why wouldn't you push it through the vfio
device FD? There is an unambiguous relationship between the QEMU vPCI
identity and the VFIO device, and we already have a good security
model for VMM access to the device FD.
Jason
next prev parent reply other threads:[~2023-03-09 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 22:05 [PATCH] vfio/pci: Propagate ACPI notifications to the user-space Grzegorz Jaszczyk
2023-03-07 23:41 ` Alex Williamson
2023-03-08 8:11 ` Tian, Kevin
2023-03-08 11:41 ` Grzegorz Jaszczyk
2023-03-08 17:49 ` Alex Williamson
2023-03-08 18:45 ` Dominik Behr
2023-03-08 20:06 ` Alex Williamson
2023-03-08 22:44 ` Dominik Behr
2023-03-08 23:38 ` Alex Williamson
2023-03-09 1:51 ` Dominik Behr
2023-03-09 18:25 ` Jason Gunthorpe [this message]
2023-03-09 13:41 ` Grzegorz Jaszczyk
2023-03-22 9:47 ` Grzegorz Jaszczyk
2023-03-23 17:07 ` Alex Williamson
2023-03-24 12:29 ` Grzegorz Jaszczyk
2023-03-08 14:40 ` kernel test robot
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=ZAokiR4EC3gFAuJ1@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=abhsahu@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=dbehr@chromium.org \
--cc=dmy@semihalf.com \
--cc=dtor@google.com \
--cc=jaz@semihalf.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tn@semihalf.com \
--cc=upstream@semihalf.com \
--cc=yi.l.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox