On 06/29/21 13:41, Jan Beulich via groups.io wrote:
> On 29.06.2021 13:29, Laszlo Ersek wrote:
>> On 06/29/21 12:35, Andrew Cooper wrote:
>>> On 29/06/2021 11:07, Jan Beulich wrote:
On 29.06.2021 11:20, Laszlo Ersek wrote:
> On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
>> Fro
On 29.06.2021 13:29, Laszlo Ersek wrote:
> On 06/29/21 12:35, Andrew Cooper wrote:
>> On 29/06/2021 11:07, Jan Beulich wrote:
>>> On 29.06.2021 11:20, Laszlo Ersek wrote:
On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
> From: Anthony PERARD
>
> Unfortunately, Xen isn't rea
On 29.06.2021 11:20, Laszlo Ersek wrote:
> On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
>> From: Anthony PERARD
>>
>> Unfortunately, Xen isn't ready to deal with mapping at the top of the
>> physical address space, so we relocate the mapping after the LAPIC
>> location.
>>
>> See this th
On 29/06/2021 11:07, Jan Beulich wrote:
> On 29.06.2021 11:20, Laszlo Ersek wrote:
>> On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
>>> From: Anthony PERARD
>>>
>>> Unfortunately, Xen isn't ready to deal with mapping at the top of the
>>> physical address space, so we relocate the mapping
On 06/29/21 12:35, Andrew Cooper wrote:
> On 29/06/2021 11:07, Jan Beulich wrote:
>> On 29.06.2021 11:20, Laszlo Ersek wrote:
>>> On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
From: Anthony PERARD
Unfortunately, Xen isn't ready to deal with mapping at the top of the
ph
On 06/28/21 15:23, Anthony PERARD via groups.io wrote:
> From: Anthony PERARD
>
> Unfortunately, Xen isn't ready to deal with mapping at the top of the
> physical address space, so we relocate the mapping after the LAPIC
> location.
>
> See this thread about the issue with the mapping:
> -
> ht
From: Anthony PERARD
Unfortunately, Xen isn't ready to deal with mapping at the top of the
physical address space, so we relocate the mapping after the LAPIC
location.
See this thread about the issue with the mapping:
-
https://lore.kernel.org/xen-devel/f8c4151a-6dac-d87c-ef46-eb35ada07...@suse