linux-kernel - Re: [PATCH v4 0/7] mtrr, mm, x86: Enhance MTRR checks for huge I/O mapping

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]

Date:	Tue, 24 Mar 2015 15:43:24 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Toshi Kani <toshi.kani@...com>
Cc:	hpa@...or.com, tglx@...utronix.de, mingo@...hat.com,
	linux-mm@...ck.org, x86@...nel.org, linux-kernel@...r.kernel.org,
	dave.hansen@...el.com, Elliott@...com, pebolle@...cali.nl
Subject: Re: [PATCH v4 0/7] mtrr, mm, x86: Enhance MTRR checks for huge I/O
 mapping

On Tue, 24 Mar 2015 16:08:34 -0600 Toshi Kani <toshi.kani@...com> wrote:

> This patchset enhances MTRR checks for the kernel huge I/O mapping,
> which was enabled by the patchset below:
>   https://lkml.org/lkml/2015/3/3/589
> 
> The following functional changes are made in patch 7/7.
>  - Allow pud_set_huge() and pmd_set_huge() to create a huge page
>    mapping to a range covered by a single MTRR entry of any memory
>    type.
>  - Log a pr_warn() message when a specified PMD map range spans more
>    than a single MTRR entry.  Drivers should make a mapping request
>    aligned to a single MTRR entry when the range is covered by MTRRs.
> 

OK, I grabbed these after barely looking at them, to get them a bit of
runtime testing.

I'll await guidance from the x86 maintainers regarding next steps?
--
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/