From: William Lee Irwin III <wli@holomorphy.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
pavel@elf.ucw.cz, andrea <andrea@suse.de>,
Mikael Pettersson <mikpe@csd.uu.se>,
msw@redhat.com, Ulrich Drepper <drepper@redhat.com>
Subject: Re: [FTF][PATCH] linux-2.4.20-pre5_bad-tsc_A0
Date: Wed, 28 Aug 2002 20:54:37 -0700 [thread overview]
Message-ID: <20020829035437.GE888@holomorphy.com> (raw)
In-Reply-To: <1030584008.3056.53.camel@cog>
On Wed, Aug 28, 2002 at 06:20:07PM -0700, john stultz wrote:
> As long as folks still seem interested in this, I'll keep on maintaining
> it, but if you feel it should just die, let me know.
Is there any chance you could do a 2.5.32 version that skips over
synchronize_tsc_ap() etc. entirely? synchronize_tsc_ap() appears to
oops on 32x NUMA-Q boxen (though it could be io_apic.c running amok).
Cheers,
Bill
prev parent reply other threads:[~2002-08-29 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 1:20 [FTF][PATCH] linux-2.4.20-pre5_bad-tsc_A0 john stultz
2002-08-29 3:54 ` William Lee Irwin III [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=20020829035437.GE888@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=drepper@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=msw@redhat.com \
--cc=pavel@elf.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