From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested
Date: Thu, 11 Sep 2014 10:57:25 +0100 [thread overview]
Message-ID: <20140911095725.GC5045@arm.com> (raw)
In-Reply-To: <CAD=FV=W_d=S-N-hguLsH+pf3kT1XqQNMMqGZ4o2wnpWZB9T70g@mail.gmail.com>
On Wed, Sep 10, 2014 at 08:50:16PM +0100, Doug Anderson wrote:
> On Wed, Sep 10, 2014 at 11:46 AM, Will Deacon <will.deacon@arm.com> wrote:
> > If `where we're at' is trying to boot an ARMv7 product, then you can boot in
> > secure svc and lose virtualisation support. Looking forward to ARMv8, this
> > isn't going to work, so I'd encourage you to start thinking about getting
> > a working bootloader as a requirement.
>
> Yup, definitely on the same page now. With everyone working on this
> I'd imagine that there will be some nice standards worked out by the
> time real ARMv8 is ready to ship?
>
> ...so would you say that you're in support of landing the patch to
> allow physical counters? I know Olof has Acked the patch above, but
> it's nice if there's general agreement that it's OK.
I'm in favour of fixing the regression, yes. What I didn't understand from
the patch is where arch_timer_use_virtual is set to false for your machine,
as we need to be careful not to regress arm64 (the vdso uses the virtual
counter there).
Will
next prev parent reply other threads:[~2014-09-11 9:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:03 [PATCH] clocksource: arch_timer: Fix code to use physical timers when requested Sonny Rao
2014-08-27 21:19 ` Olof Johansson
2014-08-27 21:27 ` Sonny Rao
2014-08-27 22:26 ` Stephen Boyd
2014-08-27 22:33 ` Olof Johansson
2014-08-28 0:56 ` Stephen Boyd
2014-08-28 2:58 ` Olof Johansson
2014-08-28 3:33 ` Doug Anderson
2014-08-28 9:35 ` Mark Rutland
2014-08-28 17:09 ` Christopher Covington
2014-08-28 18:04 ` Mark Rutland
2014-08-29 0:10 ` Sonny Rao
2014-08-29 10:04 ` Mark Rutland
2014-09-04 17:01 ` Sonny Rao
2014-09-04 17:47 ` Mark Rutland
2014-09-04 17:48 ` Lorenzo Pieralisi
2014-09-05 22:11 ` Doug Anderson
2014-09-08 13:54 ` Catalin Marinas
2014-09-10 17:17 ` Doug Anderson
2014-09-10 17:34 ` Will Deacon
2014-09-10 18:09 ` Doug Anderson
2014-09-10 18:46 ` Will Deacon
2014-09-10 19:50 ` Doug Anderson
2014-09-11 9:57 ` Will Deacon [this message]
2014-09-11 15:54 ` Doug Anderson
2014-09-10 14:58 ` Christopher Covington
2014-09-10 15:47 ` Catalin Marinas
2014-09-10 15:55 ` Mark Rutland
2014-09-10 16:39 ` Olof Johansson
2014-09-10 17:19 ` Doug Anderson
2014-08-28 9:23 ` Marc Zyngier
2014-09-10 17:27 ` Mark Rutland
2014-09-10 17:52 ` Doug Anderson
2014-09-10 18:05 ` Sonny Rao
2014-09-10 18:35 ` Doug Anderson
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=20140911095725.GC5045@arm.com \
--to=will.deacon@arm.com \
--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).