Hi Jan,
On 11/09/2017 02:45 PM, Jan Beulich wrote:
On 09.11.17 at 15:42, wrote:
Hi,
On 09/11/17 08:55, Jan Beulich wrote:
On 08.11.17 at 20:46, wrote:
Do it once at domain creation (hpet_init).
Sleep -> Resume cycles will end up crashing
On 09/11/17 at 01:55am, Jan Beulich wrote:
>Perhaps my prior reply was ambiguous: By "inlining" I meant literally
>inlining it
My apologies for the clumsiness, I can resend a v3 right away.
Thanks,
--
Eric Chanudet
___
Xen-devel mailing list
>>> On 09.11.17 at 15:42, wrote:
> Hi,
>
> On 09/11/17 08:55, Jan Beulich wrote:
> On 08.11.17 at 20:46, wrote:
>>> Do it once at domain creation (hpet_init).
>>>
>>> Sleep -> Resume cycles will end up crashing an HVM guest with hpet as
>>>
Hi,
On 09/11/17 08:55, Jan Beulich wrote:
On 08.11.17 at 20:46, wrote:
Do it once at domain creation (hpet_init).
Sleep -> Resume cycles will end up crashing an HVM guest with hpet as
the sequence during resume takes the path:
-> hvm_s3_suspend
-> hpet_reset
>>> On 08.11.17 at 20:46, wrote:
> Do it once at domain creation (hpet_init).
>
> Sleep -> Resume cycles will end up crashing an HVM guest with hpet as
> the sequence during resume takes the path:
> -> hvm_s3_suspend
> -> hpet_reset
> -> hpet_deinit
> ->
Do it once at domain creation (hpet_init).
Sleep -> Resume cycles will end up crashing an HVM guest with hpet as
the sequence during resume takes the path:
-> hvm_s3_suspend
-> hpet_reset
-> hpet_deinit
-> hpet_init
-> register_mmio_handler
-> hvm_next_io_handler