From: Mike Wray <mike.wray@hp.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen,tools: pincpu use vcpu and cpumap_t
Date: Tue, 03 May 2005 17:51:44 +0100 [thread overview]
Message-ID: <4277AC20.7060804@hp.com> (raw)
In-Reply-To: <20050426223109.GC14932@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Ryan Harper wrote:
> Here is an update to the previous pincpu patches. This patch updates
> the pincpu dom0op to use a cpumap_t pointer, rather than specifying a
> size in the interface. cpumap_t is current typedef'ed to an unsigned
> long. xm list -v now truncates the cpumap field to only show the bits
> of the map that are relevant. That is, if you have four VCPUS, you will
> only see the first four bits of the cpumap.
>
> This patch compiles against current unstable tree, but I could not test
> it as the current unstable tree crashes dom0 when booting domU. I back
> ported the patch to 20050420 snapshot and it worked there.
>
This patch causes the dom0 crash I reported on the current unstable
(attached) so it needs fixing before applying.
Mike
[-- Attachment #2: crash.eml --]
[-- Type: message/rfc822, Size: 5653 bytes --]
From: Mike Wray <mike.wray@hp.com>
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] Reproducible dom-0 crash
Date: Fri, 29 Apr 2005 11:44:29 +0100
Message-ID: <4272100D.9020501@hp.com>
Using unstable as of change set 1.1389.1.12 05/04/29 09:30,
I get the following dom-0 crash when xend starts:
(XEN) BUG at domain.c:136
(XEN) CPU: 0
(XEN) EIP: 0808:[<ff1057bc>]
(XEN) EFLAGS: 00010292 CONTEXT: hypervisor
(XEN) eax: 00000000 ebx: ff18c900 ecx: 000003f8 edx: 00000000
(XEN) esi: ff18b080 edi: feeea000 ebp: feee9000 esp: ff103f24
(XEN) ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810 cs: 0808
(XEN) Stack trace from ESP=ff103f24:
(XEN) ff1455ec ff145622 00000088 c000eb4c 000002d3 000002d3 ff19c000 [ff11e91f]
(XEN) 0c2d3063 ff18c900 e0000000 00000008 fe310ae8 0c2ba063 ff18cb00 00000000
(XEN) 00000001 00000000 ff18c900 ff18c900 c4293f54 ff18b080 ff103fb8 [ff129f63]
(XEN) ff18c900 00000000 0000c2d2 0000c2d2 feee8bfc 0c2d2bfc 00000000 ff18b080
(XEN) c42d4000 00000000 00000000 [ff1346fe] ff103fb8 ffffffff c42d3000 0c2d3063
(XEN) c42d4000 00000000 00000000 0000eb4c 000e0000 c01145e9 00000061 00010287
(XEN) c4293f54 00000069 0000007b 0000007b 00000000 00000000 ff18b080
(XEN) Call Trace from ESP=ff103f24:
(XEN) [<ff11e91f>] [<ff129f63>] [<ff1346fe>]
****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************
Mike
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-05-03 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 22:31 [PATCH] xen,tools: pincpu use vcpu and cpumap_t Ryan Harper
2005-04-26 23:14 ` Lars Rasmusson
2005-05-03 16:51 ` Mike Wray [this message]
2005-05-03 23:58 ` [RESUBMIT] [PATCH] xen, tools: " Ryan Harper
2005-05-05 15:49 ` Mike Wray
2005-05-10 13:59 ` Mike Wray
2005-05-10 14:59 ` Ryan Harper
2005-05-10 15:55 ` Ryan Harper
2005-05-11 15:16 ` Mike Wray
2005-05-11 20:30 ` Christian Limpach
2005-05-11 20:41 ` Kip Macy
2005-05-11 21:17 ` Christian Limpach
2005-05-11 21:18 ` Kip Macy
2005-05-12 15:16 ` Mike Wray
2005-05-12 16:06 ` Mike Wray
2005-05-12 16:17 ` Ryan Harper
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 0:51 [PATCH] xen,tools: " Ian Pratt
2005-04-27 14:04 ` Ryan Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4277AC20.7060804@hp.com \
--to=mike.wray@hp.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=ryanh@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.