All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [PATCH] x86_64: cleanup IRQ on/off tracing
Date: Tue, 20 Nov 2007 08:47:31 +0100	[thread overview]
Message-ID: <47429113.9080705@domain.hid> (raw)
In-Reply-To: <4741CAEE.7020003@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]

Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Tracing of IRQ on/off paths on x86_64 currently suffers from heavy
>> over-instrumentation.
> 
> I understand the point of grouping ipipe_trace_begin/ipipe_trace_end
> statements inside the .interrupt macros and using a lightweight thunk
> code since we are already covered by the SAVE_ARGS prologue, but I find
> the following hunk suspicious, since unlike i386, we do not virtualize
> inline sti/cli ops for x86_64. My concern is that removing this
> instrumentation would leave us naked in the cold the day some subtle
> upstream change introduces a hw masked section we don't immediately
> notice; such trace points would precisely help us spotting it.

The situation is not that different compared to i386:
 - we do not add or remove enabling/disabled points
 - we rely on the correctness of mainline here, so we are not on our own
   anyway
 - if things actually change in mainline, the tracer will probably be
   the last indicator for it (patching breaks and/or leaking clis will
   fairly visible impact)

On the other side, there was a good reason not to instrument cli/sti in
the assembly exit/entry code on i386, just like it is on x86_64: The
effort to get worthwhile outputs is noticeable. As you see, the current
approach is not very helpful due to loosing the caller context (thanks
to the thunks). And those points only mark uninteresting micro paths,
thus create a lot of noise in normal traces.

So, I see not good reason for fixing this instrumentation and still vote
for killing it.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-11-20  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 18:50 [Adeos-main] [PATCH] x86_64: cleanup IRQ on/off tracing Jan Kiszka
2007-11-19 17:42 ` Philippe Gerum
2007-11-20  7:47   ` Jan Kiszka [this message]
2007-11-20 10:19     ` Philippe Gerum
2007-11-20 11:50       ` Jan Kiszka
2007-11-20 13:50         ` Philippe Gerum

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=47429113.9080705@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@xenomai.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.