Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nikola Prica" <nikprica@amd.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4] PCI: Accept AtomicOps already enabled by the hypervisor
Date: Mon, 21 Sep 2026 11:13:52 +0000	[thread overview]
Message-ID: <20260921111353.0848A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921111903.978687-1-nikprica@amd.com>

> 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.
> 
> After 1ae8c4ce1570 ("PCI: Enable AtomicOps only if Root Port
> supports them"), pci_enable_atomic_ops_to_root() always fails if the
> Root Port is not visible.  On systems where the Root Port is not
> visible but *does* support AtomicOps, this is a regression: prior to
> 1ae8c4ce1570, it enabled AtomicOps in the endpoint and returned
> success.
> 
> Fixes: 1ae8c4ce1570 ("PCI: Enable AtomicOps only if Root Port supports them")
> Reviewed-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Gerd Bayer <gbayer@linux.ibm.com>
> Tested-by: Gerd Bayer <gbayer@linux.ibm.com>
> Signed-off-by: Nikola Prica <nikola.prica@amd.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260921111903.978687-1-nikprica@amd.com?part=1


  reply	other threads:[~2026-09-21 11:13 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
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 [this message]
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=20260921111353.0848A1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nikprica@amd.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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