lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1213899242.3223.110.camel@lappy.programming.kicks-ass.net>
Date:	Thu, 19 Jun 2008 20:14:02 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Avi Kivity <avi@...ranet.com>,
	linux-kernel@...r.kernel.org,
	Dmitry Adamushko <dmitry.adamushko@...il.com>
Subject: Re: [BUG] CFS vs cpu hotplug

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?

Not that that is any excuse for crashing.. but it does simplify the
scheduler somewhat.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ