linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM/ARM64: arch-timer: fix arch_timer_probed logic
Date: Tue, 21 Oct 2014 12:58:29 +0200	[thread overview]
Message-ID: <54463C55.8010209@linaro.org> (raw)
In-Reply-To: <1413385580-23317-1-git-send-email-marc.zyngier@arm.com>

On 10/15/2014 05:06 PM, Marc Zyngier wrote:
> Commit c387f07e6205 (clocksource: arm_arch_timer: Discard unavailable
> timers correctly) changed the way the driver makes sure both the memory
> and system-register timers have been probed before finalizing the probing.
>
> There is a interesting flaw in this logic that leads to this final step
> never to be executed. Things seems to work pretty well until something
> actually needs the data that is produced during this final stage.
>
> For example, KVM explodes on the first run of a guest when executed on
> a platform that has both memory and sysreg nodes (Juno, for example).
>
> Just fix the damned logic, and enjoy booting VMs again.
>
> Tested on a Juno system.
>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Reported-by: Riku Voipio <riku.voipio@linaro.org>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---

Applied to my tree. Also for -next.

Thanks !

   -- Daniel

>   drivers/clocksource/arm_arch_timer.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 2133f9d..43005d4 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -660,11 +660,11 @@ static bool __init
>   arch_timer_probed(int type, const struct of_device_id *matches)
>   {
>   	struct device_node *dn;
> -	bool probed = false;
> +	bool probed = true;
>
>   	dn = of_find_matching_node(NULL, matches);
> -	if (dn && of_device_is_available(dn) && (arch_timers_present & type))
> -		probed = true;
> +	if (dn && of_device_is_available(dn) && !(arch_timers_present & type))
> +		probed = false;
>   	of_node_put(dn);
>
>   	return probed;
>


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  parent reply	other threads:[~2014-10-21 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 15:06 [PATCH] ARM/ARM64: arch-timer: fix arch_timer_probed logic Marc Zyngier
2014-10-15 15:28 ` Mark Rutland
2014-10-15 15:49   ` Sudeep Holla
2014-10-21 10:58 ` Daniel Lezcano [this message]
2014-10-21 11:07   ` Mark Rutland
2014-10-21 11:12     ` Daniel Lezcano
2014-10-27 10:33       ` Marc Zyngier
2014-10-27 20:30         ` Thomas Gleixner
2014-10-27 21:52           ` Daniel Lezcano

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=54463C55.8010209@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).