From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Hypervisor crash(!) on xl cpupool-numa-split Date: Wed, 9 Feb 2011 12:27:27 +0000 Message-ID: References: <4D41FD3A.5090506@amd.com> <201102021539.06664.stephan.diestelhorst@amd.com> <4D4974D1.1080503@ts.fujitsu.com> <201102021701.05665.stephan.diestelhorst@amd.com> <4D4A43B7.5040707@ts.fujitsu.com> <4D4A72D8.3020502@ts.fujitsu.com> <4D4C08B6.30600@amd.com> <4D4FE7E2.9070605@amd.com> <4D4FF452.6060508@ts.fujitsu.com> <4D50D80F.9000007@ts.fujitsu.com> <4D517051.10402@amd.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=0016e6deddc88ff07e049bd896f5 Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andre Przywara Cc: Juergen Gross , "xen-devel@lists.xensource.com" , "Diestelhorst, Stephan" List-Id: xen-devel@lists.xenproject.org --0016e6deddc88ff07e049bd896f5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sorry, forgot the patch... -G On Wed, Feb 9, 2011 at 12:27 PM, George Dunlap wrote: > On Tue, Feb 8, 2011 at 4:33 PM, Andre Przywara w= rote: >> (XEN) cpu_disable_scheduler: Migrating d0v18 from cpu 24 >> (XEN) cpu_disable_scheduler: Migrating d0v34 from cpu 24 >> (XEN) cpu_disable_scheduler: Migrating d0v42 from cpu 24 >> (XEN) cpu_disable_scheduler: Migrating d0v18 from cpu 25 >> (XEN) cpu_disable_scheduler: Migrating d0v34 from cpu 25 >> (XEN) cpu_disable_scheduler: Migrating d0v42 from cpu 25 >> (XEN) cpu_disable_scheduler: Migrating d0v18 from cpu 26 >> (XEN) cpu_disable_scheduler: Migrating d0v32 from cpu 26 >> (XEN) cpu_disable_scheduler: Migrating d0v42 from cpu 26 >> (XEN) cpu_disable_scheduler: Migrating d0v18 from cpu 27 >> (XEN) cpu_disable_scheduler: Migrating d0v24 from cpu 27 >> (XEN) cpu_disable_scheduler: Migrating d0v32 from cpu 27 >> (XEN) cpu_disable_scheduler: Migrating d0v42 from cpu 27 >> (XEN) cpu_disable_scheduler: Migrating d0v3 from cpu 28 >> (XEN) cpu_disable_scheduler: Migrating d0v18 from cpu 28 >> (XEN) cpu_disable_scheduler: Migrating d0v25 from cpu 28 >> (XEN) cpu_disable_scheduler: Migrating d0v32 from cpu 28 >> (XEN) cpu_disable_scheduler: Migrating d0v39 from cpu 28 >> (XEN) cpu_disable_scheduler: Migrating d0v3 from cpu 29 > > Interesting -- what seems to happen here is that as cpus are disabled, > vcpus are "shovelled" in an accumulative fashion from one cpu to the > next: > * v18,34,42 start on cpu 24. > * When 24 is brought down, they're all migrated to 25; then when 25 is > brougth down, to 26, then to 27 > * v24 is running on cpu 27, so when 27 is brought down, v24 is added to t= he mix > * v3 is running on cpu 28, so all of them plus v3 are shoveled onto cpu 2= 9. > > While that behavior may not be ideal, it should certainly be bug-free. > > Another interesting thing to note is that the bug happened on pcpu 32, > but there were no advertised migrations from that cpu. > > Andre, can you fold the attached patch into your testing? > > Thanks for all your work on this. > > =A0-George > --0016e6deddc88ff07e049bd896f5 Content-Type: text/x-diff; charset=US-ASCII; name="cpupools-debug-curr-not-idle.diff" Content-Disposition: attachment; filename="cpupools-debug-curr-not-idle.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_gjy7s0540 ZGlmZiAtciA5ZGRmMDcwMjJiM2YgeGVuL2NvbW1vbi9zY2hlZF9jcmVkaXQuYwotLS0gYS94ZW4v Y29tbW9uL3NjaGVkX2NyZWRpdC5jCVdlZCBGZWIgMDkgMTA6Mjk6NTMgMjAxMSArMDAwMAorKysg Yi94ZW4vY29tbW9uL3NjaGVkX2NyZWRpdC5jCVdlZCBGZWIgMDkgMTA6NTE6MDUgMjAxMSArMDAw MApAQCAtMzgxLDYgKzM4MSwxNCBAQAogICAgICAgICBwZXJfY3B1KHNjaGVkdWxlX2RhdGEsIGNw dSkuc2NoZWRfcHJpdiA9IHNwYzsKIAogICAgIC8qIFN0YXJ0IG9mZiBpZGxpbmcuLi4gKi8KKyAg ICBpZiAoICFpc19pZGxlX3ZjcHUocGVyX2NwdShzY2hlZHVsZV9kYXRhLCBjcHUpLmN1cnIpICkK KyAgICB7CisgICAgICAgIHByaW50aygiJXM6IGN1cnIgZCVkdiVkIG9uIHAlZCFcbiIsCisgICAg ICAgICAgICAgICBfX2Z1bmNfXywKKyAgICAgICAgICAgICAgIHBlcl9jcHUoc2NoZWR1bGVfZGF0 YSwgY3B1KS5jdXJyLT5kb21haW4tPmRvbWFpbl9pZCwKKyAgICAgICAgICAgICAgIHBlcl9jcHUo c2NoZWR1bGVfZGF0YSwgY3B1KS5jdXJyLT52Y3B1X2lkLAorICAgICAgICAgICAgICAgY3B1KTsK KyAgICB9CiAgICAgQlVHX09OKCFpc19pZGxlX3ZjcHUocGVyX2NwdShzY2hlZHVsZV9kYXRhLCBj cHUpLmN1cnIpKTsKICAgICBjcHVfc2V0KGNwdSwgcHJ2LT5pZGxlcnMpOwogCg== --0016e6deddc88ff07e049bd896f5 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --0016e6deddc88ff07e049bd896f5--