On 30.08.21 16:16, Jan Beulich wrote:
Hi Jan
On 29.08.2021 22:28, Oleksandr wrote:
On 16.08.21 10:33, Jan Beulich wrote:
On 14.08.2021 01:28, Oleksandr Tyshchenko wrote:
--- a/xen/include/public/arch-arm.h
+++ b/xen/include/public/arch-arm.h
@@ -332,6 +332,11 @@ struct xen_arch_domainconfi
On 29.08.2021 22:28, Oleksandr wrote:
> On 16.08.21 10:33, Jan Beulich wrote:
>> On 14.08.2021 01:28, Oleksandr Tyshchenko wrote:
>>> --- a/xen/include/public/arch-arm.h
>>> +++ b/xen/include/public/arch-arm.h
>>> @@ -332,6 +332,11 @@ struct xen_arch_domainconfig {
>>>*/
>>> uint32_t
On 16.08.21 10:33, Jan Beulich wrote:
Hi Jan
Sorry for the late response.
On 14.08.2021 01:28, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
We need to pass info about maximum supported address space size
to the toolstack on Arm in order to properly calculate the base
and size of
On 14.08.2021 01:28, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko
>
> We need to pass info about maximum supported address space size
> to the toolstack on Arm in order to properly calculate the base
> and size of the safe range for the guest. Use p2m_ipa_bits variable
> which purpose
From: Oleksandr Tyshchenko
We need to pass info about maximum supported address space size
to the toolstack on Arm in order to properly calculate the base
and size of the safe range for the guest. Use p2m_ipa_bits variable
which purpose is to hold the bit size of IPAs in P2M tables.
As we change
