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: <20080504050919.GC21789@linux.vnet.ibm.com>
Date:	Sun, 4 May 2008 10:39:19 +0530
From:	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
To:	David Miller <davem@...emloft.net>
Cc:	mingo@...e.hu, a.p.zijlstra@...llo.nl, tglx@...utronix.de,
	guichaz@...il.com, andi@...stfloor.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	efault@....de
Subject: Re: [RFC][PATCH] sched_clock_cpu()

On Sat, May 03, 2008 at 09:26:07PM -0700, David Miller wrote:
> From: Ingo Molnar <mingo@...e.hu>
> Date: Sat, 3 May 2008 19:01:30 +0200
> 
> > 
> > * Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> > 
> > > it _DOESN'T_ boot ;-/ and I seem to have caught a flu that makes my
> > > whole body hurt like hell, so I'm not getting anything done.
> > 
> > i think i see where your boot problem comes from:
> > 
> > > +struct sched_clock_data {
> > > +	spinlock_t lock;
> > 
> > that wont work very well when sched_clock() is called from within 
> > CONFIG_LOCK_STAT instrumentation. Does the patch below solve the boot 
> > problems for you?
> 
> Also, no platform can set HAVE_STABLE_CLOCK until we instantiate it in
> a Kconfig somewhere.  I've choosen to do it in kernel/Kconfig.hz and
> here are the sparc/sparc64 bits as well, I've booted this up with
> Peter's patch on my 64-cpu niagara2 box and done some basic testing.
> 
> It would be nice if a powerpc person could test the trivial
> powerpc Kconfig patch.
> 

On it. Let me get hold of a powerpc box here, and try it out.
-- 
regards,
Dhaval
--
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