From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261187AbVGBP4G (ORCPT ); Sat, 2 Jul 2005 11:56:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261188AbVGBP4G (ORCPT ); Sat, 2 Jul 2005 11:56:06 -0400 Received: from opersys.com ([64.40.108.71]:46858 "EHLO www.opersys.com") by vger.kernel.org with ESMTP id S261187AbVGBPzW (ORCPT ); Sat, 2 Jul 2005 11:55:22 -0400 Message-ID: <42C6BB79.8070903@opersys.com> Date: Sat, 02 Jul 2005 12:06:17 -0400 From: Karim Yaghmour Reply-To: karim@opersys.com Organization: Opersys inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en, fr, fr-be, fr-ca, fr-fr MIME-Version: 1.0 To: Michael Raymond CC: linux-kernel , LTT-Dev , Tom Zanussi , Robert Wisniewski , Mathieu Desnoyers , Michel Dagenais Subject: Re: [ltt-dev] [PATCH/RFC] Significantly reworked LTT core References: <42C60001.5050609@opersys.com> <20050702081437.A57232@xanatos.americas.sgi.com> <42C6A58B.6020000@opersys.com> In-Reply-To: <42C6A58B.6020000@opersys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Karim Yaghmour wrote: > I think this one needs more thinking ... I did think about adding such a > hook, but I didn't like the idea of it, it just seems unclean. After all > the problem is limited to a very small subset of events, namely NMIs and > page fault traps. One thing I was thinking about is that in both these > cases there's always an entry event and an exit event. ltt_mux could then > coordinate using these events. IOW, if it just got an NMI entry, it > doesn't allow any other event to get logged until it sees the NMI exit > go by ... same for page faults. By doing this, we can just keep just one > hook: ltt_mux. Right? Brain was slow this morning. What we're trying to do is to avoid getting those very NMIs and page faults into the logging path if we're already in that path ... That's different from what my brain came up with this morning. We may need that hook after all ... something like: if (ltt_post) ltt_post(...); Karim -- Author, Speaker, Developer, Consultant Pushing Embedded and Real-Time Linux Systems Beyond the Limits http://www.opersys.com || karim@opersys.com || 1-866-677-4546