linux-kernel - Re: [PATCH 0/7] Boot IRQ quirks and rerouting

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:	Wed, 4 Jun 2008 19:51:15 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Thomas Gleixner <tglx@...utronix.de>
cc:	Stefan Assmann <sassmann@...e.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Olaf Dabrunz <od@...e.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jon Masters <jonathan@...masters.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Boot IRQ quirks and rerouting

On Wed, 4 Jun 2008, Thomas Gleixner wrote:

> >  Anyway, my other questions remain open.  How is the INTx message actually
> > delivered to the ICH? 
> 
> I have roughly as much clue as you about that. The datashi^Heet is not
> really helpful.

 I haven't been following Intel's datasheets recently.  They usually do
publish all the necessary bits, but they are scattered around, so you
really have to read them all.  Chances are it's mentioned somewhere.  
Besides, I have no access to the PCI Express spec and there may be further
interesting bits there.  I suppose Intel can be queried directly too,
especially by the interested corporate parties.

> > And why is the command line option needed?
> 
> We don't want to impose that in the first place, but OTOH to get test
> coverage it's probably better to do it unconditionally.

 I gather with the workarounds disabled affected systems are useless 
anyway, so what's the point?

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