From: Jerin Jacob <jerinjacobk@gmail.com>
To: Abdullah Sevincer <abdullah.sevincer@intel.com>,
Gaetan Rivet <grive@u256.net>,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, jerinj@marvell.com, mike.ximing.chen@intel.com
Subject: Re: [PATCH v1] event/dlb2: add support for disabling PASID
Date: Thu, 8 Jun 2023 11:08:25 +0530 [thread overview]
Message-ID: <CALBAE1OA4zhdf-FbUh4ONuOGGvJvj30kT99811k_0maFi1C_fg@mail.gmail.com> (raw)
In-Reply-To: <20230607210050.107944-1-abdullah.sevincer@intel.com>
On Thu, Jun 8, 2023 at 2:31 AM Abdullah Sevincer
<abdullah.sevincer@intel.com> wrote:
>
> vfio-pci driver in Linux kernel 6.2 enables PASID by default.
> In DLB hardware, enabling PASID puts DLB in SIOV mode. This
> breaks DLB PF-PMD mode. For DLB PF-PMD mode to function properly
> PASID needs to be disabled for kernel 6.2.
>
> In this commit this issue is addressed and PASID is disabled
> by writing a zero to PASID control register.
>
> Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
> + /* The current Linux kernel vfio driver does not expose PASID capability to
> + * users. It also enables PASID by default, which breaks DLB PF PMD. We have
> + * to use the hardcoded offset for now to disable PASID.
> + */
> + pasid_cap_offset = DLB2_PCI_PASID_CAP_OFFSET;
> +
> + off = pasid_cap_offset + DLB2_PCI_PASID_CTRL;
+++ additional folks.
Is make sense to move this helper function to PCI common for disabling
PASID for a PCI device so that other driver can use if needed
as the implementation is not specific to DLB2.
> + if (rte_pci_read_config(pdev, &pasid_ctrl, 2, off) != 2)
> + pasid_ctrl = 0;
> +
> + if (pasid_ctrl) {
> + DLB2_INFO(dlb2_dev, "DLB2 disabling pasid...\n");
> +
> + pasid_ctrl = 0;
> + ret = rte_pci_write_config(pdev, &pasid_ctrl, 2, off);
> + if (ret != 2) {
> + DLB2_LOG_ERR("[%s()] failed to write the pcie config space at offset %d\n",
> + __func__, (int)off);
> + return ret;
> + }
> + }
> +
> return 0;
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-06-08 5:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 21:00 Abdullah Sevincer
2023-06-08 5:38 ` Jerin Jacob [this message]
2023-06-08 7:22 ` Thomas Monjalon
2023-06-08 7:28 ` David Marchand
2023-06-08 11:32 ` Jerin Jacob
2023-06-08 14:25 ` Chen, Mike Ximing
2023-08-03 7:56 ` David Marchand
2023-08-03 16:57 ` Sevincer, Abdullah
2023-10-26 16:46 ` Sevincer, Abdullah
2023-10-26 16:38 ` [PATCH v2] event/dlb2: disable PASID for kernel 6.2 Abdullah Sevincer
2023-10-30 21:12 ` [PATCH v3] event/dlb2: fix " Abdullah Sevincer
2023-10-31 8:21 ` Jerin Jacob
2023-10-31 15:13 ` Sevincer, Abdullah
2023-10-31 17:06 ` Jerin Jacob
2023-10-31 17:15 ` Bruce Richardson
2023-10-31 18:42 ` Jerin Jacob
2023-10-31 20:44 ` Bruce Richardson
2023-11-01 4:51 ` Jerin Jacob
2023-11-01 19:05 ` Sevincer, Abdullah
2023-11-02 10:23 ` Bruce Richardson
2023-11-02 10:48 ` Thomas Monjalon
2023-11-02 18:17 ` Sevincer, Abdullah
2023-10-31 0:10 ` [PATCH v1] event/dlb2: add support for disabling PASID Stephen Hemminger
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=CALBAE1OA4zhdf-FbUh4ONuOGGvJvj30kT99811k_0maFi1C_fg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abdullah.sevincer@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--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).