linux-kernel - Re: [discuss] A question about GART aperture unmap

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: <ac8af0be0705100300l91f8b38y288dad4b677bf188@mail.gmail.com>
Date:	Thu, 10 May 2007 18:00:15 +0800
From:	"Zhao Forrest" <forrest.zhao@...il.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] A question about GART aperture unmap

> >
> > As we know that CPU prefetch never cross the page boundary, in this
>
> That only applies to sequential prefetch. But speculative execution can
>  prefetch pretty much any address. That is why the clear_kernel_mapping is
> needed.

In BIOS setup, there's "Speculative TLB Reload". Is this "Speculative
TLB Reload" the same as your mentioned speculative execution?
After disabling "Speculative TLB Reload" in BIOS, we could also
experience sync flood and reset when commenting out
clear_kernel_mapping()......

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