> On 1 Aug 2020, at 00:03, Stefano Stabellini wrote:
>
> On Fri, 31 Jul 2020, Bertrand Marquis wrote:
>> Sorry missed some points in my previous answer.
>>
>>> On 30 Jul 2020, at 22:50, Julien Grall wrote:
>>>
>>> Hi Bertrand,
>>>
>>> To avoid extra work on your side, I would recommend to
> On 13 Aug 2020, at 18:28, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 31/07/2020 14:16, Bertrand Marquis wrote:
>>> On 30 Jul 2020, at 22:50, Julien Grall wrote:
>>> On 30/07/2020 11:24, Bertrand Marquis wrote:
At the moment on Arm, a Linux guest running with KTPI enabled will
ca
> On 13 Aug 2020, at 18:35, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 31/07/2020 14:26, Bertrand Marquis wrote:
+{
+gprintk(XENLOG_WARNING, "Cannot map runstate pointer at
0x%"PRIvaddr
+": Invalid offset\n", vaddr);
>>>
>>> We usually enforc
Hi Bertrand,
On 31/07/2020 14:26, Bertrand Marquis wrote:
+{
+gprintk(XENLOG_WARNING, "Cannot map runstate pointer at 0x%"PRIvaddr
+": Invalid offset\n", vaddr);
We usually enforce 80 character per lines except for format string. So it is
easier to grep them in the
Hi Bertrand,
On 31/07/2020 14:16, Bertrand Marquis wrote:
On 30 Jul 2020, at 22:50, Julien Grall wrote:
On 30/07/2020 11:24, Bertrand Marquis wrote:
At the moment on Arm, a Linux guest running with KTPI enabled will
cause the following error when a context switch happens in user mode:
(XEN)
On Fri, 31 Jul 2020, Bertrand Marquis wrote:
> Sorry missed some points in my previous answer.
>
> > On 30 Jul 2020, at 22:50, Julien Grall wrote:
> >
> > Hi Bertrand,
> >
> > To avoid extra work on your side, I would recommend to wait a bit before
> > sending a new version. It would be good t
Hi Bertrand,
On 31/07/2020 14:09, Bertrand Marquis wrote:
On 31 Jul 2020, at 14:19, Jan Beulich wrote:
On 30.07.2020 22:50, Julien Grall wrote:
On 30/07/2020 11:24, Bertrand Marquis wrote:
At the moment on Arm, a Linux guest running with KTPI enabled will
cause the following error when a
Sorry missed some points in my previous answer.
> On 30 Jul 2020, at 22:50, Julien Grall wrote:
>
> Hi Bertrand,
>
> To avoid extra work on your side, I would recommend to wait a bit before
> sending a new version. It would be good to at least settle the conversation
> in v2 regarding the app
> On 31 Jul 2020, at 03:18, Stefano Stabellini wrote:
>
> On Thu, 30 Jul 2020, Julien Grall wrote:
>> Hi Bertrand,
>>
>> To avoid extra work on your side, I would recommend to wait a bit before
>> sending a new version. It would be good to at least settle the conversation
>> in
>> v2 regardi
> On 30 Jul 2020, at 22:50, Julien Grall wrote:
>
> Hi Bertrand,
>
> To avoid extra work on your side, I would recommend to wait a bit before
> sending a new version. It would be good to at least settle the conversation
> in v2 regarding the approach taken.
Thanks for the advice.
I thought
> On 31 Jul 2020, at 14:19, Jan Beulich wrote:
>
> On 30.07.2020 22:50, Julien Grall wrote:
>> On 30/07/2020 11:24, Bertrand Marquis wrote:
>>> At the moment on Arm, a Linux guest running with KTPI enabled will
>>> cause the following error when a context switch happens in user mode:
>>> (XEN)
On 30.07.2020 22:50, Julien Grall wrote:
> On 30/07/2020 11:24, Bertrand Marquis wrote:
>> At the moment on Arm, a Linux guest running with KTPI enabled will
>> cause the following error when a context switch happens in user mode:
>> (XEN) p2m.c:1890: d1v0: Failed to walk page-table va 0xff837e
On Thu, 30 Jul 2020, Julien Grall wrote:
> Hi Bertrand,
>
> To avoid extra work on your side, I would recommend to wait a bit before
> sending a new version. It would be good to at least settle the conversation in
> v2 regarding the approach taken.
>
> On 30/07/2020 11:24, Bertrand Marquis wrote:
Hi Bertrand,
To avoid extra work on your side, I would recommend to wait a bit before
sending a new version. It would be good to at least settle the
conversation in v2 regarding the approach taken.
On 30/07/2020 11:24, Bertrand Marquis wrote:
At the moment on Arm, a Linux guest running with
At the moment on Arm, a Linux guest running with KTPI enabled will
cause the following error when a context switch happens in user mode:
(XEN) p2m.c:1890: d1v0: Failed to walk page-table va 0xff837ebe0cd0
The error is caused by the virtual address for the runstate area
registered by the guest
15 matches
Mail list logo
