linux-kernel - pci_alloc_consistent and memory >= 4GB pre CONFIG_ZONE

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]

Message-ID: <1C27BF3FB8EE3A4D8F901C22ADE1DE0768043556ED@ABGEX72E.FSC.NET>
Date:	Fri, 1 Feb 2008 17:17:25 +0100
From:	"Cestonaro, Thilo" <Thilo.Cestonaro@...itsu-siemens.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: pci_alloc_consistent and memory >= 4GB pre CONFIG_ZONE_DMA32

Hey,

I've a problem with pci_alloc_consistent with Kernel 2.6.5 and memory >= 4GB on a x86_64 machine.
The device can't use the dma_addr which I retrieve from pci_alloc_consistent.
But if the machine has less then 4GB it works fine.

How can I prove that the adress I get from pci_alloc_consistent is dma compatible?
Should pci_alloc_consistent not be used in environments before CONFIG_ZONE_DMA32?

Is there a better way to get dma compatible memory since 2.6.1 (except using kmalloc and GFP_DMA, cause just below 16MB is not enough memory)?

I'm very appreciative for any answer / help.

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