From: Keith Busch <keith.busch@intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Derrick, Jonathan" <jonathan.derrick@intel.com>,
"hch@infradead.org" <hch@infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Bauer, Scott" <scott.bauer@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH] PCI/VMD: White list for fast interrupt handlers
Date: Thu, 28 Jun 2018 08:02:40 -0600 [thread overview]
Message-ID: <20180628140240.GA12793@localhost.localdomain> (raw)
In-Reply-To: <20180628112208.GA8914@red-moon>
On Thu, Jun 28, 2018 at 12:22:17PM +0100, Lorenzo Pieralisi wrote:
> On Fri, May 25, 2018 at 07:11:14PM +0000, Derrick, Jonathan wrote:
> > We've seen this actually fix an issue with one vendor's multi-function
> > switch. I'd like to see it get into 4.18 if possible
>
> Sorry for the delay in getting back to this.
>
> It seems like Christoph is not too happy about this patch, it is your
> code so I would apply it unless there is a cleaner alternative so please
> do let me know.
VMD hardware really relies on the host software to bring all the logic,
and it was intended to prioritize PCIe attached storage. The patch just
captures that intention, so yes please, let's queue this up.
I understands Christoph's lack of enthusiasm for this, but at least this
isn't a PCIe HBA with proprietary interfaces and firmware. :)
next prev parent reply other threads:[~2018-06-28 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 16:00 [PATCH] PCI/VMD: White list for fast interrupt handlers Keith Busch
2018-05-09 4:38 ` Christoph Hellwig
2018-05-09 15:26 ` Keith Busch
2018-05-11 15:39 ` Derrick, Jonathan
2018-05-25 19:11 ` Derrick, Jonathan
2018-06-28 11:22 ` Lorenzo Pieralisi
2018-06-28 14:02 ` Keith Busch [this message]
2018-06-28 16:32 ` Lorenzo Pieralisi
2018-05-14 14:15 ` Christoph Hellwig
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=20180628140240.GA12793@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=hch@infradead.org \
--cc=jonathan.derrick@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=scott.bauer@intel.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;
as well as URLs for NNTP newsgroup(s).