v@dpdk.org; jer...@marvell.com; Chen, Mike Ximing
>> ; Richardson, Bruce
>> ; NBU-Contact-Thomas Monjalon (EXTERNAL)
>> ; Marchand, David ;
>> nipun.gu...@amd.com
>> Subject: Re: [PATCH v1] bus/pci: revise support PASID control
>>
>> On Nov 15, 2023, at 01:39,
pun.gu...@amd.com
> Subject: Re: [PATCH v1] bus/pci: revise support PASID control
>
> On Nov 15, 2023, at 01:39, Sevincer, Abdullah
> wrote:
> >
> > External email: Use caution opening links or attachments
> >
> >
> >> +I don’t know about the details,
On Nov 15, 2023, at 01:39, Sevincer, Abdullah
wrote:
>
> External email: Use caution opening links or attachments
>
>
>> +I don’t know about the details, so it means for different devices that
>> support PASID, they have different offsets?
>
>> +Btw, Is this cap still not exposed to user spa
>+I don’t know about the details, so it means for different devices that
>support PASID, they have different offsets?
>+Btw, Is this cap still not exposed to user space in latest kernel?
Yes, may be different offsets for different devices.
As of now it is not exposed to user. Bruce's test was o
+Nipun
Please cc me and Nipun if there is a new version.
> On Nov 14, 2023, at 01:27, Abdullah Sevincer
> wrote:
>
> External email: Use caution opening links or attachments
>
>
> This commit revises PASID control function to accept PASID offset to
> pasid *structure* instead of taking exact
This commit revises PASID control function to accept PASID offset to
pasid *structure* instead of taking exact register for controlling the
feature.
PASID control function was introduced in earlier commit.
Pls see commit 5a6878335b81 ("event/dlb2: disable PASID") and
commit 60ea19609aec ("bus/pci:
6 matches
Mail list logo
