Re: [Xen-devel] Hypervisor crash(!) on xl cpupool-numa-split

[Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>]

On 02/16/11 15:11, Juergen Gross wrote:
> On 02/16/11 14:54, George Dunlap wrote:
> > Andre (and Juergen), can you try again with the attached patch?
> >
> > What the patch basically does is try to make "cpu_disable_scheduler()"
> > do what it seems to say it does. :-) Namely, the various
> > scheduler-related interrutps (both per-cpu ticks and the master tick)
> > is a part of the scheduler, so disable them before doing anything, and
> > don't enable them until the cpu is really ready to go again.
> >
> > To be precise:
> > * cpu_disable_scheduler() disables ticks
> > * scheduler_cpu_switch() only enables ticks if adding a cpu to a pool,
> > and does it after inserting the idle vcpu
> > * Modify semantics, s.t., {alloc,free}_pdata() don't actually start or
> > stop tickers
> > + Call tick_{resume,suspend} in cpu_{up,down}, respectively
> I tried this before :-)
> It didn't work for Andre, but may be there were some bits missing.
>
> > * Modify credit1's tick_{suspend,resume} to handle the master ticker
> > as well.
> >
> > With this patch (if dom0 doesn't get wedged due to all 8 vcpus being
> > on one pcpu), I can perform thousands of operations successfully.
> Nice. I'll try later. In the moment I'm testing another patch (attached
> for review, if you like). I think I've identified two possible races.
My patch works for me. I think I have to rework the locking for credit1, but
that shouldn't be too hard.

My machine survived 10000 iterations of your script with additional
consistency checks in the scheduler. Without my patch the machine crashed
after less then 500 iterations.


Juergen

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel