From: Marc Zyngier <maz@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: virt: Relax arch timer version check during early boot
Date: Mon, 20 Jan 2020 12:56:34 +0100 [thread overview]
Message-ID: <55fbdb33fc3e107385c12def941aa934@kernel.org> (raw)
In-Reply-To: <38a43fed-1c7a-69ea-3662-e17f13ca74d6@arm.com>
On 2020-01-20 12:34, Vladimir Murzin wrote:
> Hi Marc,
>
> On 1/20/20 11:14 AM, Marc Zyngier wrote:
>> Hi Vladimir,
>>
>> On 2020-01-20 11:46, Vladimir Murzin wrote:
>>> + Marc
>>> + kvmarm@lists.cs.columbia.edu
>>>
>>> On 1/15/20 2:16 PM, Vladimir Murzin wrote:
>>>> Updates to the Generic Timer architecture allow ID_PFR1.GenTimer to
>>>> have values other than 0 or 1. At the moment, Linux is quite strict
>>>> in
>>>> the way it handles this field at early boot and will not configure
>>>> arch timer if it doesn't find the value 1.
>>>>
>>>> Since here use ubfx for arch timer version extraction (hyb-stub
>>>> build
>>>> with -march=armv7-a, so it is safe)
>>>>
>>>> To help backports (even though the code was correct at the time of
>>>> writing)
>>>> Fixes: 8ec58be9f3ff ("ARM: virt: arch_timers: enable access to
>>>> physical timers")
>>>> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
>>
>> I'm not opposed to such a change, but it'd be good to document what
>> other values
>> are expected here, as the current (Rev E_a) ARM ARM only mentions
>> values 0 and 1.
>
> That true, ARM ARM doesn't mention it yet. OTOH, should we really care
> about exact values as soon it stays compatible?
That's for you to say, really. But given that you hint at some changes,
it'd be good to have at least a short sentence explaining that, for
example,
"upcoming revisions of the architecture will allow different
ID_PFR1.GenTimer
values while preserving backward compatibility".
Other than that, feel free to add my
Acked-by: Marc Zyngier <maz@kernel.org>
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2020-01-20 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1579097798-106243-1-git-send-email-vladimir.murzin@arm.com>
2020-01-20 10:46 ` [PATCH] ARM: virt: Relax arch timer version check during early boot Vladimir Murzin
2020-01-20 11:14 ` Marc Zyngier
2020-01-20 11:34 ` Vladimir Murzin
2020-01-20 11:56 ` Marc Zyngier [this message]
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=55fbdb33fc3e107385c12def941aa934@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vladimir.murzin@arm.com \
/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