From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from canuck.infradead.org ([209.217.80.40]:54678 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752598AbXFPIcM (ORCPT ); Sat, 16 Jun 2007 04:32:12 -0400 Subject: Re: [PATCH] Introduce compat_u64 and compat_s64 types From: David Woodhouse In-Reply-To: <200706152322.07739.ak@suse.de> References: <200706151355.57464.ak@suse.de> <200706151454.28854.ak@suse.de> <200706151650.53481.rgetz@blackfin.uclinux.org> <200706152322.07739.ak@suse.de> Content-Type: text/plain Date: Sat, 16 Jun 2007 09:31:41 +0100 Message-Id: <1181982701.25228.615.camel@pmac.infradead.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org To: Andi Kleen Cc: Robin Getz , Alan Cox , David Howells , Arnd Bergmann , Benjamin Herrenschmidt , Linux Kernel Mailing List , Dave Airlie , linux-arch@vger.kernel.org, Andrew Morton , Bernd Schmidt List-ID: On Fri, 2007-06-15 at 23:22 +0200, Andi Kleen wrote: > > For the architecture we use (Blackfin), it does not support unaligned > > accesses, and we purposely never put in the trap/fixup code - we trap, and > > printk("fix your source"); > > For the kernel you should fix up too in addition to the printk. Otherwise > you risk a ping of death in the field with some more obscure protocol. > Also the printk should be load limited. Sometimes you can't. Some architectures don't even take a trap, and on others (FR-V without MMU) it's an imprecise exception. -- dwmw2