From: Christoph Hellwig <hch@infradead.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <helgaas@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH 3/3] PCI/VMD: Enable firmware-first combined model
Date: Sat, 27 Oct 2018 00:34:52 -0700 [thread overview]
Message-ID: <20181027073452.GA15476@infradead.org> (raw)
In-Reply-To: <1540585146-31876-3-git-send-email-jonathan.derrick@intel.com>
On Fri, Oct 26, 2018 at 02:19:06PM -0600, Jon Derrick wrote:
> The VMD endpoint acts as a host bridge for a nested PCIe segment. This
> segment and its ports and endpoints are not represented in ACPI tables
> such as DSDT and HEST, so "firmware first" error handling is currently
> unsupported in the driver in favor of OS native error handling.
>
> VMD does support firmware error handling where errors are signaled to
> host firmware via SMI. VMD supports a "combined model" [1] where
> OS-native error handling is used in addition to firmware. Because of
> this combined model, this patch does not subscribe to the kernel
> firmware-first architecture which would prevent OS native error
> handling.
This sounds really horrible. Why can't Intel just offer a tweak to
disable this whole VMD nightmare and treat it like a normal PCIe bus,
which would leave everyone much better off?
next prev parent reply other threads:[~2018-10-27 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 20:19 [PATCH 1/3] PCI/AER: Option to leave System Error Interrupts as-is Jon Derrick
2018-10-26 20:19 ` [PATCH 2/3] PCI: Export pci_find_host_bridge() Jon Derrick
2018-10-26 20:19 ` [PATCH 3/3] PCI/VMD: Enable firmware-first combined model Jon Derrick
2018-10-27 7:34 ` Christoph Hellwig [this message]
2018-10-29 21:06 ` [PATCH 1/3] PCI/AER: Option to leave System Error Interrupts as-is Bjorn Helgaas
2018-11-02 9:53 ` Borislav Petkov
2018-11-02 16:17 ` Keith Busch
2018-11-02 16:26 ` Borislav Petkov
2018-11-02 16:34 ` Keith Busch
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=20181027073452.GA15476@infradead.org \
--to=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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