All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Stelian Pop <stelian@domain.hid>, Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] [PATCH] fix hw-timer setup/cleanup for i386
Date: Fri, 12 Oct 2007 13:15:31 +0200	[thread overview]
Message-ID: <470F5753.5020809@domain.hid> (raw)
In-Reply-To: <20071012110054.GA26325@domain.hid>

Stelian Pop wrote:
> On Fri, Oct 12, 2007 at 11:14:43AM +0200, Jan Kiszka wrote:
> 
>> Hmm, that's not too different from my own test setup.
> 
> I'm attaching the .config and dmesg in case you see something strange.
> 
>> /proc/xenomai/timerstat/master may provide further hints about the state
>> of the host timer (please keep my patch applied for this).
> 
> /proc/xenomai/timerstat/master says:
> 
> CPU  SCHEDULED   FIRED       TIMEOUT    INTERVAL   HANDLER      NAME
> 0    1           1           -          -          NULL         [host-timer]
> 
>> Also, you
>> could take an I-pipe trace around the timer takeover and the following
>> few milliseconds, using the new trigger feature:
>>
>> echo rthal_timer_request > /proc/ipipe/trace/trigger
> 
> It gives this:
> 
> root@domain.hid# cat /proc/ipipe/trace/max

/frozen holds the result. Also, a bit more post_trace_points may help to
see what goes on after that function is called.

> 
>> BTW, does the latency test of Xenomai work?
> 
> No. It hangs after "warming up". I'm able to interrupt with ^C and then
> it prints a single line showing a max latency of 208983.492 ms (same value
> on several invocations).

Ah, then we may fail to program the APIC appropriately. That would need
a closer look if you want to dig into this. /me is going to be
distracted from this for now.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2007-10-12 11:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 20:47 [Xenomai-core] [PATCH] fix hw-timer setup/cleanup for i386 Jan Kiszka
2007-10-12  8:58 ` Stelian Pop
2007-10-12  9:14   ` Jan Kiszka
2007-10-12 11:00     ` Stelian Pop
2007-10-12 11:15       ` Jan Kiszka [this message]
2007-10-12 13:19         ` Stelian Pop
2007-10-12 13:39           ` Jan Kiszka
2007-10-12 13:41           ` Philippe Gerum
2007-10-12 14:26             ` Stelian Pop
2007-10-12 19:53       ` Jan Kiszka
2007-10-12 20:22         ` Stelian Pop
2007-10-12 21:51           ` Stelian Pop
2007-10-12 21:58             ` Philippe Gerum
2007-10-13 14:28               ` Stelian Pop
2007-10-13 14:42                 ` Jan Kiszka
2007-10-13 16:12                   ` Stelian Pop
2007-10-13 16:35                     ` Philippe Gerum
2007-10-13 16:38                     ` Jan Kiszka
2007-10-13 20:55                       ` Stelian Pop
2007-10-13 14:32           ` Stelian Pop
2007-10-12  9:00 ` Jan Kiszka
2007-10-12  9:16 ` Philippe Gerum
2007-10-12  9:47   ` Jan Kiszka
2007-10-12 12:48     ` 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=470F5753.5020809@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Xenomai-core@domain.hid \
    --cc=stelian@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.