From: Vojtech Pavlik <vojtech@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: rdtsc to mili secs?
Date: Sun, 19 Nov 2000 10:21:43 +0100 [thread overview]
Message-ID: <20001119102143.A529@suse.cz> (raw)
In-Reply-To: <3A078C65.B3C146EC@mira.net> <20001116115730.A665@suse.cz> <8v1pfj$p5e$1@cesium.transmeta.com> <20001118211349.B382@bug.ucw.cz> <8v74fm$2d7$1@cesium.transmeta.com>
In-Reply-To: <8v74fm$2d7$1@cesium.transmeta.com>; from hpa@zytor.com on Sat, Nov 18, 2000 at 03:48:06PM -0800
On Sat, Nov 18, 2000 at 03:48:06PM -0800, H. Peter Anvin wrote:
> Followup to: <20001118211349.B382@bug.ucw.cz>
> By author: Pavel Machek <pavel@suse.cz>
> In newsgroup: linux.dev.kernel
>
> > > Actually, on machines where RDTSC works correctly, you'd like to use
> > > that to detect a lost timer interrupt.
> > >
> > > It's tough, it really is :(
> >
> > Well, my patch did not do that but you probably want lost timer
> > interrupt detection so that you avoid false alarms.
> >
> > But that means you can no longer detect speed change after 10msec:
> >
> > going from 150MHz to 300MHz is very similar to one lost timer
> > interrupt.
> >
>
> That's the point.
... and, you still can have both - detection of lost timer interrupts
and detection of speed changing. It'll take longer than 10ms to notice,
though (I think 20 or 30 will just do it).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-19 9:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-05 23:09 rdtsc to mili secs? Sushil Agarwal
2000-11-06 0:10 ` Andrea Arcangeli
2000-11-06 0:28 ` Alan Cox
2000-11-06 0:34 ` Andrea Arcangeli
2000-11-06 0:46 ` Alan Cox
2000-11-06 17:17 ` Anton Blanchard
2000-11-06 17:27 ` Alan Cox
2000-11-07 5:00 ` Antony Suter
2000-11-07 6:10 ` H. Peter Anvin
2000-11-07 12:18 ` Alan Cox
2000-11-10 14:42 ` Pavel Machek
2000-11-10 21:38 ` H. Peter Anvin
2000-11-10 22:23 ` Rogier Wolff
2000-11-10 23:00 ` H. Peter Anvin
2000-11-14 21:22 ` Pavel Machek
2000-11-15 21:05 ` H. Peter Anvin
2000-11-16 10:57 ` Vojtech Pavlik
2000-11-16 23:09 ` H. Peter Anvin
2000-11-18 20:13 ` Pavel Machek
2000-11-18 23:48 ` H. Peter Anvin
2000-11-19 9:21 ` Vojtech Pavlik [this message]
2000-11-18 20:12 ` Pavel Machek
2000-11-18 22:13 ` Vojtech Pavlik
2000-11-19 20:24 ` Pavel Machek
2000-11-19 21:46 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 8:15 ming_l
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=20001119102143.A529@suse.cz \
--to=vojtech@suse.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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