From: yhlu <yhlu.kernel@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: sync_tsc fix the race (so we can boot)
Date: Fri, 29 Jul 2005 17:52:10 -0700 [thread overview]
Message-ID: <86802c4405072917525cfacc38@mail.gmail.com> (raw)
In-Reply-To: <m1oe8lf7o9.fsf@ebiederm.dsl.xmission.com>
I will use linus's latest tree to have a try.
YH
On 7/29/05, Eric W. Biederman <ebiederm@xmission.com> wrote:
> yhlu <yhlu.kernel@gmail.com> writes:
>
> > if using you patch, the
> > "synchronized TSC with CPU" never come out.
> >
> > then with your patch, I add back patch that moving set callin_map from
> > smp_callin to start_secondary. It told me can not inquire the apic for
> > the CPU 1....2....
>
> Hmm. You didn't post enough of a boot log for me to see the problem.
> Does it boot and you don't see the message or is it something
> else.
>
> > Can we put tsc_sync_wait() back to smp_callin?
> >
> > So that it will be executed serially and we can get
> > "synchronized TSC with CPU"?
>
> Currently that just seems silly. That code should be async
> safe.
>
> But it sounds like you have some weird bug I don't understand.
>
> Eric
>
next prev parent reply other threads:[~2005-07-30 0:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 4:03 [PATCH] x86_64: sync_tsc fix the race (so we can boot) Eric W. Biederman
2005-07-28 16:22 ` yhlu
2005-07-28 17:10 ` [PATCH] x86_64 : prefetchw() can fall back to prefetch() if !3DNOW Eric Dumazet
2005-08-03 13:17 ` Andi Kleen
2005-07-28 17:35 ` [PATCH] x86_64: sync_tsc fix the race (so we can boot) yhlu
2005-07-29 3:08 ` Eric W. Biederman
2005-07-29 20:41 ` yhlu
2005-07-29 23:27 ` yhlu
2005-07-30 0:40 ` Eric W. Biederman
2005-07-30 0:52 ` yhlu [this message]
2005-07-30 1:45 ` yhlu
2005-07-29 7:44 ` Andi Kleen
2005-07-29 15:52 ` Eric W. Biederman
2005-07-29 16:04 ` Eric W. Biederman
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=86802c4405072917525cfacc38@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.