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

[Julien Grall <julien.grall@xxxxxxx>]

On 16/11/2018 11:29, Mirela Simonovic wrote:
> On Fri, Nov 16, 2018 at 11:33 AM Mirela Simonovic
> <mirela.simonovic@xxxxxxxxxx> wrote:
> > Hi Julien,
> >
> > On Thu, Nov 15, 2018 at 9:31 PM Julien Grall <julien.grall@xxxxxxx> wrote:
> > > 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.
> > We don't need to, but that is what is promised in the design spec.
You surely had some rationale when writing the promise in the design document, 
right?
So what is the reason behind it? I don't want to resume a domain if that's not 
necessary.
> >
> To be more specific - a domU that doesn't depend on dom0 can resume
> and work happily without dom0 being resumed, i.e. just Xen and domU
> resume. So patch "[PATCH 17/18] xen/arm: Resume Dom0 after Xen
> resumes" is not a must (when there are no PV drivers involved).
PV backends don't necessarily reside in the hardware domain. So how is this 
going to work for the other case?
Cheers,

--
Julien Grall

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