All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] x86 TSC emulation broken
Date: Sun, 23 Jul 2006 23:22:12 +0200	[thread overview]
Message-ID: <1153689732.8053.32.camel@domain.hid> (raw)
In-Reply-To: <44C3E17C.2050906@domain.hid>

On Sun, 2006-07-23 at 22:52 +0200, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Sun, 2006-07-23 at 19:28 +0200, Jan Kiszka wrote:
> >> Hi,
> >>
> >> I happened to switch on some CPU type that enabled the Xenomai's TSC
> >> emulation code. The result was an ugly lock-up: endless loop in the
> >> timer IRQ handler.
> >>
> >> The reason: the TSC emulation collides with the VT sound output / the PC
> >> speaker driver. Over 2.6, one can easily avoid this my switching off
> >> CONFIG_INPUT_PCSPKR. 2.4 requires to export and than manipulate
> >> kb_mksound (the pointer to the sound gen*
> >> erating code).
> > 
> > There is an issue in the Adeos 2.4 patch (1.2-05) which is not
> > preventing the kernel from poking into the 8254 registers to determine
> > the current time offset.
> 
> But the TSC emulation itself is not an Adeos service. Shouldn't it be
> better moved?

Unfortunately, we can't do that. The relevant code is in
arch/i386/kernel/time.c, do_slow_gettimeoffset(), you just can't
abstract this from the kernel sanely. It's a recurring issue with any
Adeos port over x86, and this got more complex with 2.6.

Btw, it's not an emulation issue that Adeos processes that way, it's
about dealing with the true owner of the PIT - as a non-virtualizable
resource -, i.e. Linux, or some domain above it. When Linux does not
"own" the PIT, it should refrain from touching it, period; and that's
what this code actually ensures. This is consistent with
ipipe_tune_timer(), which on some archs, is even used to tell Linux that
some domain is grabbing the timer for its own use (e.g. ia64).

>  Then I would happily leave it up to you. :)

I've a fix pending for the do_slow_gettimeofset() issue in 2.4 (2.6 is
fine). Adeos could export kd_mksound too, even if it's a terminally ugly
way of fixing this, but I have no better approach at hand.

> > 
> >> The latter pointer rang some bell. I once fixed a broken RTAI build due
> >> to that code. So I pulled out vulcano and actually found the related
> >> code + an extension of the original ipipe patch to export kb_mksound. I
> >> guess it would have been too complicated for Paolo to explain the reason
> >> of this export to us...
> >>
> >> Anyway, this digging revealed another potential breakage in the
> >> emulation code: RTAI takes care to read the emulated TSC at least once
> >> per 50 ms, to avoid overflows I assume. Xenomai does not.
> > 
> > Mm, through the host timer service, it should at least each 10ms period.
> 
> Yeah, true. I probably got blinded by the existing RTAI code.

I recall having once thoroughly debugged the non-TSC case circa fusion
0.6.4 or so, this is why I'm relatively confident that we should be able
to reactivate such support without too much burden. It's confined in the
HAL, so the impact on the rest of the code is minimal.

>  There is
> just the likely theoretical case that there is no host tick (LAPIC +
> emulated TSC? Not configurable, is it?).
> 

Nope; in the LAPIC case, the hw must provide a TSC anyway.

> Jan
> 
-- 
Philippe.




      reply	other threads:[~2006-07-23 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23 17:28 [Xenomai-core] [BUG] x86 TSC emulation broken Jan Kiszka
2006-07-23 20:28 ` Philippe Gerum
2006-07-23 20:52   ` Jan Kiszka
2006-07-23 21:22     ` 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=1153689732.8053.32.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@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.