linux-kernel - Re: Not able to use HIGH_RES

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: <CAB4K4y6u_59XLCBL2k5TrpAGv9C161wyqE_0_CEGbmgWeEwCyw@mail.gmail.com>
Date:	Fri, 23 Mar 2012 11:22:46 +0530
From:	Ajeet Yadav <ajeet.yadav.77@...il.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>,
	John Stultz <john.stultz@...aro.org>
Cc:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
	stable@...r.kernel.org
Subject: Re: Not able to use HIGH_RES_TIMERS on ARM

CCing to stable@...r.kernel.org
On Fri, Mar 23, 2012 at 8:58 AM, John Stultz <john.stultz@...aro.org> wrote:
> On 03/22/2012 03:25 AM, Ajeet Yadav wrote:
>>
>> If I set  ARCH_USES_GETTIMEOFFSET=n to use this feature, my target
>> fail to boot. (reason I well understand from our past discussions)
>
> And this point I'm not sure I'm following. Why exactly does disabling
> ARCH_USES_GETTIMEOFFSET cause boot failures? Could you expand on the details
> here?
We did some dissection to narrow down the patch, our latest kernel is
stable 3.0.X , however we backported patch " ARM: 7321/1: cache-v7:
Disable preemption when reading CCSIDR" from 3.0.25 stable tree, this
patch causes kernel hang during boot (IRQSOFF_TRACER=y and
PREEMPT_TRACER=y) with 100% probability , if we remove this patch or
disable the given CONFIG's then boot is success.
>
> You should just end up using the jiffies clocksource, which would give you
> low-res HZ granular timestamps, but shouldn't get in the way of booting.
>
> thanks
> -john
>
--
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/