netdev - Re: [PATCH 3/20][BNX2]: Add 40-bit DMA workaround for 5708.

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: <1551EAE59135BE47B544934E30FC4FC09400DB@nt-irva-0751.brcm.ad.broadcom.com>
Date:	Wed, 2 May 2007 08:23:40 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"David Miller" <davem@...emloft.net>, jeff@...zik.org
cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 3/20][BNX2]: Add 40-bit DMA workaround for 5708.

David Miller wrote:

> From: Jeff Garzik <jeff@...zik.org>
> Date: Wed, 02 May 2007 03:06:43 -0400
> 
> > Second, CONFIG_HIGHMEM is a bad test for IOMMU presence.  I don't
> > think you /can/ test for IOMMU presence.  Maybe DaveM knows a way
> > that I do not?
> 
> You really can't.
> 
> We have platforms that are both IOMMU and non-IOMMU for the same
> configuration, it isn't known until run-time.
> 
> 
A non-IOMMU system using 64-bit dma_addr_t will always set
CONFIG_HIGHMEM, right?

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html