Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756642AbbDOU5Q (ORCPT ); Wed, 15 Apr 2015 16:57:16 -0400 Received: from terminus.zytor.com ([198.137.202.10]:34615 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756547AbbDOU5E (ORCPT ); Wed, 15 Apr 2015 16:57:04 -0400 Message-ID: <552ED06E.8030303@zytor.com> Date: Wed, 15 Apr 2015 13:56:14 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Andy Lutomirski , "Luis R. Rodriguez" , linux-rdma@vger.kernel.org CC: Toshi Kani , Ingo Molnar , "linux-kernel@vger.kernel.org" , Hal Rosenstock , Sean Hefty , Suresh Siddha , Rickard Strandqvist , Mike Marciniszyn , Roland Dreier , Juergen Gross , Mauro Carvalho Chehab , Andy Walls , Borislav Petkov , Mel Gorman , Vlastimil Babka , Davidlohr Bueso , Dave Hansen , Jean-Christophe Plagniol-Villard , Thomas Gleixner , =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= , Linux Fbdev development list , linux-media@vger.kernel.org, X86 ML Subject: Re: ioremap_uc() followed by set_memory_wc() - burrying MTRR References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1286 Lines: 32 On 04/15/2015 01:42 PM, Andy Lutomirski wrote: > > I disagree. We should try to NACK any new code that can't function > without MTRRs. > > (Plus, ARM is growing in popularity in the server space, and ARM quite > sensibly doesn't have MTRRs.) > Yes. People need to understand that MTRRs are fundamentally a transitional solution, a replacement for the KEN# logic in the P4 and P5 generation processors. The KEN# logic in the chipset would notify the CPU that a specific address should not be cached, without affecting the software (which may have been written for x86s built before caching existed, even.) MTRRs move this to the head end, so the CPU knows ahead of time what to do, as is required with newer architectures. It also enabled write combining in a transparent fashion. However, it is still transitional; it is there to describe the underlying constraints of the memory system so that code which doesn't use paging can run at all, but the only thing that can actually scale is PAT. -hpa -- 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/