All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [BUG] x86 TSC emulation broken
Date: Sun, 23 Jul 2006 19:28:59 +0200	[thread overview]
Message-ID: <44C3B1DB.2040807@domain.hid> (raw)

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

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 generating code).

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.

Before spending "some" time on a clean (in contrast to what I just read
in foreign code...) fix for Xenomai, I would like to cross-check if this
emulation is still considered useful. No one seems to use it, otherwise
we should have received complaints much earlier.

Fix it or drop it?

Jan


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

             reply	other threads:[~2006-07-23 17:28 UTC|newest]

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