Subject: Re: How to lock current->signal->tty
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jes Sorensen <jes@sgi.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, linux-kernel@vger.kernel.org
In-Reply-To: <yq0u04mtjni.fsf@jaguar.mkp.net>
References: <1155050242.5729.88.camel@localhost.localdomain>
	 <44D8A97B.30607@linux.intel.com>
	 <1155051876.5729.93.camel@localhost.localdomain>
	 <20060808164127.GA11392@intel.com>
	 <1155059405.5729.103.camel@localhost.localdomain>
	 <yq0u04mtjni.fsf@jaguar.mkp.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 09 Aug 2006 11:44:10 +0100
Message-Id: <1155120250.5729.146.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 971
Lines: 23

Ar Mer, 2006-08-09 am 04:09 -0400, ysgrifennodd Jes Sorensen:
> Personally I don't like the current approach. However, I believe the
> philosophy behind it is that users rarely look in dmesg and they
> should be notified (and beaten with a stick) when their badly written
> app spawns unaligned accesses which end up being emulated by the
> kernel.

The users won't seem the anyway, they are hidden behind the GUI.

> These messages are normally caused by userland code, so kprobes
> probably wont do much good :)

Jes, read up on kprobes a little if you think its of no use in these
kind of situations. A systemtap script to count/measure alignment fault
rates and see who is causing the load isn't very hard to write.

Alan

-
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/