From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (not verified)) by ozlabs.org (Postfix) with ESMTPS id B126B2C03DF for ; Mon, 24 Jun 2013 13:47:12 +1000 (EST) Received: by mail-ie0-f175.google.com with SMTP id a13so23920724iee.34 for ; Sun, 23 Jun 2013 20:47:09 -0700 (PDT) References: <1371945647.3944.106.camel@pasglop> <1372036573.3944.115.camel@pasglop> Mime-Version: 1.0 (1.0) In-Reply-To: <1372036573.3944.115.camel@pasglop> Content-Type: text/plain; charset=us-ascii Message-Id: From: Peter LaDow Subject: Re: Inbound PCI and Memory Corruption Date: Sun, 23 Jun 2013 20:47:04 -0700 To: Benjamin Herrenschmidt Cc: Peter LaDow , "linuxppc-dev@lists.ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >=20 >=20 > On Jun 23, 2013, at 6:16 PM, Benjamin Herrenschmidt wrote: >> Also dbl check that the MMU is indeed mapping all these pages with the >> "M" bit. >=20 > Just to be clear, do you mean the e1000 registers in PCI space? Or the RAM= pages? >=20 > Thanks, > Pete