From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davidm@hpl.hp.com
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
marcelo@conectiva.com.br (Marcelo Tosatti),
akpm@zip.com.au (Andrew Morton),
j-nomura@ce.jp.nec.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)
Date: Sat, 8 Dec 2001 20:45:07 +0000 (GMT) [thread overview]
Message-ID: <E16CoLL-0002bW-00@the-village.bc.nu> (raw)
In-Reply-To: <15378.17075.960942.357075@napali.hpl.hp.com> from "David Mosberger" at Dec 08, 2001 08:41:23 AM
> Alan> x86_udelay_tsc wont have been set at that point so the main
> Alan> timer is still being used.
>
> x86 does use current_cpu_data.loops_per_jiffy in the non-TSC case, no?
I believe so. So we should propogate that across earlier, although its
not needed for our current console drivers that I can see
next prev parent reply other threads:[~2001-12-08 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 5:46 [PATCH] 2.4.16 kernel/printk.c (per processor initialization check) j-nomura
2001-12-03 9:20 ` Andrew Morton
2001-12-03 10:32 ` j-nomura
2001-12-04 1:45 ` [PATCH] 2.4.16 kernel/printk.c (per processor initializationcheck) Andrew Morton
2001-12-06 5:01 ` j-nomura
2001-12-07 3:40 ` [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck) Andrew Morton
2001-12-07 18:52 ` Marcelo Tosatti
2001-12-07 20:52 ` William Lee Irwin III
2001-12-07 21:37 ` David Mosberger
2001-12-07 20:47 ` Marcelo Tosatti
2001-12-07 22:08 ` Alan Cox
2001-12-07 22:14 ` Christopher Friesen
2001-12-07 22:17 ` David Mosberger
2001-12-07 21:09 ` Marcelo Tosatti
2001-12-08 1:10 ` David Mosberger
2001-12-08 11:27 ` Alan Cox
2001-12-08 16:41 ` David Mosberger
2001-12-08 20:45 ` Alan Cox [this message]
2001-12-09 0:32 ` David Mosberger
2001-12-09 0:55 ` Alan Cox
2001-12-09 0:58 ` David Mosberger
2001-12-09 1:14 ` David Mosberger
2001-12-09 1:32 ` Alan Cox
2001-12-09 1:15 ` Alan Cox
2001-12-08 17:36 Manfred Spraul
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=E16CoLL-0002bW-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@zip.com.au \
--cc=davidm@hpl.hp.com \
--cc=j-nomura@ce.jp.nec.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
all inboxes | Powered by JetHome®