[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170726173353.GB21705@kroah.com>
Date: Wed, 26 Jul 2017 10:33:53 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Jan Glauber <jan.glauber@...iumnetworks.com>,
Suzuki K Poulose <Suzuki.Poulose@....com>,
Mark Rutland <mark.rutland@....com>,
Will Deacon <will.deacon@....com>,
linux-arm-kernel@...ts.infradead.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-pci@...r.kernel.org
Subject: Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU
counters
On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav Petkov wrote:
> On Wed, Jul 26, 2017 at 09:19:49AM -0700, Greg KH wrote:
> > On Wed, Jul 26, 2017 at 05:55:48PM +0200, Borislav Petkov wrote:
> > > On Wed, Jul 26, 2017 at 05:45:15PM +0200, Jan Glauber wrote:
> > > > The PMU/EDAC devices are all PCI devices do I need the 'struct pci_dev *'.
> > > > I'm not aware of other ways to access these devices. Please enlighten
> > > > me if I'm missing something.
> > >
> > > Me enlighten you on Cavium hardware?! You're funny.
> > >
> > > So I don't know whether the PCI hotplug code can run more than one
> > > function upon PCI ID detection. Probably Greg will say, write a
> > > multiplexer wrapper. :-)
> >
> > -ENOCONTEXT....
> >
> > Anyway, pci questions are best asked on the linux-pci@...r list. And
> > yes, all PCI devices end up with a 'struct pci_dev *' automatically.
>
> Simple: so they have a PCI ID of a memory contoller and want to hotplug
> two drivers for it. And those two drivers should remain independent from
> each other.
Hahahahaha, no. That's crazy, you were right in guessing what my answer
was going to be :)
greg k-h
Powered by blists - more mailing lists