linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [BUG] x86_udelay_tsc not honoring notsc
Date: Thu, 19 Sep 2002 21:09:05 -0700	[thread overview]
Message-ID: <20020920040905.GG3530@holomorphy.com> (raw)
In-Reply-To: <466275568.1032469207@[10.10.2.3]>

At some point in the past, I wrote:
>> If so, it's probably not worth mucking around with the bootstrap
>> sequence to deal with something this minor. It's not like it can
>> be mistaken for having hung, as console output is very consistent.
>> Maybe we should give NUMA-Q a couple of minutes instead of 5s?

On Thu, Sep 19, 2002 at 09:00:09PM -0700, Martin J. Bligh wrote:
> Nah, just recode the boot sequence to make them all boot in 
> parallel ;-)
> M.

Do you think cpu wakeup alone could be doing this? If so, then doing
that bit would be relatively isolated (though a slightly larger diff
than changing an NMI oopser timeout).

Does 0xFF broadcast cluster, broadcast low nybble work or is waking
them a cluster at a time required?  This thing is not swift to boot...



Thanks,
Bill

  reply	other threads:[~2002-09-20  4:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20  0:10 [BUG] x86_udelay_tsc not honoring notsc William Lee Irwin III
2002-09-20  3:07 ` Martin J. Bligh
2002-09-20  3:52   ` William Lee Irwin III
2002-09-20  4:00     ` Martin J. Bligh
2002-09-20  4:09       ` William Lee Irwin III [this message]
2002-09-20  4:20         ` Martin J. Bligh

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=20020920040905.GG3530@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).