From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>
Cc: Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen/arm: remove check for generic timer support for arm64
Date: Mon, 02 Jun 2014 15:13:27 +0100 [thread overview]
Message-ID: <538C8687.2060502@linaro.org> (raw)
In-Reply-To: <1401718288.21534.25.camel@kazak.uk.xensource.com>
On 06/02/2014 03:11 PM, Ian Campbell wrote:
> On Mon, 2014-06-02 at 19:38 +0530, Vijay Kilari wrote:
>> On Mon, Jun 2, 2014 at 7:32 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>>> On Mon, 2014-06-02 at 19:29 +0530, Vijay Kilari wrote:
>>>> However generic timer is required for aarch64 mode.
>>>
>>> Do you have an ARM ARM reference for that? If true it would indeed
>>> simplify things, but I was unable to find a statement along those
>>> lines...
>>
>> Sorry, I too didn't not get any reference for this.
>> But in arm64 where Aarch32 is optional, why should one rely on Aarch32
>> feature register
>> if generic timer is anyway required for Aarch64
>
> We shouldn't, the bug is that we are checking the AArch32 feature
> register instead of the AArch64 one in this case (see the rest of this
> thread).
AArch64 doesn't have a similar feature bit in AA64PFR*.
--
Julien Grall
next prev parent reply other threads:[~2014-06-02 14:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 8:37 [PATCH] xen/arm: remove check for generic timer support for arm64 vijay.kilari
2014-06-02 11:06 ` Julien Grall
2014-06-02 11:09 ` Ian Campbell
2014-06-02 11:13 ` Julien Grall
2014-06-02 13:03 ` Ian Campbell
2014-06-02 13:23 ` Julien Grall
2014-06-02 13:30 ` Ian Campbell
2014-06-02 13:39 ` Julien Grall
2014-06-02 13:59 ` Vijay Kilari
2014-06-02 14:02 ` Ian Campbell
2014-06-02 14:08 ` Vijay Kilari
2014-06-02 14:11 ` Ian Campbell
2014-06-02 14:13 ` Julien Grall [this message]
2014-06-02 14:21 ` Ian Campbell
2014-06-02 14:10 ` Julien Grall
2014-06-02 14:12 ` Ian Campbell
2014-06-02 14:01 ` Ian Campbell
2014-06-02 14:48 ` Ian Campbell
2014-06-02 14:50 ` Julien Grall
2014-06-02 14:53 ` Ian Campbell
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=538C8687.2060502@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.