From: Giuliano Pochini <pochini@shiny•it>
To: Iain Sandoe <iain@sandoe•co.uk>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Sound skips
Date: Mon, 09 Apr 2001 09:56:20 +0200 (CEST) [thread overview]
Message-ID: <XFMail.010409095620.pochini@shiny.it> (raw)
In-Reply-To: <20010408145245.304002F00D@apollo.valhalla.net>
> Note: this is a completely *different* problem from the PowerComputing
> "DEAD" dbdma one...
Yes, the subject of the message is different too :))
> This problem exist for _all_ PPC Linux users - and _did_ exist for all x86
> users (without) applying Andrew Morton's LL patches.
I didn't noticed the problem on my father's x86, but I'm not
sure. I'll try ASAP.
> Perhaps I'll ask Andrew about libtool (it may still give hassles on x86).
libtool is a bash script.
> If you look at my latest patches they log overruns (reported as xrun in
> /dev/sndstat output).
>
> I get *lots* on all my systems (without LL patches) even when lightly
> loaded.
sndstat ? I didn't looked at that.
>
>>> >(if it doesn't involve libtool).
>>>
>>> hmmm. Have you got any idea what libtool does that is different ?
>>> (does strace work at the moment?)
>>
>> The only unusual thing strace shows is thai it calls rt_sigprocmask()
>> hundred times. rt_sigprocmask() stops irqs for a very short time. A
>> prog that calls it 1M time shows this is not what I'm looking for.
>> I searched in all /arch/ppc for something interesting... nothing. I
>> definitely need a tool to measure how much time the various
>> spinlock_irq's are hold.
>
> Well, I did something for 2.2.x - maybe I'll try and re-do this soon for
> 2.4.x.
I'll try to write a replacement for spin_*lock_irq* to make use of
time base facility to measure times. The problem is I don't know
how to store and export the data so all the kernel can see it. I have
to write a nice /proc interface too. It could take a lot of time...
Bye.
Giuliano Pochini ->)|(<- Shiny Network {AS6665} ->)|(<-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-09 7:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-08 14:52 Sound skips Iain Sandoe
2001-04-09 7:56 ` Giuliano Pochini [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 9:34 Iain Sandoe
2001-03-29 8:52 Iain Sandoe
2001-03-29 15:39 ` Giuliano Pochini
2001-04-07 20:39 ` Giuliano Pochini
2001-03-26 11:51 Iain Sandoe
2001-03-26 16:23 ` Geert Uytterhoeven
2001-03-26 8:56 Iain Sandoe
2001-03-26 10:34 ` Giuliano Pochini
2001-03-28 20:33 ` Giuliano Pochini
2001-03-26 4:30 Iain Sandoe
2001-03-26 7:17 ` Giuliano Pochini
2001-03-24 19:45 Iain Sandoe
2001-03-25 19:41 ` Giuliano Pochini
2001-03-24 15:39 Giuliano Pochini
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=XFMail.010409095620.pochini@shiny.it \
--to=pochini@shiny$(echo .)it \
--cc=iain@sandoe$(echo .)co.uk \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox