From: yhlu <yhlu.kernel@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: Mike Waychison <mikew@google.com>,
Peter Buckingham <peter@pantasys.com>,
linux-kernel@vger.kernel.org,
"discuss@x86-64.org" <discuss@x86-64.org>
Subject: Re: [discuss] Re: 2.6.13-rc2 with dual way dual core ck804 MB
Date: Fri, 12 Aug 2005 09:18:07 -0700 [thread overview]
Message-ID: <86802c4405081209187e51878@mail.gmail.com> (raw)
In-Reply-To: <20050812130725.GL8974@wotan.suse.de>
good, I will produce one patch next week.
YH
On 8/12/05, Andi Kleen <ak@suse.de> wrote:
> On Thu, Aug 11, 2005 at 11:59:21PM -0700, yhlu wrote:
> > andi,
> >
> > is it possible for
> > after the AP1 call_in is done and before AP1 get in tsc_sync_wait
> > The AP2 call_in done. and then AP1 get in tsc_sync_wait and before it
> > done, AP2 get in tsc_sync_wait too.
> >
> > sync_master can not figure out from AP1 or AP2 because only have
> > go[MASTER] and go{SLAVE].
>
> Ok, you're right. It's better to move it to before callin map.
>
> -Andi
>
next prev parent reply other threads:[~2005-08-12 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 0:56 2.6.13-rc2 with dual way dual core ck804 MB YhLu
2005-08-10 23:14 ` Mike Waychison
2005-08-10 23:26 ` [discuss] " Andi Kleen
2005-08-10 23:42 ` yhlu
2005-08-11 0:04 ` Andi Kleen
2005-08-11 0:17 ` yhlu
2005-08-11 0:23 ` yhlu
2005-08-11 0:28 ` Andi Kleen
2005-08-11 0:43 ` yhlu
2005-08-11 0:51 ` Andi Kleen
2005-08-12 6:59 ` yhlu
2005-08-12 7:04 ` yhlu
2005-08-12 13:07 ` Andi Kleen
2005-08-12 16:18 ` yhlu [this message]
2005-08-12 16:41 ` Andi Kleen
2005-08-12 17:36 ` yhlu
2005-08-10 23:49 ` Mike Waychison
2005-08-10 23:31 ` Peter Buckingham
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=86802c4405081209187e51878@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=peter@pantasys.com \
/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.