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

[Xen-devel] dependences for backporting to 4.5 [was: Re: [PATCH 2/3] xen: Have schedulers revise initial placement]



On Fri, 2016-08-05 at 07:24 -0600, Jan Beulich wrote:
> > > > On 01.08.16 at 14:32, <dario.faggioli@xxxxxxxxxx> wrote:
> > Yes, I think they're good backporting candidates.
> Well, they appear to work fine on 4.7, but putting them onto 4.5
> causes an early boot crash (BUG_ON( cpu != svc->vcpu->processor )
> in __runq_insert()). 
>
I just tested staging-4.5 plus your backport of these patches (i.e.,
the two commits that you have then reverted), and I haven't seen
this... how can it that be?

> Pulling in e59321d154 ("credit: remove cpu
> argument to __runq_insert()") obviously makes that crash go
> away, just to, a little later, hit the similar one close to the top
> of
> csched_load_balance().
> 
In fact, I'd say that as far as I can see, the same that I said about
backporting to 4.6, does the trick for 4.5 as well:

https://lists.xen.org/archives/html/xen-devel/2016-08/msg01673.html

I've double checked that I am using the proper tree and code, and it
looks like I do.

Can (anyone of) you have a go with that?

If I'm right, and "just" avoiding to call insert_vcpu() for idle vcpu
is enough, the question about what's the best path is the same as fo
4.6.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

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