mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: mahesh@linux.ibm.com, mpe@ellerman.id.au,
	linuxppc-dev@lists.ozlabs.org,
	Narayana Murty N <nnmlinux@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, oohall@gmail.com,
	npiggin@gmail.com, christophe.leroy@csgroup.eu,
	naveen@kernel.org, gwshan@linux.vnet.ibm.com,
	benh@kernel.crashing.org, agraf@suse.de, vaibhav@linux.ibm.com
Subject: Re: [PATCH v1] powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery
Date: Sun, 15 Jun 2025 08:09:15 +0530	[thread overview]
Message-ID: <174995502358.107804.15093806320062799032.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20250508062928.146043-1-nnmlinux@linux.ibm.com>

On Thu, 08 May 2025 02:29:28 -0400, Narayana Murty N wrote:
> VFIO EEH recovery for PCI passthrough devices fails on PowerNV and pseries
> platforms due to missing host-side PE bridge reconfiguration. In the
> current implementation, eeh_pe_configure() only performs RTAS or OPAL-based
> bridge reconfiguration for native host devices, but skips it entirely for
> PEs managed through VFIO in guest passthrough scenarios.
> 
> This leads to incomplete EEH recovery when a PCI error affects a
> passthrough device assigned to a QEMU/KVM guest. Although VFIO triggers the
> EEH recovery flow through VFIO_EEH_PE_ENABLE ioctl, the platform-specific
> bridge reconfiguration step is silently bypassed. As a result, the PE's
> config space is not fully restored, causing subsequent config space access
> failures or EEH freeze-on-access errors inside the guest.
> 
> [...]

Applied to powerpc/fixes.

[1/1] powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery
      https://git.kernel.org/powerpc/c/33bc69cf6655cf60829a803a45275f11a74899e5

Thanks

      parent reply	other threads:[~2025-06-15  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  6:29 Narayana Murty N
2025-05-14 13:09 ` Ganesh G R
2025-06-15  2:39 ` Madhavan Srinivasan [this message]

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=174995502358.107804.15093806320062799032.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=nnmlinux@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    --cc=vaibhav@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®