From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state
Date: Wed, 13 Aug 2008 12:29:09 -0700 [thread overview]
Message-ID: <20080813192909.GA31685@us.ibm.com> (raw)
In-Reply-To: <20080813162553.GA5720@elte.hu>
On 13.08.2008 [18:25:53 +0200], Ingo Molnar wrote:
>
> * Luck, Tony <tony.luck@intel.com> wrote:
>
> > > I'm happy to test any better patches.
> >
> > Linus just took a patch from my tree that should solve this
> > once and for all for ia64.
> >
> > commit 10617bbe84628eb18ab5f723d3ba35005adde143
> > Author: Tony Luck <tony.luck@intel.com>
> > Date: Tue Aug 12 10:34:20 2008 -0700
> >
> > [IA64] Ensure cpu0 can access per-cpu variables in early boot code
> >
> >
> > When you get a chance please test with your config against this
> > tree just to confirm that this is fixed.
>
> there's also Peter's other patch upstream since yesterday (and included
> in -rc3) which should solve the same problem:
>
> | commit c1955a3d4762e7a9bf84035eb3c4886a900f0d15
> | Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> | Date: Mon Aug 11 08:59:03 2008 +0200
> |
> | sched_clock: delay using sched_clock()
> |
> | Some arch's can't handle sched_clock() being called too early - delay
> | this until sched_clock_init() has been called.
>
> so i'd be mighty surprised if this dual firepower of commits didnt at
> least weaken this bug somewhat! ;-)
Well Peter's patch was tested-by me, so I know it fixes the problem on
the box I have access to, I'm verifying that -rc3 is ok.
Tony, would you like me to test your patch in isolation (reverting
c1955a3d4762e7a9bf84035eb3c4886a900f0d15) to see if it also fixes it?
Thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
next prev parent reply other threads:[~2008-08-13 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 19:46 [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state Nishanth Aravamudan
2008-08-04 20:37 ` Luck, Tony
2008-08-04 22:00 ` Luck, Tony
2008-08-04 22:02 ` David Miller
2008-08-04 22:10 ` Luck, Tony
2008-08-04 22:14 ` David Miller
2008-08-04 22:22 ` Luck, Tony
2008-08-04 22:41 ` Luck, Tony
2008-08-04 22:45 ` Nishanth Aravamudan
2008-08-04 22:53 ` Luck, Tony
2008-08-04 23:30 ` Nishanth Aravamudan
2008-08-05 8:56 ` Peter Zijlstra
2008-08-05 14:59 ` Luck, Tony
2008-08-05 17:34 ` Nishanth Aravamudan
2008-08-13 0:37 ` Luck, Tony
2008-08-13 16:25 ` Ingo Molnar
2008-08-13 19:29 ` Nishanth Aravamudan [this message]
2008-08-13 20:11 ` Luck, Tony
2008-08-19 22:19 ` Nishanth Aravamudan
2008-08-19 22:34 ` Luck, Tony
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=20080813192909.GA31685@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox