From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-f49.google.com (mail-yh0-f49.google.com [209.85.213.49]) by kanga.kvack.org (Postfix) with ESMTP id 168B66B00BB for ; Wed, 10 Sep 2014 17:58:30 -0400 (EDT) Received: by mail-yh0-f49.google.com with SMTP id z6so11467082yhz.8 for ; Wed, 10 Sep 2014 14:58:29 -0700 (PDT) Received: from g4t3427.houston.hp.com (g4t3427.houston.hp.com. [15.201.208.55]) by mx.google.com with ESMTPS id t36si12948016yhp.180.2014.09.10.14.58.29 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 10 Sep 2014 14:58:29 -0700 (PDT) Message-ID: <1410385673.28990.313.camel@misato.fc.hp.com> Subject: Re: [PATCH v2 2/6] x86, mm, pat: Change reserve_memtype() to handle WT From: Toshi Kani Date: Wed, 10 Sep 2014 15:47:53 -0600 In-Reply-To: <5410C4F7.4080704@zytor.com> References: <1410367910-6026-1-git-send-email-toshi.kani@hp.com> <1410367910-6026-3-git-send-email-toshi.kani@hp.com> <1410377428.28990.260.camel@misato.fc.hp.com> <5410B10A.4030207@zytor.com> <1410381050.28990.295.camel@misato.fc.hp.com> <1410383484.28990.303.camel@misato.fc.hp.com> <5410C4F7.4080704@zytor.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "H. Peter Anvin" Cc: Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Andrew Morton , Arnd Bergmann , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Juergen Gross , Stefan Bader , Henrique de Moraes Holschuh , Yigal Korman , Konrad Rzeszutek Wilk On Wed, 2014-09-10 at 14:39 -0700, H. Peter Anvin wrote: > On 09/10/2014 02:27 PM, Andy Lutomirski wrote: > >> > >> That's possible, but the only benefit is that we can enable WT on > >> pre-PAT systems, which I do not think anyone cares now... WB & UC work > >> on pre-PAT systems. WC & WT need PAT. I think this requirement is > >> reasonable. > > > > It might end up being a cleanup, though. A whole bunch of > > rarely-exercised if (!pat_enabled) things would go away. > > > > Yes. Don't think of it as PAT vs non-PAT. Think of it as a specific > set of cache types available on different processors. The fact that you > may have to frob an MSR to initialize it is almost trivial in comparison. Right. Thanks, -Toshi -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org