public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Avi Kivity <avi@qumranet.com>,
	linux-kernel@vger.kernel.org,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: Re: [BUG] CFS vs cpu hotplug
Date: Thu, 19 Jun 2008 23:14:47 +0200	[thread overview]
Message-ID: <20080619211447.GA6180@osiris.ibm.com> (raw)
In-Reply-To: <1213899242.3223.110.camel@lappy.programming.kicks-ass.net>

On Thu, Jun 19, 2008 at 08:14:02PM +0200, Peter Zijlstra wrote:
> On Thu, 2008-06-19 at 20:05 +0200, Peter Zijlstra wrote:
> > On Thu, 2008-06-19 at 18:19 +0200, Heiko Carstens wrote:
> 
> > > The sched_entity that belongs to the cfs_rq:
> > > 
> > > >> px *(sched_entity *) 0x759300
> > > struct sched_entity {
> > >         load = struct load_weight {
> > >                 weight = 0x800
> > >                 inv_weight = 0x1ffc01
> > >         }
> > >         run_node = struct rb_node {
> > >                 rb_parent_color = 0x1
> > >                 rb_right = (nil)
> > >                 rb_left = (nil)
> > >         }
> > >         group_node = struct list_head {
> > >                 next = 0x75a3b8
> > >                 prev = 0x75a3b8
> > >         }
> > >         on_rq = 0x1
> > >         exec_start = 0x189685acb4aa46
> > >         sum_exec_runtime = 0x188a2b84c
> > >         vruntime = 0xd036bd29
> > >         prev_sum_exec_runtime = 0x1672e3f62
> > >         last_wakeup = 0x0
> > >         avg_overlap = 0x0
> > >         parent = (nil)
> > >         cfs_rq = 0x75a380
> > >         my_q = 0x759400
> > > }
> 
> Ooh, this thing is with CONFIG_GROUP_SCHED... does it still happen when
> you disable that?

Indeed, when CONFIG_GROUP_SCHED is disabled I cannot reproduce it anymore.

  reply	other threads:[~2008-06-19 21:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 16:19 [BUG] CFS vs cpu hotplug Heiko Carstens
2008-06-19 18:05 ` Peter Zijlstra
2008-06-19 18:14   ` Peter Zijlstra
2008-06-19 21:14     ` Heiko Carstens [this message]
2008-06-19 21:26       ` Peter Zijlstra
2008-06-19 21:17   ` Heiko Carstens
2008-06-19 21:32   ` Peter Zijlstra
2008-06-19 21:49     ` Heiko Carstens
2008-06-20  8:51       ` Peter Zijlstra
2008-06-20 22:19         ` Heiko Carstens
2008-06-20 11:44   ` Dmitry Adamushko
2008-06-20 22:23     ` Heiko Carstens
2008-06-25 22:12 ` Dmitry Adamushko
2008-06-28 22:16   ` Dmitry Adamushko
2008-06-29  6:55     ` Ingo Molnar
2008-06-30  9:07     ` Heiko Carstens
2008-06-30  9:17       ` Ingo Molnar
2008-07-01  9:22         ` Lai Jiangshan
2008-07-01  9:31           ` Ingo Molnar
2008-07-01 10:09             ` Lai Jiangshan
2008-07-02  7:13             ` Lai Jiangshan
2008-07-02  8:50               ` Dmitry Adamushko
2008-07-02  9:23                 ` Lai Jiangshan
2008-07-07 10:26                   ` Miao Xie
2008-07-07 11:31                     ` Dmitry Adamushko
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 22:32 Dmitry Adamushko
2008-07-10  7:30 ` Heiko Carstens
2008-07-10  7:39   ` Ingo Molnar

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=20080619211447.GA6180@osiris.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=avi@qumranet.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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