linux-kernel - Re: [PATCH] x86_64: reserve dma32 early for gart

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

Message-ID: <86802c440803071745l33584535jb998b262e59a915a@mail.gmail.com>
Date:	Fri, 7 Mar 2008 17:45:54 -0800
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86_64: reserve dma32 early for gart

On Fri, Mar 7, 2008 at 3:20 PM, Andi Kleen <ak@...e.de> wrote:
> On Saturday 08 March 2008 00:02:50 Yinghai Lu wrote:
>  >
>  >
>
>
>
>  >solution will be:
>  >1. make memmap allocation get memory above 4G...
>  >2. reserve some dma32 range early before we try to set up memmap for all.
>  >and release that before pci_iommu_alloc, so gart or swiotlb could get some
>  >range under 4g limit for sure.
>
>  Funny we had (1) before vmemmap for some time, but it looks like
>  that regressed with vmemmap Anyways I think (1) alone should be enough, is (2)
>  really needed?

even vmemmap is disabled, still need (2).

(1) is not there yet.

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