[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 17/18] xen/arm: Resume Dom0 after Xen resumes

To: Mirela Simonovic <mirela.simonovic@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx
From: Julien Grall <julien.grall@xxxxxxx>
Date: Thu, 15 Nov 2018 20:31:05 +0000
Cc: stefano.stabellini@xxxxxxxxxx, Stefano Stabellini <sstabellini@xxxxxxxxxx>, dm@xxxxxxxxxx, saeed.nowshadi@xxxxxxxxxx
Delivery-date: Thu, 15 Nov 2018 20:31:14 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi,

On 11/12/18 11:30 AM, Mirela Simonovic wrote:

The resume of Dom0 should always follow Xen's resume. This is
done by unblocking the first vCPU of Dom0.


Please explain why you always need to resume Dom0 afterwards.

Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 17/18] xen/arm: Resume Dom0 after Xen resumes
  - From: Mirela Simonovic

References:
- [Xen-devel] [PATCH 00/18] xen/arm64: Suspend to RAM support for Xen
  - From: Mirela Simonovic
- [Xen-devel] [PATCH 17/18] xen/arm: Resume Dom0 after Xen resumes
  - From: Mirela Simonovic

Prev by Date: Re: [Xen-devel] [PATCH 03/18] xen/arm: Save GIC and virtual timer context when the domain suspends
Next by Date: Re: [Xen-devel] [PATCH 05/18] xen/arm: Trigger Xen suspend when Dom0 completes suspend
Previous by thread: [Xen-devel] [PATCH 17/18] xen/arm: Resume Dom0 after Xen resumes
Next by thread: Re: [Xen-devel] [PATCH 17/18] xen/arm: Resume Dom0 after Xen resumes
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.