From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26921 invoked by alias); 23 Sep 2008 04:18:38 -0000 Received: (qmail 26914 invoked by uid 22791); 23 Sep 2008 04:18:37 -0000 X-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out3.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 23 Sep 2008 04:17:59 +0000 Received: from spaceape13.eur.corp.google.com (spaceape13.eur.corp.google.com [172.28.16.147]) by smtp-out.google.com with ESMTP id m8N4Ho7s015380 for ; Tue, 23 Sep 2008 05:17:50 +0100 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1222143471; bh=Oy0yx0CQ13A8cch/J3MABvXsiPU=; h=DomainKey-Signature:Message-ID:Date:From:To:Subject:Cc: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-Disposition:References:X-GMailtapped-By; b=Hrpgu2wxW3n04I6 mHy1QnlfVYRdCQXXUCML/pobv2iCe6dt9Dz9IvG8+j2hufu8+TT/EJg1EsmcyfFqji7 hu5Q== DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references:x-gmailtapped-by; b=A+zbUeIdpUfGHJi7vR4gvnWzdnMX+JKcr7vZ0bsoOP17Jo4RJS0mQrJ4cX3ysXYoi vORwUtKCrmeezxIZTGd0A== Received: from wf-out-1314.google.com (wfd26.prod.google.com [10.142.4.26]) by spaceape13.eur.corp.google.com with ESMTP id m8N4Hl1J020176 for ; Mon, 22 Sep 2008 21:17:48 -0700 Received: by wf-out-1314.google.com with SMTP id 26so2097304wfd.26 for ; Mon, 22 Sep 2008 21:17:47 -0700 (PDT) Received: by 10.142.148.10 with SMTP id v10mr1783693wfd.303.1222143467125; Mon, 22 Sep 2008 21:17:47 -0700 (PDT) Received: by 10.142.49.3 with HTTP; Mon, 22 Sep 2008 21:17:46 -0700 (PDT) Message-ID: <33307c790809222117w655894ffoce7950fb72b60e3f@mail.gmail.com> Date: Tue, 23 Sep 2008 04:18:00 -0000 From: "Martin Bligh" To: "Masami Hiramatsu" Subject: Re: Unified tracing buffer Cc: "Steven Rostedt" , "Linus Torvalds" , "Roland Dreier" , "Linux Kernel Mailing List" , "Thomas Gleixner" , "Mathieu Desnoyers" , darren@dvhart.com, "Frank Ch. Eigler" , systemtap-ml In-Reply-To: <48D86C38.9000407@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <33307c790809191433w246c0283l55a57c196664ce77@mail.gmail.com> <33307c790809221313s3532d851g7239c212bc72fe71@mail.gmail.com> <48D81B5F.2030702@redhat.com> <33307c790809221616h5e7410f5gc37c262d83722111@mail.gmail.com> <48D832B6.3010409@redhat.com> <48D86C38.9000407@redhat.com> X-GMailtapped-By: 172.28.16.147 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00755.txt.bz2 > yes, if event c is an interrupt event :-). > > cpu 0 cpu 1 > hit event d > hit event a > log event a > irq event c > log event c > hit event b > log event b > log event d > > so, I think if we really need to order events, we have to stop > irq right after hitting an event. How could you fix that in any practical way?