From owner-svn-src-all@FreeBSD.ORG Sun Nov 2 16:07:56 2014 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA0026CE; Sun, 2 Nov 2014 16:07:56 +0000 (UTC) Received: from mailrelay008.isp.belgacom.be (mailrelay008.isp.belgacom.be [195.238.6.174]) by mx1.freebsd.org (Postfix) with ESMTP id 038743CF; Sun, 2 Nov 2014 16:07:55 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsIIADRWVlRbsIXe/2dsb2JhbABcgw6BIQvUXgQCAoERFwEBAQEBfYQDAQEEOhwjEAsOCgklDyoeBhOIRQHJFQEBAQEBAQQBAQEBAR2REAeESwEEngCWUYN5PC+CSwEBAQ Received: from 222.133-176-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.176.133.222]) by relay.skynet.be with ESMTP; 02 Nov 2014 17:07:47 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.9/8.14.9) with ESMTP id sA2G7k9i002422; Sun, 2 Nov 2014 17:07:46 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Sun, 2 Nov 2014 17:07:46 +0100 From: Tijl Coosemans To: Nathan Whitehorn Subject: Re: svn commit: r273963 - head/sys/dev/agp Message-ID: <20141102170746.287a64e1@kalimero.tijl.coosemans.org> In-Reply-To: <54564D5C.8090100@freebsd.org> References: <201411021126.sA2BQcx4053562@svn.freebsd.org> <54564D5C.8090100@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 16:07:57 -0000 On Sun, 02 Nov 2014 07:27:24 -0800 Nathan Whitehorn wrote: > There is actually a write-combining memory type on PowerPC. You can set > it the same way as on x86 (with VM_MEMATTR_WRITE_COMBINING). Yes, that's what the patch does, but in sys/powerpc (aim/mmu_oea.c, aim/mmu_oea64.c and booke/pmap.c) VM_MEMATTR_WRITE_COMBINING becomes PTE_I meaning Caching Inhibited. Does powerpc do write-combining for this type? That code also maps VM_MEMATTR_WRITE_BACK to PTE_I by the way. I think that should be PTE_M (write-back caching + cache coherency).