lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2008 16:21:13 +0900
From:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
To:	Matthew Wilcox <matthew@....cx>
CC:	Pierre Ossman <drzeus-list@...eus.cx>,
	Alex Chiang <achiang@...com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org
Subject: Re: post 2.6.26 requires pciehp_slot_with_bus

Matthew Wilcox wrote:
> On Fri, Jul 25, 2008 at 05:53:33PM +0900, Kenji Kaneshige wrote:
>> IIRC, pciehp uses bridge's secondary bus number for slot name, and
>> PCI express downstream port can have only one hotplug slot. I think
>> this is why with_bus prameter makes difference.
> 
> Ahh, I overlooked that last night.
> 
>> But it doesn't work on the system that has multiple pci segments.
> 
> Yes, we still have the problem that pciehp does not include the 'chassis
> number' as part of the name.  I no longer have easy access to any
> systems with multiple chassis.  Do your systems have devices which
> implement the PCI_CAP_ID_SLOTID capcbility?  (as root) lspci -vvv will
> report it:
> 
>   printf("Slot ID: %d slots, First%c, chassis %02x\n",
>          esr & PCI_SID_ESR_NSLOTS,
>          FLAG(esr, PCI_SID_ESR_FIC),
>          chs);
> 

Unfortunately, I don't have any systems that implement the
PCI_CAP_ID_SLOTID capability...

Thanks,
Kenji Kaneshige


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ