From: Jason Gunthorpe <jgg@ziepe.ca>
To: James Morse <james.morse@arm.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
alex@ghiti.fr, aou@eecs.berkeley.edu, babu.moger@amd.com,
baolin.wang@linux.alibaba.com, ben.horgan@arm.com,
corbet@lwn.net, cuiyunhui@bytedance.com, Dave.Martin@arm.com,
fustini@kernel.org, joro@8bytes.org, kevin.tian@intel.com,
palmer@dabbelt.com, pjw@kernel.org, reinette.chatre@intel.com,
robin.murphy@arm.com, shuah@kernel.org, tomasz.jeznach@linux.dev,
wangzhou1@hisilicon.com, will@kernel.org, xiaqinxin@huawei.com,
yuanzhu@bytedance.com, zengheng4@huawei.com,
zhangzhanpeng.jasper@bytedance.com, x86@kernel.org,
iommu@lists.linux.dev, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: Resctrl and I/O
Date: Wed, 23 Sep 2026 14:24:51 -0300 [thread overview]
Message-ID: <20260923172451.GN1540250@ziepe.ca> (raw)
In-Reply-To: <8557363f-c051-4267-9fbc-f4cbb13ac35e@arm.com>
On Wed, Sep 23, 2026 at 06:13:27PM +0100, James Morse wrote:
> Using iommu_group like this may need a bit more thinking....
> If we can fall back to using a device as seen by sysfs, then the arch differences
> here could be invisible to user-space.
Please don't codify iommu_groups in any new uAPI, that has proven to
be a problematic choice for VFIO. We undid it.. Lets not repeat it.
Jason
next prev parent reply other threads:[~2026-09-23 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 16:51 Luck, Tony
2026-09-23 1:27 ` Drew Fustini
2026-09-23 17:13 ` James Morse
2026-09-23 17:24 ` Jason Gunthorpe [this message]
2026-09-24 2:30 ` [External] " yunhui cui
2026-09-24 9:38 ` Qinxin Xia
2026-09-24 9:40 ` Ben Horgan
2026-09-24 9:51 ` Zhanpeng Zhang
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=20260923172451.GN1540250@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Dave.Martin@arm.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=babu.moger@amd.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=ben.horgan@arm.com \
--cc=corbet@lwn.net \
--cc=cuiyunhui@bytedance.com \
--cc=fustini@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=james.morse@arm.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=robin.murphy@arm.com \
--cc=shuah@kernel.org \
--cc=tomasz.jeznach@linux.dev \
--cc=tony.luck@intel.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xiaqinxin@huawei.com \
--cc=yuanzhu@bytedance.com \
--cc=zengheng4@huawei.com \
--cc=zhangzhanpeng.jasper@bytedance.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
all inboxes | Powered by JetHome®