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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52276001.8070801@codeaurora.org>
Date:	Wed, 04 Sep 2013 09:29:53 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
CC:	Simon Horman <horms@...ge.net.au>,
	Magnus Damm <magnus.damm@...il.com>,
	linux-kernel@...r.kernel.org, linux@....linux.org.uk,
	arnd@...db.de, linux-sh@...r.kernel.org, rob.herring@...xeda.com,
	olof@...om.net, santosh.shilimkar@...com, grant.likely@...aro.org,
	tglx@...utronix.de
Subject: Re: [PATCH] clocksource: em_sti: Set cpu_possible_mask to fix SMP
 broadcast

On 09/04/13 01:44, Daniel Lezcano wrote:
>
>> On Wed, Sep 04, 2013 at 05:01:51PM +0900, Magnus Damm wrote:
>>> From: Magnus Damm <damm@...nsource.se>
>>>
>>> Update the STI driver by setting cpu_possible_mask to make EMEV2
>>> SMP work as expected together with the ARM broadcast timer.
>>>
>>> This breakage was introduced by:
>>>
>>> f7db706 ARM: 7674/1: smp: Avoid dummy clockevent being preferred over real hardware clock-event
>>>
>>> Without this fix SMP operation is broken on EMEV2 since no
>>> broadcast timer interrupts trigger on the secondary CPU cores.
>>>
>>> Signed-off-by: Magnus Damm <damm@...nsource.se>
>> Tested-by: Simon Horman <horms+renesas@...ge.net.au>
>>
>> I will let this sit for a few days to see if there is any further feedback.

Reviewed-by: Stephen Boyd <sboyd@...eaurora.org>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

--
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