On Tue, Jun 30, 2009 at 06:06:56PM +0800, Jike Song wrote:
> On Mon, Jun 29, 2009 at 7:07 PM, Matthew Wilcox<matthew@xxxxxx> wrote:
> > On Mon, Jun 29, 2009 at 01:04:53PM +0530, M. Mohan Kumar wrote:
> >>
> >> If the files don't exist, should not we return without displaying any
> >> warning?
> >
> > Yes, we should. ??Can you try this patch?
>
> Hi Willy, specify -M to lspci still produce lots of errors like these:
>
> pcilib: Cannot open /sys/bus/pci/devices/0000:00:02.0/config
To be fair, what you're trying to do there makes no sense:
-M Invoke bus mapping mode which performs a thorough scan of all
PCI devices, including those behind misconfigured bridges etc.
This option is available only to root and it gives meaningful
results only if combined with direct hardware access mode (oth-
erwise the results are identical to normal listing modes, modulo
bugs in lspci). Please note that the bus mapper doesn't support
PCI domains and scans only domain 0.
I'd be inclined to make lspci error out when trying -M with sysfs or procfs.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
