Hi Luca,
On 15/05/2024 11:05, Luca Fancellu wrote:
On 14 May 2024, at 22:06, Julien Grall wrote:
Hi,
On 14/05/2024 08:53, Luca Fancellu wrote:
Hi Julien,
Thanks for having a look on the patch,
On 13 May 2024, at 22:54, Julien Grall wrote:
Hi Luca,
On 25/04/2024 14:11, Luca Fancellu
> On 14 May 2024, at 22:06, Julien Grall wrote:
>
> Hi,
>
> On 14/05/2024 08:53, Luca Fancellu wrote:
>> Hi Julien,
>> Thanks for having a look on the patch,
>>> On 13 May 2024, at 22:54, Julien Grall wrote:
>>>
>>> Hi Luca,
>>>
>>> On 25/04/2024 14:11, Luca Fancellu wrote:
Currently
Hi,
On 14/05/2024 08:53, Luca Fancellu wrote:
Hi Julien,
Thanks for having a look on the patch,
On 13 May 2024, at 22:54, Julien Grall wrote:
Hi Luca,
On 25/04/2024 14:11, Luca Fancellu wrote:
Currently the code is listing device tree reserve map regions
as reserved memory for Xen, but
Hi Julien,
Thanks for having a look on the patch,
> On 13 May 2024, at 22:54, Julien Grall wrote:
>
> Hi Luca,
>
> On 25/04/2024 14:11, Luca Fancellu wrote:
>> Currently the code is listing device tree reserve map regions
>> as reserved memory for Xen, but they are not added into
>>
Hi Luca,
On 25/04/2024 14:11, Luca Fancellu wrote:
Currently the code is listing device tree reserve map regions
as reserved memory for Xen, but they are not added into
bootinfo.reserved_mem and they are fetched in multiple places
using the same code sequence, causing duplication. Fix this
by
Currently the code is listing device tree reserve map regions
as reserved memory for Xen, but they are not added into
bootinfo.reserved_mem and they are fetched in multiple places
using the same code sequence, causing duplication. Fix this
by adding them to the bootinfo.reserved_mem at early
