mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keng-Yu Lin <keng-yu.lin@hpe.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Matthew Ruffell <matthew.ruffell@canonical.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	andy.liang@hpe.com, david.chang@hpe.com, s.collins@hpe.com,
	jenifer.golmitz@hpe.com, pravallika.kamma@hpe.com,
	zhen-dong.lai@hpe.com, zachary.pabor-ext@hpe.com
Subject: Re: [PATCH v2] PCI/PM: Restore BARs after powering up during enumeration
Date: Wed, 14 Oct 2026 12:31:50 +0800	[thread overview]
Message-ID: <20261014043150.1094480-1-keng-yu.lin@hpe.com> (raw)
In-Reply-To: <80c964e1-30d3-4b09-aef8-08c04e119e79@amd.com>

Hi Rafael, Mario,

I tested this sequence on AMD Venice SP7 and Turin, with debug
prints added. Both systems saved a vmcore and rebooted successfully.

There were no BAR writes from this path on normal boot. In the
crash kernels, only the cleared xHCI BARs were restored: two on
Venice and one on Turin. All readbacks matched.

Rafael, would you prefer to send a patch with this sequence, or
should I send v3 with your Suggested-by?

Thanks,
Keng-Yu

  reply	other threads:[~2026-10-14  4:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 10:46 Keng-Yu Lin
2026-10-12 11:34 ` Rafael J. Wysocki (Intel)
2026-10-12 17:09   ` Mario Limonciello
2026-10-13  6:09     ` Keng-Yu Lin
2026-10-13 15:23       ` Rafael J. Wysocki (Intel)
2026-10-13 15:39         ` Mario Limonciello
2026-10-13 15:52           ` Rafael J. Wysocki (Intel)
2026-10-13 16:57             ` Rafael J. Wysocki (Intel)
2026-10-13 21:48               ` Mario Limonciello
2026-10-14  4:31                 ` Keng-Yu Lin [this message]
2026-10-14 15:49                   ` Rafael J. Wysocki (Intel)

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=20261014043150.1094480-1-keng-yu.lin@hpe.com \
    --to=keng-yu.lin@hpe.com \
    --cc=andy.liang@hpe.com \
    --cc=bhelgaas@google.com \
    --cc=david.chang@hpe.com \
    --cc=jenifer.golmitz@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=matthew.ruffell@canonical.com \
    --cc=pravallika.kamma@hpe.com \
    --cc=rafael@kernel.org \
    --cc=s.collins@hpe.com \
    --cc=zachary.pabor-ext@hpe.com \
    --cc=zhen-dong.lai@hpe.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®