From: Olaf Hering <olaf@aepfle.de>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com
Subject: Re: xenpaging fixes for kernel and hypervisor
Date: Wed, 22 Sep 2010 17:48:44 +0200 [thread overview]
Message-ID: <20100922154844.GD25088@aepfle.de> (raw)
In-Reply-To: <20100915160521.GA16644@aepfle.de>
Patrick,
there are three more changes to make xenpaging more robust.
Do you need to ack each one to get them merged in xen-unstable?
Should any of these changes go also into the xen-4.0-testing tree for
the 4.0.2 release? If so, I will prepare the patches for this branch.
One more thing: In an earlier mail you mentioned that realmode support
is not there yet. However, in my testing I can run grub and the bios and
even boot into Linux a bit. So it appears there is realmode support,
perhaps still incomplete because the guest crashes in (appearently)
early Linux init functions:
(XEN) realmode.c:115:d1 Failed to emulate insn.
(XEN) realmode.c:165:d1 Real-mode emulation failed @ 9000:0000f81a: 0f 00 00 00 00 00
(XEN) domain_crash called from realmode.c:166
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.1_21326_01-20100922.141534 x86_64 debug=y Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: 9000:[<000000000000f81a>]
(XEN) RFLAGS: 0000000000000246 CONTEXT: hvm guest
(XEN) rax: 0000000000000000 rbx: 0000000000008fb8 rcx: 0000000000000000
(XEN) rdx: 0000000000009000 rsi: 0000000000000008 rdi: 0000000000099fff
(XEN) rbp: 000000000000ffff rsp: 0000000000001ff2 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 0000000000000010 cr4: 0000000000000000
(XEN) cr3: 0000000000000000 cr2: 0000000000000000
(XEN) ds: 0000 es: 9000 fs: 9000 gs: 9000 ss: 9000 cs: 9000
(XEN) cpupool_rm_domain(dom=1,pool=0) n_dom 1
[ 127.709423] br0: port 2(vif1.0) entering disabled state
[ 127.732999] br0: port 2(vif1.0) entering disabled state
I'm poking around and adding debug to the gfn_to_mfn* functions, but none triggers.
Where should I start looking for this kind of bug?
Olaf
next prev parent reply other threads:[~2010-09-22 15:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 16:05 xenpaging fixes for kernel and hypervisor Olaf Hering
2010-09-15 16:08 ` [PATCH] xenpaging: handle GNTST_eagain in kernel drivers Olaf Hering
2010-09-16 3:44 ` Patrick Colp
2010-09-16 9:05 ` Keir Fraser
2010-09-16 13:33 ` Olaf Hering
2010-09-15 16:10 ` [PATCH] xenpaging: page-in granttable entries Olaf Hering
2010-09-15 16:11 ` [PATCH] xenpaging: fix crash in notify_via_xen_event_channel Olaf Hering
2010-09-15 16:12 ` [PATCH] xenpaging: avoid empty pagefile on unsupported hardware Olaf Hering
2010-09-22 15:38 ` [PATCH] xenpaging: handle XENMEM_decrease_reservation Olaf Hering
2010-09-22 15:40 ` [PATCH] xenpaging: break endless loop during inital page-out with large pagefiles Olaf Hering
2010-09-22 15:41 ` [PATCH] xenpaging: allow only one xenpaging call per guest Olaf Hering
2010-09-22 15:48 ` Olaf Hering [this message]
2010-09-22 16:49 ` xenpaging fixes for kernel and hypervisor Patrick Colp
2010-09-22 17:13 ` Keir Fraser
2010-09-22 17:14 ` Keir Fraser
2010-09-22 17:20 ` Olaf Hering
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=20100922154844.GD25088@aepfle.de \
--to=olaf@aepfle.de \
--cc=pjcolp@cs.ubc.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).