From: Yi Liu <yi.l.liu@intel.com>
To: XueMei Yue <xuemeiyue@petaio.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
"joro@8bytes.org" <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: FW: About the patch ”https://lore.kernel.org/linux-iommu/20240412082121.33382-1-yi.l.liu@intel.com/ “ for help
Date: Tue, 23 Jul 2024 11:03:58 +0800 [thread overview]
Message-ID: <903517d3-7a65-4269-939c-6033d57f2619@intel.com> (raw)
In-Reply-To: <SJ0PR18MB51864CD07C0F5FB0AA23AC05D3A92@SJ0PR18MB5186.namprd18.prod.outlook.com>
On 2024/7/23 10:52, XueMei Yue wrote:
> DEAR ALL ,
>
> No I have know the root cause , the issue ouccured when below code run my AMD test PC.
>
> So could you guys give some suggestion ? Will very much appreciate if you feel free to reply！！
>
> [cid:image001.png@01DADCEE.6F2E3F80]
For the people that cannot see the picture. It shows the pasid attach
path failed as the domain->ops->set_dev_pasid is null, hence failed with
EOPNOTSUPP errno.
I don't think the AMD iommu driver has supported the set_dev_pasid callback
for the non-SVA domains. Suravee can keep me honest. And you may also need
to check if your test PC has the PASID capability.
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-07-23 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ0PR18MB51863C8625058B9BB35D3EC1D3A82@SJ0PR18MB5186.namprd18.prod.outlook.com>
2024-07-23 2:52 ` FW: About the patch ”https://lore.kernel.org/linux-iommu/20240412082121.33382-1-yi.l.liu@intel.com/ “ for help XueMei Yue
2024-07-23 3:03 ` Yi Liu [this message]
2024-07-23 3:22 ` XueMei Yue
2024-07-23 4:05 ` Yi Liu
2024-07-23 6:52 ` XueMei Yue
2024-07-24 2:51 ` Yi Liu
2024-07-26 9:18 ` FW: About the patch âhttps://lore.kernel.org/linux-iommu/20240412082121.33382-1-yi.l.liu@intel.com/ â " Vasant Hegde
2024-07-30 9:08 ` XueMei Yue
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=903517d3-7a65-4269-939c-6033d57f2619@intel.com \
--to=yi.l.liu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xuemeiyue@petaio.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