From: "Sevincer, Abdullah" <abdullah.sevincer@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"Chen, Mike Ximing" <mike.ximing.chen@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>
Subject: RE: [PATCH v7 1/2] bus/pci: support PASID control
Date: Mon, 13 Nov 2023 15:51:43 +0000 [thread overview]
Message-ID: <BYAPR11MB3158198C3835525D3C5DFB0BE9B3A@BYAPR11MB3158.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wwApquaUakA7-ygMTJrT60grOwFGW_aBTHV9xon+WFeQ@mail.gmail.com>
>+Ok, that is indeed an issue.
>+I found some patches exposing this capability with vfio-pci but I am not sure what is the latest work on the topic.
That's right, some kernels may expose the capability some not. We realized it when Bruce reported my earlier patch with the api rte_pci_find_ext_capability() did not
work for him but it was working for me. We had different versions/flavors of kernel.
>+Do you have pointers to the latest kernel patches?
I don’t have any pointers to the latest kernel patches, though I have come across some internet search that was submitted to expose the capability but I am not sure what's the latest status on those patches.
We can ask people involved there and get feedback.
For example below:
https://lists.linuxfoundation.org/pipermail/iommu/2020-June/045531.html
>+In any case, even if, in the future, the kernel exposes this capability, we need to live with the current behavior (and probably for a long time).
>+As the discovery of pasid offset is not possible, the common API merit is low, but at least it shows what is being done by the driver.
>+Can we make a change so that this new API takes only the offset to the pasid *structure* and not to the exact register controlling the feature?
>+It should be something like:
We can change it the way you described. The patch is already merged though 😊.
next prev parent reply other threads:[~2023-11-13 15:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 17:05 [PATCH v7 0/2] *** Disable PASID for DLB Device *** Abdullah Sevincer
2023-11-06 17:05 ` [PATCH v7 1/2] bus/pci: support PASID control Abdullah Sevincer
2023-11-06 18:30 ` David Marchand
2023-11-06 18:50 ` Sevincer, Abdullah
2023-11-10 8:03 ` David Marchand
2023-11-13 15:51 ` Sevincer, Abdullah [this message]
2023-11-13 17:36 ` Sevincer, Abdullah
2023-11-13 17:27 ` [PATCH v1] bus/pci: revise " Abdullah Sevincer
2023-11-14 13:59 ` Chenbo Xia
2023-11-14 17:39 ` Sevincer, Abdullah
2023-11-15 1:53 ` Chenbo Xia
2023-11-16 17:43 ` Chen, Mike Ximing
2023-11-17 6:48 ` Chenbo Xia
2023-11-14 17:36 ` [PATCH v2] " Abdullah Sevincer
2023-11-17 6:55 ` Chenbo Xia
2023-11-21 15:50 ` Thomas Monjalon
2023-11-06 17:05 ` [PATCH v7 2/2] event/dlb2: fix disable PASID Abdullah Sevincer
2023-11-06 17:50 ` [PATCH v7 0/2] *** Disable PASID for DLB Device *** Thomas Monjalon
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=BYAPR11MB3158198C3835525D3C5DFB0BE9B3A@BYAPR11MB3158.namprd11.prod.outlook.com \
--to=abdullah.sevincer@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=nipun.gupta@amd.com \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).