From: Jason Gunthorpe <jgg@ziepe.ca>
To: Fred Griffoul <fgriffo@amazon.co.uk>
Cc: griffoul@gmail.com, Alex Williamson <alex.williamson@redhat.com>,
Yi Liu <yi.l.liu@intel.com>, Kevin Tian <kevin.tian@intel.com>,
Eric Auger <eric.auger@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Ankit Agrawal <ankita@nvidia.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Ye Bin <yebin10@huawei.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfio/pci: add msi interrupt affinity support
Date: Wed, 5 Jun 2024 13:22:49 -0300 [thread overview]
Message-ID: <20240605162249.GE791043@ziepe.ca> (raw)
In-Reply-To: <20240605155509.53536-1-fgriffo@amazon.co.uk>
On Wed, Jun 05, 2024 at 03:55:05PM +0000, Fred Griffoul wrote:
> The usual way to configure a device interrupt from userland is to write
> the /proc/irq/<irq>/smp_affinity or smp_affinity_list files. When using
> vfio to implement a device driver or a virtual machine monitor, this may
> not be ideal: the process managing the vfio device interrupts may not be
> granted root privilege, for security reasons. Thus it cannot directly
> control the interrupt affinity and has to rely on an external command.
For a long time I've been beating a drum that people need to stop
using /proc/irq/../smp_affinity, so I like this idea :)
Jason
next prev parent reply other threads:[~2024-06-05 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 15:55 [PATCH v2] vfio/pci: add msi interrupt affinity support Fred Griffoul
2024-06-05 16:22 ` Jason Gunthorpe [this message]
2024-06-06 0:40 ` kernel test robot
2024-06-06 23:11 ` 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=20240605162249.GE791043@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=brauner@kernel.org \
--cc=eric.auger@redhat.com \
--cc=fgriffo@amazon.co.uk \
--cc=griffoul@gmail.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=stefanha@redhat.com \
--cc=yebin10@huawei.com \
--cc=yi.l.liu@intel.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