From mboxrd@z Thu Jan 1 00:00:00 1970 From: tupeng212 Subject: CPU stucked when xen initializing, why? Date: Thu, 16 Aug 2012 22:12:26 +0800 Message-ID: <2012081622122189073014@gmail.com> Reply-To: tupeng212 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6719232616089783824==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============6719232616089783824== Content-Type: multipart/alternative; boundary="----=_001_NextPart255634547472_=----" This is a multi-part message in MIME format. ------=_001_NextPart255634547472_=---- Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 RGVhciBhbGw6DQpJIG5lZWQgeW91ciBoZWxwLg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KX19zdGFydF94ZW4gDQp7DQogICAgaW9t bXVfc2V0dXAoKTsgICAgLyogc2V0dXAgaW9tbXUgaWYgYXZhaWxhYmxlICovDQogICAgc21wX3By ZXBhcmVfY3B1cyhtYXhfY3B1cyk7DQp9DQoNCnJvdXRpbmcgcGF0Y2g6DQpzbXBfcHJlcGFyZV9j cHVzIC0+IHNtcF9ib290X2NwdXMgLT4gZG9fYm9vdF9jcHUgLT4gd2FrZXVwX3NlY29uZGFyeV9j cHUgDQoNCndoZW4gQlNQICJTZW5kaW5nIFNUQVJUVVAgIzEobnVtX3N0YXJ0cz0yKSIsIGhhbmRs aW5nIENQVSMzMSwgc3lzdGVtIHdhcyBzdHVjaywgSSBkb24ndCBrbm93IHdoeS4NCmJlc2lkZXMs IHRoZXJlIGFyZSA2NCBwaHlzaWNhbCBDUFVzLg0Kd2FrZXVwX3NlY29uZGFyeV9jcHUgDQp7DQpm b3IgKGogPSAxOyBqIDw9IG51bV9zdGFydHM7IGorKykgew0KRHByaW50aygiU2VuZGluZyBTVEFS VFVQICMlZC5cbiIsaik7IC8vdGhpcyBwcmludGluZyBhcHBlYXJlZA0KYXBpY19yZWFkX2Fyb3Vu ZChBUElDX1NQSVYpOw0KYXBpY193cml0ZShBUElDX0VTUiwgMCk7DQphcGljX3JlYWQoQVBJQ19F U1IpOw0KRHByaW50aygiQWZ0ZXIgYXBpY193cml0ZS5cbiIpOyAvL2J1dCB0aGlzIHByaW50IG5l dmVyIGNvbWUgb3V0LCBhbmQgc3lzdGVtIHdhcyBzdHVjaw0KfQ0KfQ0KLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCjEgIGFwaWNfd3JpdGUvcmVh ZCgpIGNvbnRhaW5zIHNvbWUgbG9jayB0aGVyZT8gaG93IHRvIGNoZWNrID8NCg0KMiBCU1AgQ1BV ICdzIHJpcCBqdW1wZWQgdG8gYW5vdGhlciBwbGFjZSBvd2luZyB0byBzdWNoIGFzIGFuIGludGVy cnVwdGlvbj8NCnRoZSBtb3N0IHN1c3BlY3RlZCBwbGFjZSBJIGRvdWJ0IGlzIGlvbW11X3NldHVw KCksIGFuZCBpbiB0aGlzIGZ1bmN0aW9uLCANCkkvTyB2aXJ0dWFsaXNhdGlvbiBlbmFibGVkDQpE b20wIG1vZGU6IFJlbGF4ZWQNCmJ1dCBpb21tdV9wYWdlX2ZhdWx0IG5ldmVyIGVudGVyZWQgYWZ0 ZXIgY2hlY2tpbmcgbG9nLg0KDQozIENhbiBzb21lb25lIHRlYWNoIG1lIGEgbWV0aG9kIHRvIGFu YWx5emUgWGVuJ3Mgc3R1Y2sgc3RhY2ssIGZvciBleGFtcGxlIA0KY29yZSBkdW1wPy4uLiB0aGlz IHByb2JsZW0gaGFwcGVuZWQgYWNjaWRlbnRhbGx5LCBoYXJkIHRvIGNhdGNoIGl0cyBwcmludGlu Zy4NCnNvIGlmIGFwcGVhciwgSSdkIGxpa2UgdG8gYW5hbHl6ZSBpdCBpbnN0YW50bHkuDQoNClRo YW5rIHlvdSB2ZXJ5IG11Y2ghDQoNCg0KDQoNCnR1cGVuZzIxMg== ------=_001_NextPart255634547472_=---- Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Dear all:

I need your help.

--------------------------------------------------------

__start_xen

{

iommu_setup(); /* = ;setup iommu if available */

smp_prepare_cpus(max_cpus);

}

routing patch:

smp_prepare_cpus -> smp_boot_cpus -> do_boot_cpu ->=20 wakeup_secondary_cpu

when BSP "Sending STARTUP #1(num_starts=3D2)", handling CPU= #31,=20 system was stuck, I don't know why.

besides, there are 64 physical CPUs.

wakeup_secondary_cpu

{

for (j =3D 1; j <=3D num_starts;&n= bsp;j++) {

Dprintk("Sending STARTUP #%d.\n",j); //this printing=20 appeared

apic_read_around(APIC_SPIV);

apic_write(APIC_ESR, 0);

apic_read(APIC_ESR);

Dprintk("After apic_write.\n"); //but this print never come=20 out, and system was stuck

}

}

---------------------------------------------------

1 apic_write/read() contains some lock there? how to check ?

2 BSP CPU 's rip jumped to another place owing to such as an=20 interruption?

the most suspected place I doubt is iommu_setup(), and in this functi= on,=20

I/O virtualisation enabled

Dom0 mode: Relaxed

but iommu_page_fault never entered after checking log.

3 Can someone teach me a method to analyze Xen's stuck stack, fo= r=20 example

core dump?... this problem happened accidentally, hard to catch its=20 printing.

so if appear, I'd like to analyze it instantly.

Thank you very much!

tupeng212

------=_001_NextPart255634547472_=------ --===============6719232616089783824== 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.xen.org http://lists.xen.org/xen-devel --===============6719232616089783824==--