From: Zeng Heng <zengheng4@huawei.com>
To: Ben Horgan <ben.horgan@arm.com>, James Morse <james.morse@arm.com>
Cc: Qinxin Xia <xiaqinxin@huawei.com>, <amitsinght@marvell.com>,
<baisheng.gao@unisoc.com>, <baolin.wang@linux.alibaba.com>,
<carl@os.amperecomputing.com>, <dave.martin@arm.com>,
<david@kernel.org>, <dfustini@baylibre.com>,
<fenghuay@nvidia.com>, <gshan@redhat.com>, <james.morse@arm.com>,
<jonathan.cameron@huawei.com>, <kobak@nvidia.com>,
<lcherian@marvell.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <peternewman@google.com>,
<punit.agrawal@oss.qualcomm.com>, <quic_jiles@quicinc.com>,
<reinette.chatre@intel.com>, <rohit.mathew@arm.com>,
<scott@os.amperecomputing.com>, <sdonthineni@nvidia.com>,
<xhao@linux.alibaba.com>, Linuxarm <linuxarm@huawei.com>
Subject: Re: [Question mpam mpam/snapshot+extras/v6.18-rc1] Question with Configuring iommu_group in 'task'
Date: Wed, 15 Apr 2026 09:27:12 +0800 [thread overview]
Message-ID: <d5918112-0c9f-ecf3-226c-8c3cdd5cd508@huawei.com> (raw)
In-Reply-To: <0d578c61-1341-4149-9e8c-936ea0ce0c50@arm.com>
Hi Ben,
On 2026/4/13 23:02, Ben Horgan wrote:
> Hi Qinxin,
>
> On 4/3/26 03:44, Qinxin Xia wrote:
>>
>>
>> On 2026/3/27 18:47:49, Ben Horgan <ben.horgan@arm.com> wrote:
>>> Hi Qinxin,
>>>
>>> On 3/27/26 10:21, Qinxin Xia wrote:
>>>>
>>>> Hello everyone!
>>>>
>>>> In earlier versions, mpam supports the configuration of iommu_groups.
>>>>
>>>> 823 static ssize_t rdtgroup_tasks_write(struct kernfs_open_file *of,
>>>> 824 char *buf, size_t nbytes,
>>>> loff_t off)
>>>> 825 {
>>>> 826 struct rdtgroup *rdtgrp;
>>>> 827 int iommu_group_id;
>>>> 828 bool is_iommu;
>>>> 829 char *pid_str;
>>>> 830 int ret = 0;
>>>> 831 pid_t pid;
>>>> 832
>>>> 833 rdtgrp = rdtgroup_kn_lock_live(of->kn);
>>>> 834 if (!rdtgrp) {
>>>> 835 rdtgroup_kn_unlock(of->kn);
>>>> 836 return -ENOENT;
>>>> 837 }
>>>> 838 rdt_last_cmd_clear();
>>>> 839
>>>> 840 if (rdtgrp->mode == RDT_MODE_PSEUDO_LOCKED ||
>>>> 841 rdtgrp->mode == RDT_MODE_PSEUDO_LOCKSETUP) {
>>>> 842 ret = -EINVAL;
>>>> 843 rdt_last_cmd_puts("Pseudo-locking in progress\n");
>>>> 844 goto unlock;
>>>> 845 }
>>>> 846
>>>> 847 while (buf && buf[0] != '\0' && buf[0] != '\n') {
>>>> 848 pid_str = strim(strsep(&buf, ","));
>>>> 849
>>>> 850 is_iommu = string_is_iommu_group(pid_str, &iommu_group_id);
>>>>
>>>> What puzzles me is why we would put it under 'task'—this seems a little
>>>> strange to users.It seems they are not related.Why don't we add a new
>>>> interface like 'iommu'?
>>>
>>> I think it is likely that this interface would change if upstream support is added.
>>>
>>
>> I have done some work in this direction before, and I will release an
>> RFC later for further discussion.:-)
>
> Looking forward to seeing it.
>
> Ben
>
Following the current SMMU approach, I've submitted several bugfix
patches for the MPAM driver, but haven't received any review feedback
yet.
To avoid these being overlooked, I'd like to kindly remind to take a
look:
v2:
https://lore.kernel.org/all/20260414032610.1523958-1-zengheng4@huawei.com/
v1:
https://lore.kernel.org/all/20251107063300.1580046-1-zengheng4@huawei.com/
Additionally, I'd like to check on the status of this branch — is it
still actively maintained? It would be helpful to understand the future
plans for MPAM development.
Thanks for your time,
Zeng Heng
next prev parent reply other threads:[~2026-04-15 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:21 [Question mpam mpam/snapshot+extras/v6.18-rc1] Question with Configuring iommu_group in 'task' Qinxin Xia
2026-03-27 10:47 ` Ben Horgan
2026-04-03 2:44 ` Qinxin Xia
2026-04-13 15:02 ` Ben Horgan
2026-04-15 1:27 ` Zeng Heng [this message]
2026-04-15 12:42 ` Ben Horgan
2026-04-16 3:02 ` Zeng Heng
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=d5918112-0c9f-ecf3-226c-8c3cdd5cd508@huawei.com \
--to=zengheng4@huawei.com \
--cc=amitsinght@marvell.com \
--cc=baisheng.gao@unisoc.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=ben.horgan@arm.com \
--cc=carl@os.amperecomputing.com \
--cc=dave.martin@arm.com \
--cc=david@kernel.org \
--cc=dfustini@baylibre.com \
--cc=fenghuay@nvidia.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=kobak@nvidia.com \
--cc=lcherian@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=peternewman@google.com \
--cc=punit.agrawal@oss.qualcomm.com \
--cc=quic_jiles@quicinc.com \
--cc=reinette.chatre@intel.com \
--cc=rohit.mathew@arm.com \
--cc=scott@os.amperecomputing.com \
--cc=sdonthineni@nvidia.com \
--cc=xhao@linux.alibaba.com \
--cc=xiaqinxin@huawei.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