From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: mathieu.desnoyers@polymtl.ca,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] WIP pvops trace events
Date: Fri, 17 Apr 2009 17:55:00 +0200 [thread overview]
Message-ID: <20090417155500.GD8253@elte.hu> (raw)
In-Reply-To: <49E888EE.6000003@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Ingo Molnar wrote:
>> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>>
>>
>>> This is my series of pvops tracing patches, consisting of:
>>>
>>> - Split out asm/paravirt_type.h from asm/paravirt.h, so that
>>> trace/events/pvops.h can include the types without getting everything
>>> else.
>>>
>>
>> Ob'sidenote: seems like tracing is driving include file dependency
>> cleanups! The law of unintended consequences (of the positive
>> variety).
>
> The tracing stuff is making the C preprocessor cower and wimper like a
> beaten puppy, so we need to do something to help it...
'beaten puppy' is not the fitting analogy i believe here.
'tortured bastard' might be closer?
Ingo
prev parent reply other threads:[~2009-04-17 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 6:39 [PATCH RFC] WIP pvops trace events Jeremy Fitzhardinge
2009-04-17 6:39 ` [PATCH 1/5] x86/paravirt: split paravirt definitions into paravirt_types.h Jeremy Fitzhardinge
2009-04-17 6:39 ` [PATCH 2/5] x86/pvops: add tracing for all significant pvops entrypoints Jeremy Fitzhardinge
2009-04-17 6:39 ` [PATCH 3/5] x86/paravirt: update tracing for start/end context switch Jeremy Fitzhardinge
2009-04-17 6:39 ` [PATCH 4/5] x86/paravirt: add forward-decl for task_struct Jeremy Fitzhardinge
2009-04-17 6:39 ` [PATCH 5/5] x86/pvops: move tracing around to match CREATE_PVOPS_TRACE_POINTS Jeremy Fitzhardinge
2009-04-17 8:43 ` [PATCH RFC] WIP pvops trace events Ingo Molnar
2009-04-17 13:49 ` Jeremy Fitzhardinge
2009-04-17 15:55 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090417155500.GD8253@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.