From: Mel Gorman <mel@csn.ul.ie>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..
Date: Wed, 03 Oct 2007 01:37:35 +0100 [thread overview]
Message-ID: <1191371855.2708.26.camel@localhost> (raw)
In-Reply-To: <4702C1AD.3090701@tmr.com>
On Tue, 2007-10-02 at 18:09 -0400, Bill Davidsen wrote:
> Mel Gorman wrote:
> > On (02/10/07 14:15), Ingo Molnar didst pronounce:
> >> * Mel Gorman <mel@csn.ul.ie> wrote:
> >>
> >>> Dirt. Booting with "profile=sleep,2" is broken in 2.6.23-rc9 and
> >>> 2.6.23-rc8 but working in 2.6.22. I was checking it out as part of a
> >>> discussion in another thread and noticed it broken in -mm as well
> >>> (2.6.23-rc8-mm2). Bisect is in progress but suggestions as to the
> >>> prime candidates are welcome or preferably, pointing out that I'm an
> >>> idiot because I missed twiddling some config change.
> >> Mel, does the patch below fix this bug for you? (Note: you will need to
> >> enable CONFIG_SCHEDSTATS=y too.)
> >>
> >
> > Nice one Ingo - got it first try. The problem commit was
> > dd41f596cda0d7d6e4a8b139ffdfabcefdd46528 and it's clear that the code removed
> > in this commit is put back by this latest patch. When applied, profile=sleep
> > works as long as CONFIG_SCHEDSTAT is set.
> >
> And if it isn't set? I can easily see building a new kernel with stats
> off and forgetting to change the boot options.
>
If CONFIG_SCHEDSTAT is off and profile=sleep is set, you see with Ingo's
patch and readprofile;
0 *unknown*
0 total 0.0000
That is a tad confusing hence my follow-up patch which would say
"/proc/profile" doesn't exist when readprofile is used and the warning
in dmesg.
--
Mel Gorman
next prev parent reply other threads:[~2007-10-02 23:37 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0710012029400.3579@woody.linux-foundation.org >
2007-10-02 3:41 ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Linus Torvalds
2007-10-02 9:17 ` Thomas Gleixner
2007-10-02 9:21 ` Andi Kleen
2007-10-02 10:37 ` Jeff Garzik
2007-10-02 10:48 ` Andi Kleen
2007-10-02 11:05 ` Thomas Gleixner
2007-10-02 14:07 ` Ingo Molnar
2007-10-02 14:23 ` Andi Kleen
2007-10-02 14:31 ` Ingo Molnar
2007-10-02 14:54 ` Andi Kleen
2007-10-02 14:58 ` Sam Ravnborg
2007-10-02 15:24 ` Andi Kleen
2007-10-02 15:27 ` Ingo Molnar
2007-10-02 15:30 ` Thomas Gleixner
2007-10-02 15:40 ` Sam Ravnborg
2007-10-02 12:04 ` Jiri Kosina
2007-10-02 20:12 ` Rafael J. Wysocki
2007-10-02 20:11 ` Andrew Morton
2007-10-02 20:31 ` Rafael J. Wysocki
2007-10-02 20:32 ` Roland Dreier
2007-10-03 3:53 ` Eric St-Laurent
2007-10-02 12:07 ` Mel Gorman
2007-10-02 12:15 ` Ingo Molnar
2007-10-02 17:21 ` Mel Gorman
2007-10-02 22:09 ` Bill Davidsen
2007-10-03 0:37 ` Mel Gorman [this message]
2007-10-03 8:21 ` Ingo Molnar
2007-10-03 12:51 ` Mel Gorman
2007-10-22 15:56 ` Ingo Molnar
2007-10-03 8:19 ` Ingo Molnar
2007-10-02 14:44 ` John Stoffel
2007-10-02 15:03 ` Ingo Molnar
2007-10-02 15:45 ` John Stoffel
2007-10-02 22:13 ` Bill Davidsen
2007-10-02 22:44 ` Willy Tarreau
2007-10-02 22:51 ` Alistair John Strachan
2007-10-02 23:00 ` Glauber de Oliveira Costa
2007-10-05 5:41 ` Ingo Molnar
2007-10-05 5:38 ` Ingo Molnar
2007-10-05 6:11 ` Sam Ravnborg
2007-10-05 8:32 ` Thomas Gleixner
2007-10-07 23:44 ` Alistair John Strachan
2007-10-02 23:07 ` Diego Calleja
2007-10-02 23:32 ` Linus Torvalds
2007-10-03 15:28 ` Diego Calleja
2007-10-03 8:46 ` [bug] crash when reading /proc/mounts (was: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..) Ingo Molnar
2007-10-03 8:50 ` Ingo Molnar
2007-10-03 9:12 ` Ingo Molnar
2007-10-03 9:23 ` Ingo Molnar
2007-10-03 13:34 ` Al Viro
2007-10-03 14:08 ` Ingo Molnar
2007-10-03 14:26 ` Al Viro
2007-10-03 15:12 ` Arjan van de Ven
2007-10-03 15:11 ` Linus Torvalds
2007-10-03 15:40 ` Ingo Molnar
2007-10-03 16:07 ` Linus Torvalds
2007-10-03 15:47 ` Linus Torvalds
2007-10-03 15:49 ` Ingo Molnar
2007-10-03 16:07 ` Ingo Molnar
2007-10-03 15:51 ` Alan Cox
2007-10-03 16:09 ` Linus Torvalds
2007-10-03 16:25 ` Jan Engelhardt
2007-10-03 17:07 ` Linus Torvalds
2007-10-04 14:12 ` Adrian Bunk
2007-10-04 15:08 ` Alexey Dobriyan
2007-10-03 14:21 ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Timo Jantunen
2007-10-03 19:07 ` Jeff Garzik
2007-10-03 19:25 ` Linus Torvalds
2007-10-04 11:55 ` [patch] net, 9p: build fix with !CONFIG_SYSCTL Ingo Molnar
2007-10-04 17:05 ` [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES Mathieu Chouquet-Stringer
2007-10-04 17:17 ` Peter Zijlstra
2007-10-04 20:47 ` Mathieu Chouquet-Stringer
2007-10-04 21:58 ` Mathieu Chouquet-Stringer
2007-10-04 17:27 ` Linus Torvalds
2007-10-04 20:44 ` Mathieu Chouquet-Stringer
2007-10-04 21:21 ` Linus Torvalds
2007-10-04 22:27 ` Paul Mackerras
2007-10-05 0:12 ` Linus Torvalds
2007-10-05 3:22 ` Mathieu Chouquet-Stringer
2007-10-05 7:43 ` Peter Zijlstra
2007-10-04 21:50 ` Chuck Ebbert
2007-10-04 21:54 ` Mathieu Chouquet-Stringer
2007-10-06 8:29 ` Hans-Peter Jansen
2007-10-06 11:29 ` Hans-Peter Jansen
2007-10-06 17:36 ` Bill Davidsen
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=1191371855.2708.26.camel@localhost \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox