linux-kernel - Re: [PATCH] pci: enable MSI on 8132

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: <m1fxi82pq0.fsf@fess.ebiederm.org>
Date:	Fri, 20 Feb 2009 23:50:31 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Andrew Morton <akpm@...ux-foundation.org>, david@...g.hm,
	Matthew Wilcox <matthew@....cx>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, DL-MPTFusionLinux@....com,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH] pci: enable MSI on 8132

Robert Hancock <hancockrwd@...il.com> writes:
>
> Is there a reason why we can't just enable the HT MSI mapping for any bridge
> device that has that PCI capability and is underneath an HT bridge?

The code should be under CONFIG_X86 because the rules for enabling HT MSI mappings
are different for other architectures.  But otherwise I can't think of a reason.

> Essentially
> the code for nv_msi_ht_cap_quirk could potentially be applied to all bridges as
> it is currently for NVIDIA and ALi bridges..

Sounds like it would save a fair amount of grief.

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