From: Gerd Bayer <gbayer@linux.ibm.com>
To: Nikola Prica <nikprica@amd.com>,
bhelgaas@google.com, Niklas Schnelle <schnelle@linux.ibm.com>,
Alexander Schmidt <alexs@linux.ibm.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
jerry.jiang@amd.com, haijun.chang@amd.com, andy.zhang@amd.com,
christian.koenig@amd.com, jim.chow@broadcom.com,
matthew.mcclure@broadcom.com, Nikola Prica <nikola.prica@amd.com>
Subject: Re: [PATCH v2] PCI: Accept AtomicOps already enabled by the hypervisor
Date: Mon, 14 Sep 2026 15:41:20 +0200 [thread overview]
Message-ID: <85a220af90568124bd4e7d354a8741b612955595.camel@linux.ibm.com> (raw)
In-Reply-To: <20260907161701.454364-1-nikprica@amd.com>
On Mon, 2026-09-07 at 18:17 +0200, Nikola Prica wrote:
> From: Nikola Prica <nikola.prica@amd.com>
>
> pci_enable_atomic_ops_to_root() currently fails when no root port is
> visible. That is common in passthrough guests (ESXi, Hyper-V): the
> endpoint is assigned to the VM, but the guest topology has no root
> port above it.
>
> In those setups the hypervisor may already have enabled AtomicOp
> requester enable on the device. If PCI_EXP_DEVCTL2_ATOMIC_REQ is set,
> treat AtomicOps as already enabled and return success instead of
> failing the Root Port walk.
Hi Nikola,
your patch got me interested, since it touches those parts of
pci_enable_atomic_ops_to_root() that commit 1ae8c4ce1570 ("PCI: Enable
AtomicOps only if Root Port supports them") has modified.
I like your solution for putting the hypervisor in control of the
enablement of Atomic Ops on root-less PCI functions and did test your
change on s390/Connect-X, successfully.
> Signed-off-by: Nikola Prica <nikola.prica@amd.com>
If that commit of mine regressed your use-cases, you might even want to
add a Fixes: tag?
> ---
> Changes in v2:
> - Be more strict and only apply logic in headless device case.
>
> drivers/pci/pci.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index b2879a6be5f8..62729ade496f 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -3769,8 +3769,18 @@ int pci_enable_atomic_ops_to_root(struct pci_dev *dev, u32 cap_mask)
> }
>
> root = pcie_find_root_port(dev);
> - if (!root)
> + if (!root) {
> + /*
> + * A hypervisor may expose a headless topology with no
> + * visible root port. If it has already set AtomicOp
> + * Requester Enable, there is nothing more to do.
> + */
> + pcie_capability_read_dword(dev, PCI_EXP_DEVCTL2, &ctl2);
> + if (ctl2 & PCI_EXP_DEVCTL2_ATOMIC_REQ)
> + return 0;
> +
> return -EINVAL;
> + }
>
> pcie_capability_read_dword(root, PCI_EXP_DEVCAP2, &cap);
> if ((cap & cap_mask) != cap_mask)
At any rate, feel free to add my
Reviewed-by: Gerd Bayer <gbayer@linux.ibm.com>
Tested-by: Gerd Bayer <gbayer@linux.ibm.com>
next prev parent reply other threads:[~2026-09-14 13:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:12 [PATCH] PCI: Accept AtomicOps already enabled by the hypervisor Nikola Prica
2026-09-03 12:09 ` Christian König
2026-09-03 12:12 ` sashiko-bot
2026-09-07 15:59 ` Prica, Nikola
2026-09-07 16:17 ` [PATCH v2] " Nikola Prica
2026-09-07 16:15 ` sashiko-bot
2026-09-07 18:23 ` Prica, Nikola
2026-09-08 8:47 ` Christian König
2026-09-11 14:09 ` Prica, Nikola
2026-09-14 13:41 ` Gerd Bayer [this message]
2026-09-14 13:54 ` Christian König
2026-09-18 9:07 ` Prica, Nikola
2026-09-18 9:28 ` [PATCH v3] " Nikola Prica
2026-09-18 9:28 ` sashiko-bot
2026-09-18 12:07 ` Christian König
2026-09-18 17:07 ` Bjorn Helgaas
2026-09-21 11:04 ` Prica, Nikola
2026-09-21 11:05 ` Prica, Nikola
2026-09-21 11:19 ` [PATCH v4] " Nikola Prica
2026-09-21 11:13 ` sashiko-bot
2026-10-01 16:23 ` Bjorn Helgaas
2026-09-21 11:58 ` [PATCH v3] " Christian König
2026-09-21 12:12 ` Thorsten Leemhuis
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=85a220af90568124bd4e7d354a8741b612955595.camel@linux.ibm.com \
--to=gbayer@linux.ibm.com \
--cc=alexs@linux.ibm.com \
--cc=andy.zhang@amd.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=haijun.chang@amd.com \
--cc=jerry.jiang@amd.com \
--cc=jim.chow@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.mcclure@broadcom.com \
--cc=nikola.prica@amd.com \
--cc=nikprica@amd.com \
--cc=schnelle@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.