On 02/10/2020 11:31, Jan Beulich wrote:
> Hence there's no need to guard allocation / mapping by checks whether
> the same action has been done before. I assume this was a transient
> change which should have been undone before 509529e99148 ("x86 hvm: Xen
> interface and implementation for virtual S3") got committed.
>
> While touching this code, switch dprintk()-s to use %pv.Logging ENOMEM, especially without actually saying ENOMEM, is quite pointless. > Signed-off-by: Jan Beulich <[email protected]> Reviewed-by: Andrew Cooper <[email protected]>, preferably with the printk()s dropped.
