From: Ingo Molnar <mingo@elte.hu>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>
Subject: Re: 2.6.12-mm1 boot failure on NUMA box.
Date: Fri, 24 Jun 2005 21:52:48 +0200 [thread overview]
Message-ID: <20050624195248.GA9663@elte.hu> (raw)
In-Reply-To: <320710000.1119632967@flay>
* Martin J. Bligh <mbligh@mbligh.org> wrote:
> > - /*
> > - * In the NUMA case we dont use the TSC as they are not
> > - * synchronized across all CPUs.
> > - */
> > -#ifndef CONFIG_NUMA
> > - if (!use_tsc)
> > -#endif
> > + if (!cpu_has_tsc)
> > /* no locking but a rare wrong value is not a big deal */
> > return jiffies_64 * (1000000000 / HZ);
>
> Humpf. That does look dangerous on a NUMA-Q. The TSCs aren't synced,
> and we can't use them .... have to use PIT, whether the CPUs have TSC
> or not.
is the only problem the unsyncedness? That should be fine as far as the
scheduler is concerned. (we compensate for per-CPU drifts)
Ingo
next prev parent reply other threads:[~2005-06-24 19:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 5:07 2.6.12-mm1 boot failure on NUMA box Martin J. Bligh
2005-06-21 6:29 ` Andrew Morton
2005-06-21 14:22 ` Martin J. Bligh
2005-06-21 20:03 ` Andrew Morton
2005-06-24 14:11 ` Martin J. Bligh
2005-06-24 14:14 ` Con Kolivas
2005-06-24 15:31 ` Martin J. Bligh
2005-06-24 17:01 ` Ingo Molnar
2005-06-24 17:09 ` Martin J. Bligh
2005-06-24 19:52 ` Ingo Molnar [this message]
2005-06-24 20:08 ` Nish Aravamudan
2005-06-24 20:56 ` Martin J. Bligh
2005-06-25 4:00 ` Ingo Molnar
2005-06-25 6:42 ` Martin J. Bligh
2005-06-25 9:09 ` Ingo Molnar
2005-06-25 18:08 ` Lee Revell
2005-06-25 21:03 ` Martin J. Bligh
2005-06-25 21:54 ` Lee Revell
2005-06-28 22:09 ` Martin J. Bligh
[not found] <208690000.1119330454@[10.10.2.4].suse.lists.linux.kernel>
2005-06-21 11:31 ` Andi Kleen
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=20050624195248.GA9663@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
/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