Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262139AbTIWSBj (ORCPT ); Tue, 23 Sep 2003 14:01:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262161AbTIWSBj (ORCPT ); Tue, 23 Sep 2003 14:01:39 -0400 Received: from usea-naimss2.unisys.com ([192.61.61.104]:54284 "EHLO usea-naimss2.unisys.com") by vger.kernel.org with ESMTP id S262139AbTIWSBf convert rfc822-to-8bit (ORCPT ); Tue, 23 Sep 2003 14:01:35 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: NS83820 2.6.0-test5 driver seems unstable on IA64 Date: Tue, 23 Sep 2003 12:58:59 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NS83820 2.6.0-test5 driver seems unstable on IA64 Thread-Index: AcOB+4f+A/scTi+0S7STcJN0vkPsdAAABdwA From: "Van Maren, Kevin" To: "David S. Miller" , Cc: , , , , , , , , X-OriginalArrivalTime: 23 Sep 2003 17:59:10.0512 (UTC) FILETIME=[63F30B00:01C381FC] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 926 Lines: 22 > > The printk() is rate-controlled and doesn't happen for every unaligned > > access. It's average cost can be made as low as we want to, by adjusting > > the rate. > > But if the event is normal, you shouldn't be logging it as if > it weren't. That's my view on the fpswa printk's (handle_fpu_swa): they are normal, expected, and there is absolutely nothing that can be done about them -- so why print a "warning" about them (even if it is only 5 per second)? If nothing else, toggle the meaning for IA64_THREAD_FPEMU_NOPRINT: turn it ON for special apps. Rate-limited unaligned loads in user space make a lot more sense, since they _may_ point out issues in the code. Kevin - 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/