From: Jerin Jacob <jerinjacobk@gmail.com>
To: Abdullah Sevincer <abdullah.sevincer@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, mike.ximing.chen@intel.com,
bruce.richardson@intel.com, thomas@monjalon.net
Subject: Re: [PATCH v5 1/2] bus/pci: add function to enable/disable PASID
Date: Fri, 3 Nov 2023 23:32:00 +0530 [thread overview]
Message-ID: <CALBAE1PUKyyB3RTkmc+j6KuwTO789ZvDL5THvdtwGoy_+vc-QA@mail.gmail.com> (raw)
In-Reply-To: <20231103175204.2812654-2-abdullah.sevincer@intel.com>
On Fri, Nov 3, 2023 at 11:23 PM Abdullah Sevincer
<abdullah.sevincer@intel.com> wrote:
>
> This commit implements an internal api to enable and disable PASID for
> a device e.g. device driver event/dlb2.
>
> For kernels when PASID enabled by default it breaks DLB functionality,
> hence disabling PASID is required for DLB to function properly.
>
> PASID capability is not exposed to users hence offset can not be
> retrieved by rte_pci_find_ext_capability() api. Therefore, api
> implemented in this commit accepts an offset for PASID with an enable
> flag which is used to enable/disable PASID.
>
> Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
Looks like you missed my comments at
https://patches.dpdk.org/project/dpdk/patch/20231103170347.2790525-1-abdullah.sevincer@intel.com/
next prev parent reply other threads:[~2023-11-03 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:52 [PATCH v5 0/2] *** Disable PASID for DLB Device *** Abdullah Sevincer
2023-11-03 17:52 ` [PATCH v5 1/2] bus/pci: add function to enable/disable PASID Abdullah Sevincer
2023-11-03 18:02 ` Jerin Jacob [this message]
2023-11-03 18:06 ` Sevincer, Abdullah
2023-11-03 17:52 ` [PATCH v5 2/2] event/dlb2: fix disable PASID Abdullah Sevincer
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=CALBAE1PUKyyB3RTkmc+j6KuwTO789ZvDL5THvdtwGoy_+vc-QA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abdullah.sevincer@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.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).