Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()
- From: Borislav Petkov <bp@xxxxxxxxx>
- Date: Fri, 31 Jul 2015 16:44:52 +0200
- Cc: mingo@xxxxxxxxxx, hpa@xxxxxxxxx, dvlasenk@xxxxxxxxxx, bp@xxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, brgerst@xxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-mm@xxxxxxxxx, luto@xxxxxxxxxxxxxx, mcgrof@xxxxxxxx, toshi.kani@xxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20150731131802.GW25159@twins.programming.kicks-ass.net>
- User-agent: Mutt/1.5.23 (2014-03-12)
On Fri, Jul 31, 2015 at 03:18:02PM +0200, Peter Zijlstra wrote:
> Using these functions with preemption enabled is racy against MTRR
> updates. And if that race is ok, at the very least explain that it is
> indeed racy and why this is not a problem.
Right, so Luis has been working on burying direct MTRR access so
after that work is done, we'll be using only PAT for changing memory
attributes. Look at arch_phys_wc_add() and all those fbdev users of
mtrr_add() which get converted to that thing...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
