On Tue, 2018-10-16 at 18:44 +0100, Ian Jackson wrote:
> Dario Faggioli writes ("Re: [PATCH] libxl: extract and save affinity
> maps from hypervisor"):
> > If on the other hand, a domain was actually explicitly specified,
> > then
> > I guess it makes sense to at least try to set it when resuming.
> >
> > So the point is, are we, at that time (i.e., during resume), able
> > to
> > tell whether the reason why the domain has an affinity, is because
> > the
> > user explicitly specified it? Out of the top of my head, I don't
> > think
> > we can, but I probably better have another look at the code
> > tomorrow...
> > :-/
>
> So I think what is needed is to save the original config-specified
> affinity (plus any updates), not fish the (probably libxl-generated)
> one out of the hypervisor.
>
I think that too.Well, we probably can even fish it from Xen, but we need to save it in a place/field which is not the one that is looked at in libxl to decide whether or not to run placement (or, in general, decide whether or not to use whatever libxl own default). And then make the resume code look at that new field, rather than at vcpu_[hard,soft]_affinity. Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Software Engineer @ SUSE https://www.suse.com/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
