[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1534454924.13356.1.camel@intel.com>
Date: Thu, 16 Aug 2018 21:28:45 +0000
From: "Derrick, Jonathan" <jonathan.derrick@...el.com>
To: "Busch, Keith" <keith.busch@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"okaya@...nel.org" <okaya@...nel.org>,
"willy@...radead.org" <willy@...radead.org>,
"liudongdong3@...wei.com" <liudongdong3@...wei.com>,
"helgaas@...nel.org" <helgaas@...nel.org>,
"poza@...eaurora.org" <poza@...eaurora.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 1/2] PCI/DPC: Add 'nodpc' parameter
On Thu, 2018-08-16 at 15:19 -0600, Keith Busch wrote:
> On Thu, Aug 16, 2018 at 01:50:42PM -0700, Derrick, Jonathan wrote:
> > It can also be disabled with setpci, but is that any less of a
> > hassle?
> > Genuine question to understand your point of view.
>
> That is not a real solution, IMO. 'setpci' is good to inject things
> for testing, but it changes config space without the kernel aware
> that
> you've done that, so it is inherently racey with other kernel threads
> touching pci config space. And the kernel or platform may end up
> undoing
> what you had 'setpci' do anyway with no immediate way to be notified
> it
> was changed.
It sounds like a sysfs toggle could be useful regardless of the boot
parameter.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (3278 bytes)
Powered by blists - more mailing lists