linux-kernel - Re: [git patch] improve INTx toggle for PCI MSI

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6dc076840612071900r657e78dag1377312d86042c67@mail.gmail.com>
Date:	Fri, 8 Dec 2006 12:00:31 +0900
From:	"Takashi Iwai" <takashi.iwai@...il.com>
To:	"Linus Torvalds" <torvalds@...l.org>
Cc:	"Jeff Garzik" <jeff@...zik.org>, "Takashi Iwai" <tiwai@...e.de>,
	"Andrew Morton" <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>, gregkh@...e.de,
	barkalow@...ervon.org
Subject: Re: [git patch] improve INTx toggle for PCI MSI

2006/12/8, Linus Torvalds <torvalds@...l.org>:
>
>
> On Thu, 7 Dec 2006, Jeff Garzik wrote:
> >
> > "it boots" on ICH7 at least.
>
> Ok. Pulled, pushed out.
>
> There was some noise saying that this may actually fix the problems with
> the NVidia "Intel HDA" sound situation? Can people who saw that issue try
> it out whether this just makes MSI works for them?
>
> Takashi added to the To: field, because he hopefully remembers and has a
> clue about the proper identities in question.. Iirc, you needed to have
> not only a NVidia chipset, but also have the legacy interrupt shared with
> some other device to see the problem.

Well, I'm on vacation now, so cannot answer much, too :)

IIRC, the problem was with HD-audio and network devices on Nvidia.
The explicit call of pci_intx() (currently implemented in hd-audio
driver locally) helped avoiding the orphan irq problem, but doesn't
fix the MSI problem itself.  (Some might have been fixed indeed,
but I don't have reports in hands.)


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