From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [RFC] algorithm for handling bad cachelines Date: Tue, 27 Mar 2012 15:34:53 +0100 Message-ID: <1332858905_114387@CP5-2952> References: <20120327071943.061bba40@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id 8BD01A0C0E for ; Tue, 27 Mar 2012 07:35:08 -0700 (PDT) In-Reply-To: <20120327071943.061bba40@bwidawsk.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Ben Widawsky , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Tue, 27 Mar 2012 07:19:43 -0700, Ben Widawsky wrote: > Any feedback is highly appreciated. I couldn't really find much > precedent for doing this in other drivers, so pointers to similar > things would also be highly welcome. badblocks and badram (memmap) both seem to be similar situations. A comma-separated list works when the number is quite small, otherwise an ioctl. Of course that requires us to be able to reprogram the cache on the fly. -Chris -- Chris Wilson, Intel Open Source Technology Centre