From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: [Adeos-main] Re: [SMP-BUG?] inconsistent cpuid after dispatch_wired
Date: Mon, 18 Dec 2006 22:12:34 +0100 [thread overview]
Message-ID: <1166476355.17298.20.camel@domain.hid> (raw)
In-Reply-To: <45868547.6050304@domain.hid>
On Mon, 2006-12-18 at 13:10 +0100, Jan Kiszka wrote:
> Hi Philippe,
>
> actually, I was trying to apply a micro-optimisation on
> __ipipe_handle_irq, but I think I also found a bug on SMP systems (at
> least on x86):
>
> After __ipipe_handle_irq forwarded some IRQ to __ipipe_dispatch_wired
> and the latter returned 1 (i.e. "not deferred"), a pipeline sync is
> triggered using the cpuid read on IRQ entry. But I think that
> __ipipe_dispatch_wired may very well have caused some CPU migration of
> the current context so that reloading the cpuid is required here. This
> is what the first attached patch does.
>
Correct. Applied, thanks.
> Jan
>
>
> PS: The optimisation I was looking at deals with the assumption that a
> wired IRQ may never be also a sticky one, correct?
Correct.
> If yes, the second
> (alternative) patch might be interesting as it avoids to touch the root
> domain data structure and to test for stickiness in the wired case.
> Should shorten the wired IRQ path by a few cycles (or more on cache
> miss...).
Applied, thanks.
--
Philippe.
prev parent reply other threads:[~2006-12-18 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 12:10 [Adeos-main] [SMP-BUG?] inconsistent cpuid after dispatch_wired Jan Kiszka
2006-12-18 21:12 ` Philippe Gerum [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=1166476355.17298.20.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
/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.