From: Marc Zyngier <marc.zyngier@arm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: arm64: fix misleading comments in save/restore
Date: Thu, 04 Jun 2015 11:50:11 +0100 [thread overview]
Message-ID: <55702D63.1050402@arm.com> (raw)
In-Reply-To: <87bngvbvjv.fsf@linaro.org>
On 04/06/15 11:46, Alex Bennée wrote:
>
> Marc Zyngier <marc.zyngier@arm.com> writes:
>
>> On 04/06/15 11:20, Alex Bennée wrote:
>>>
>>> Marc Zyngier <marc.zyngier@arm.com> writes:
>>>
>>>> On 04/06/15 10:34, Christoffer Dall wrote:
>>>>> On Thu, May 28, 2015 at 10:43:06AM +0100, Alex Bennée wrote:
>>>>>> The elr_el2 and spsr_el2 registers in fact contain the processor state
>>>>>> before entry into the hypervisor code.
>>>>>
>>>>> be careful with your use of the hypervisor, in the KVM design the
>>>>> hypervisor is split across EL1 and EL2.
>>>
>>> "before entry into EL2."
>>>
>>>>>
>>>>>> In the case of guest state it
>>>>>> could be in either el0 or el1.
>>>>>
>>>>> true
>>>>>
>>>>>>
>>>>>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>>>>> ---
>>>>>> arch/arm64/kvm/hyp.S | 8 ++++----
>>>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>>>>
>>>>>> diff --git a/arch/arm64/kvm/hyp.S b/arch/arm64/kvm/hyp.S
>>>>>> index d755922..1940a4c 100644
>>>>>> --- a/arch/arm64/kvm/hyp.S
>>>>>> +++ b/arch/arm64/kvm/hyp.S
>>>>>> @@ -50,8 +50,8 @@
>>>>>> stp x29, lr, [x3, #80]
>>>>>>
>>>>>> mrs x19, sp_el0
>>>>>> - mrs x20, elr_el2 // EL1 PC
>>>>>> - mrs x21, spsr_el2 // EL1 pstate
>>>>>> + mrs x20, elr_el2 // PC before hyp entry
>>>>>> + mrs x21, spsr_el2 // pstate before hyp entry
>>>>>>
>>>>>> stp x19, x20, [x3, #96]
>>>>>> str x21, [x3, #112]
>>>>>> @@ -82,8 +82,8 @@
>>>>>> ldr x21, [x3, #16]
>>>>>>
>>>>>> msr sp_el0, x19
>>>>>> - msr elr_el2, x20 // EL1 PC
>>>>>> - msr spsr_el2, x21 // EL1 pstate
>>>>>> + msr elr_el2, x20 // PC to restore
>>>>>> + msr spsr_el2, x21 // pstate to restore
>>>>>
>>>>> I don't feel like 'to restore' is much more meaningful here.
>>>>>
>>>>> I would actually vote for removin the comments all together, since one
>>>>> should really understand the code as opposed to the comments when
>>>>> reading this kind of stuff.
>>>>>
>>>>> Meh, I'm not sure. Your patch is definitely better than doing nothing.
>>>>>
>>>>> Marc?
>>>>
>>>> While I definitely agree that people should pay more attention to the
>>>> code rather than blindly trusting comments, I still think there is some
>>>> value in disambiguating the exception entry/return, because this bit of
>>>> code assumes some intimate knowledge of the ARMv8 exception model.
>>>>
>>>> As for the comments themselves, I'd rather have some wording that
>>>> clearly indicate that we're dealing with guest information, i.e:
>>>>
>>>> mrs x20, elr_el2 // Guest PC
>>>> mrs x21, spsr_el2 // Guest pstate
>>>>
>>>> (and the same for the exception return). The "before hyp entry" and "to
>>>> restore" are not really useful (all the registers we are
>>>> saving/restoring fall into these categories). What I wanted to convey
>>>> here was that despite using an EL2 register, we are dealing with guest
>>>> registers.
>>>
>>> Which would be great it we were. However the code is used to
>>> save/restore the host context as well as the guest context hence my
>>> weasely words.
>>
>> Gahhh. You're right. I'm spending too much time on the VHE code these
>> days. Guess I'll stick to the weasel words then. Can you respin it with
>> Christoffer's comment addressed?
>
> Sure. Do you want it separated from the guest debug series or will you
> be happy to take it with it when ready?
I'll take it now, no need to wait on the whole debug series to fix this.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2015-06-04 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:43 [PATCH] KVM: arm64: fix misleading comments in save/restore Alex Bennée
2015-06-04 9:34 ` Christoffer Dall
2015-06-04 10:01 ` Marc Zyngier
2015-06-04 10:20 ` Alex Bennée
2015-06-04 10:34 ` Marc Zyngier
2015-06-04 10:46 ` Alex Bennée
2015-06-04 10:50 ` 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=55702D63.1050402@arm.com \
--to=marc.zyngier@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).