> On 24 Sep 2020, at 18:25, Bertrand Marquis wrote:
>
> Hi,
>
> Sorry for the delay.
>
>> On 11 Sep 2020, at 01:33, Stefano Stabellini wrote:
>>
>> On Thu, 10 Sep 2020, Jan Beulich wrote:
>> - should we backport the support for this hypercall in older kernel
>> releases ?
>
Hi,
Sorry for the delay.
> On 11 Sep 2020, at 01:33, Stefano Stabellini wrote:
>
> On Thu, 10 Sep 2020, Jan Beulich wrote:
> - should we backport the support for this hypercall in older kernel
> releases ?
It's a bug fix to KPTI, and as such ought to be at least eligible for
On Thu, 10 Sep 2020, Jan Beulich wrote:
> >>> - should we backport the support for this hypercall in older kernel
> >>> releases ?
> >>
> >> It's a bug fix to KPTI, and as such ought to be at least eligible for
> >> considering doing so?
> >
> > That will mean also backport in Linux. What should
On 10.09.2020 16:00, Bertrand Marquis wrote:
>> On 10 Sep 2020, at 14:56, Jan Beulich wrote:
>> On 10.09.2020 15:46, Bertrand Marquis wrote:
>>> Some open questions:
>>> - should we allow to register an area using both hypercalls or should it be
>>> exclusive ?
>>
>> I thought it was already
> On 10 Sep 2020, at 15:00, Bertrand Marquis wrote:
>
>
>
>> On 10 Sep 2020, at 14:56, Jan Beulich wrote:
>>
>> On 10.09.2020 15:46, Bertrand Marquis wrote:
>>> Some open questions:
>>> - should we allow to register an area using both hypercalls or should it be
>>> exclusive ?
>>
>> I
> On 10 Sep 2020, at 14:56, Jan Beulich wrote:
>
> On 10.09.2020 15:46, Bertrand Marquis wrote:
>> Some open questions:
>> - should we allow to register an area using both hypercalls or should it be
>> exclusive ?
>
> I thought it was already clarified that to a certain degree both need
> to
On 10.09.2020 15:46, Bertrand Marquis wrote:
> Some open questions:
> - should we allow to register an area using both hypercalls or should it be
> exclusive ?
I thought it was already clarified that to a certain degree both need
to remain usable at least in sequence, to allow transitioning
Hi,
Following my patch[1] to map the guest runstate in Xen during the hypercall
directly
instead of doing the conversion from virtual to physical when updating the
runstate
content during a context switch a global discussion started[2][3].
To resume the discussion the problem is the following:
