On 09.12.2021 11:41, Juergen Gross wrote:
> On 09.12.21 11:36, Juergen Gross wrote:
>> On 09.12.21 11:26, Jan Beulich wrote:
>>> do_memory_op() supplies return value and has errno set the usual way.
>>> Don't overwrite errno with 1 (aka EPERM on at least Linux).
>>>
>>> Signed-off-by: Jan Beulich
On 09.12.21 11:36, Juergen Gross wrote:
On 09.12.21 11:26, Jan Beulich wrote:
do_memory_op() supplies return value and has errno set the usual way.
Don't overwrite errno with 1 (aka EPERM on at least Linux).
Signed-off-by: Jan Beulich
---
An alternative would be to let go of the DPRINTK() and
On 09.12.21 11:26, Jan Beulich wrote:
do_memory_op() supplies return value and has errno set the usual way.
Don't overwrite errno with 1 (aka EPERM on at least Linux).
Signed-off-by: Jan Beulich
---
An alternative would be to let go of the DPRINTK() and leave errno and
err alone altogether.
do_memory_op() supplies return value and has errno set the usual way.
Don't overwrite errno with 1 (aka EPERM on at least Linux).
Signed-off-by: Jan Beulich
---
An alternative would be to let go of the DPRINTK() and leave errno and
err alone altogether. While the hypervisor side of the hypercall