From: george anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: marcelo <marcelo@conectiva.com.br>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL][PATCH] cpu_has_tsc cleanup
Date: Thu, 08 Aug 2002 12:56:59 -0700 [thread overview]
Message-ID: <3D52CD0B.AF8C5068@mvista.com> (raw)
In-Reply-To: 1028765030.22918.166.camel@cog
john stultz wrote:
>
> Marcelo,
>
> Here is a trivial cleanup patch that replaces:
> test_bit(X86_FEATURE_TSC, &boot_cpu_data.x86_capability)
> w/ the cpu_has_tsc macro.
>
> I believe this was originally by Brian Gerst for 2.5
>
This patch has a problem in the TSC not defined case in that
it access the PIT with out taking the required
locks. spin_lock_irq(&i8253_lock) is used to protect
the PIT...
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
prev parent reply other threads:[~2002-08-08 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 0:03 [TRIVIAL][PATCH] cpu_has_tsc cleanup john stultz
2002-08-08 19:56 ` george anzinger [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=3D52CD0B.AF8C5068@mvista.com \
--to=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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