Groups > linux.kernel > #1197119

Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()

From	Borislav Petkov <bp@alien8.de>
Newsgroups	linux.kernel
Subject	Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()
Date	2015-07-31 17:30 +0200
Message-ID	<pSkpZ-1ly-33@gated-at.bofh.it> (permalink)
References	(1 earlier) <puiz0-71G-9@gated-at.bofh.it> <puKvg-6dj-35@gated-at.bofh.it> <pSio9-6zT-1@gated-at.bofh.it> <pSjNg-mz-19@gated-at.bofh.it> <pSk6B-Yx-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Jul 31, 2015 at 05:08:06PM +0200, Peter Zijlstra wrote:
> But its things like set_memory_XX(), and afaict that's all buggy against
> MTRR modifications.

I think the idea is to not do any MTRR modifications at some point:

From Documentation/x86/pat.txt:

"... Ideally mtrr_add() usage will be phased out in favor of
arch_phys_wc_add() which will be a no-op on PAT enabled systems. The
region over which a arch_phys_wc_add() is made, should already have been
ioremapped with WC attributes or PAT entries, this can be done by using
ioremap_wc() / set_memory_wc()."

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup() Peter Zijlstra <peterz@infradead.org> - 2015-07-31 17:10 +0200
  Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup() Borislav Petkov <bp@alien8.de> - 2015-07-31 17:30 +0200

csiph-web