Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Rickey Bartlett <subtexel@gmail.com>
Cc: Nirmal Patel <nirmal.patel@linux.intel.com>,
	Jonathan Derrick <jonathan.derrick@linux.dev>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Krzysztof Wilczynski <kwilczynski@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: vmd: Flush initiator posted writes before demuxing interrupts on Meteor Lake
Date: Tue, 8 Sep 2026 19:53:25 -0600	[thread overview]
Message-ID: <aqC8FSpnNxxitHtA@kbusch-mbp> (raw)
In-Reply-To: <20260825043220.9047-1-subtexel@gmail.com>

This might be going beyond the minimum requirement for the errata, but
lacking additional insight into it, and considering this will clearly
flush preceding writes to completion, looks good to me!

Acked-by: Keith Busch <kbusch@kernel.org>

I am just not sure if reading config space is necessary vs memory space
(maybe it doesn't matter), or if this errata requires reading from every
potential interrupting device to flush preceeding transactions vs just a
single posted transaction to anything in the domain. Worst case, many
devices sharing the interrupt may reduce performance, but it sounds like
the affected platforms typically only have a pair of nvme's at most
anyway.

  parent reply	other threads:[~2026-09-09  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  4:32 [PATCH] PCI: vmd: Flush initiator posted writes before demuxing interrupts on Meteor Lake Rickey Bartlett
2026-08-25  4:45 ` sashiko-bot
2026-09-02 12:28 ` Manivannan Sadhasivam
2026-09-08 23:10 ` Bjorn Helgaas
2026-09-09  1:53 ` Keith Busch [this message]
2026-09-09  3:00   ` Rickey Bartlett

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=aqC8FSpnNxxitHtA@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=jonathan.derrick@linux.dev \
    --cc=kai.heng.feng@canonical.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=nirmal.patel@linux.intel.com \
    --cc=subtexel@gmail.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