From: Christian Hoelbling <christian.holbling@cern.ch>
To: cpufreq@www.linux.org.uk
Subject: [PATCH] 2.6.5 speedstep on P4Ms
Date: Fri, 11 Jun 2004 00:30:03 +0000 [thread overview]
Message-ID: <40C8FD0B.4050108@cern.ch> (raw)
>
>
>>/ i also wonder about one thing, maybe you can help me on that. with the
>/>/ old speedstep driver, i would have occational hard freezups of my
>/>/ machine. this seems to be gone (just experimental evidence, since i
>/>/ didn't have one in a few days now where before they occured about
>/>/ hourly). so my guess is that something in this patch must have corrected
>/>/ it. since my machine just has one physical cpu, i really don't
>/>/ understand what went wrong before. do you have any idea on that?
>/>/
>/
>IMHO the lockup is due to the fact we use local_irq_disable() but it
>should be done more globally. I believe you may still have some lockup
>still.
>
>
i didn't, but that might be pure chance. :-) so does one have to
disable the interrupts on both siblings of a HT CPU seperately? i just
don't know how this works.
thanks,
chris
next reply other threads:[~2004-06-11 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 0:30 Christian Hoelbling [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 0:21 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-08 17:15 Christian Hoelbling
2004-06-08 15:30 ` Bruno Ducrot
2004-06-08 23:53 ` Christian Hoelbling
2004-06-09 15:47 ` Dominik Brodowski
2004-06-09 16:09 ` Bruno Ducrot
2004-06-09 16:29 ` Dave Jones
2004-06-09 16:53 ` Dominik Brodowski
2004-06-09 18:32 ` Mattia Dongili
2004-06-10 0:46 ` Christian Hoelbling
2004-06-10 8:30 ` Dominik Brodowski
2004-06-10 11:20 ` Dave Jones
2004-06-10 9:10 ` Bruno Ducrot
2004-06-10 15:37 ` Bruno Ducrot
2004-06-10 16:44 ` Dominik Brodowski
2004-06-10 19:44 ` Bruno Ducrot
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=40C8FD0B.4050108@cern.ch \
--to=christian.holbling@cern.ch \
--cc=cpufreq@www.linux.org.uk \
--cc=holbling@cpt.univ-mrs.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox