From: Andi Kleen <ak@suse.de>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2007-04-25-02-49.tar.gz uploaded
Date: Thu, 26 Apr 2007 00:07:12 +0200 [thread overview]
Message-ID: <200704260007.12843.ak@suse.de> (raw)
In-Reply-To: <6bffcb0e0704251440l6149b50creafd4845c131be09@mail.gmail.com>
On Wednesday 25 April 2007 23:40:51 Michal Piotrowski wrote:
> On 25/04/07, Andi Kleen <ak@suse.de> wrote:
> >
> > > Maybe because it's P4 HT?
> >
> > Shouldn't make a difference.
> >
> > Can you please: apply the latest patch from
> >
> > ftp://firstfloor.org/pub/ak/x86_64/quilt/patches/sched-clock-share
> >
> > to a 2.6.21-rc7 kernel and then send me a full boot log?
>
> Now everything looks OK
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-04-25-02-49/git-dmesg
Does it also work when you revert the sched-clock-share patch in Andrew's broken-out
directory from mm and then apply my patch? (just to check there is not a bad interaction
with other mm changes)
Thanks,
-Andi
next prev parent reply other threads:[~2007-04-25 22:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 9:52 mm snapshot broken-out-2007-04-25-02-49.tar.gz uploaded akpm
2007-04-25 17:20 ` William Heimbigner
2007-04-25 20:25 ` Andrew Morton
2007-04-25 20:24 ` Michal Piotrowski
2007-04-25 20:42 ` Jeremy Fitzhardinge
2007-04-25 20:48 ` Andi Kleen
2007-04-25 20:55 ` Michal Piotrowski
2007-04-25 20:57 ` Andi Kleen
2007-04-25 21:40 ` Michal Piotrowski
2007-04-25 22:07 ` Andi Kleen [this message]
2007-04-25 23:02 ` Michal Piotrowski
2007-04-29 13:36 ` Michal Piotrowski
2007-04-29 13:55 ` Andi Kleen
2007-04-29 16:10 ` Jeremy Fitzhardinge
2007-04-26 21:21 ` Michal Piotrowski
2007-04-27 0:12 ` Greg KH
2007-04-27 17:38 ` Michal Piotrowski
2007-04-27 17:46 ` Greg KH
2007-04-27 17:48 ` Tejun Heo
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=200704260007.12843.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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