[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160119153822.GA3979@localhost.localdomain>
Date: Tue, 19 Jan 2016 15:38:23 +0000
From: Keith Busch <keith.busch@...el.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: "Derrick, Jonathan" <jonathan.derrick@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Veal, Bryan E" <bryan.e.veal@...el.com>
Subject: Re: [PATCHv8 0/5] Driver for new "VMD" device
On Fri, Jan 15, 2016 at 04:06:31PM -0600, Bjorn Helgaas wrote:
> On Fri, Jan 15, 2016 at 07:48:11PM +0000, Derrick, Jonathan wrote:
> > Additionally, what are your thoughts of moving the menuconfig option from the root-tier to 'Processor Type and Features'?
>
> I don't know how Intel is going to market this feature, but from a
> developer point of view, the code looks more like the PCI host bridge
> drivers in drivers/pci/host than it does like a processor feature.
> Most of those drivers are specific to a particular architecture or
> SoC.
We had tighter dependencies on x86 in earlier revisions of this driver. It
probably now looks more sensible to be in drivers/pci/host instead of
arch specific.
Do you want us to make this change and resend the series? Or can we
provide patches for in tree development? We'll also add the requested
code comments to explain more about the device.
BTW, we completed tests with your pci/host-vmd branch, and that was
successful.
Powered by blists - more mailing lists