linux-kernel - [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 20 Dec 2007 07:28:25 -0500
From:	Tony Camuso <tcamuso@...hat.com>
To:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]



-------- Original Message --------
Subject: Re: [PATCH 0/5]PCI: x86 MMCONFIG
Date: Wed, 19 Dec 2007 19:44:13 -0500
From: Tony Camuso <tcamuso@...hat.com>
Reply-To: tcamuso@...hat.com
To: Robert Hancock <hancockr@...w.ca>
References: <fa.zIbPFbLub6ANMT5vMxS6hx+dfv0@....uio.no> 
<fa.3T2SqNjavN55hanLOjr3RO+WalE@....uio.no> <4769B368.1030402@...w.ca>

Robert Hancock wrote:
> Greg KH wrote:
> 
> I think we need more details on why this patch is needed. Also, we 
> already have something like this in arch/x86/pci/mmconfig-shared.c, in 
> the unreachable_devices function. This attempts to detect devices where 
> MMCONFIG cannot access the configuration space (one of these would be at 
> least one device in the AMD K8 built-in northbridge). If this is not 
> sufficient, I would suggest expanding that mechanism instead of adding 
> all this new code.
> 

We thought of doing that. But IIRC, unreachable_devices() only covers
the first 16 buses on segment 0. What happens to the bitmap when you
want to cover all possible buses on all possible segments?

We felt that we had to come up with a more in-line way of doing this.


--
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/