[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0117e263-2856-b2fd-1e61-59b21e5da2e5@linux.ibm.com>
Date: Tue, 25 Oct 2022 15:17:36 +0200
From: Pierre Morel <pmorel@...ux.ibm.com>
To: David Hildenbrand <david@...hat.com>, kvm@...r.kernel.org
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
borntraeger@...ibm.com, frankja@...ux.ibm.com, cohuck@...hat.com,
thuth@...hat.com, imbrenda@...ux.ibm.com, hca@...ux.ibm.com,
gor@...ux.ibm.com, svens@...ux.ibm.com
Subject: Re: [PATCH v2 1/1] KVM: s390: vsie: clarifications on setting the
APCB
On 10/25/22 11:30, David Hildenbrand wrote:
> On 25.10.22 11:13, Pierre Morel wrote:
>> The APCB is part of the CRYCB.
>> The calculation of the APCB origin can be done by adding
>> the APCB offset to the CRYCB origin.
>>
>> Current code makes confusing transformations, converting
>> the CRYCB origin to a pointer to calculate the APCB origin.
>>
>
>
> While at it, can we rename "crycb_o" to "crycb_gpa" and "apcb_o" to
> "apcb_gpa".
>
> These are not pointers but guest physical addresses.
>
I can do that.
the _o came from the name in the documentation "origin"
but gpa is more obvious.
--
Pierre Morel
IBM Lab Boeblingen
Powered by blists - more mailing lists