From: John Byrne <john.l.byrne@hp.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: Guy Zana <guy@neocleus.com>,
xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
Date: Thu, 06 Sep 2007 16:16:29 -0700 [thread overview]
Message-ID: <46E08A4D.8050706@hp.com> (raw)
In-Reply-To: <13A2F7DE1BAEA345A61DD40F303ED7A667D9DD@scsmsx412.amr.corp.intel.com>
When I use these patches and start a nativedom with a directly-assigned
NIC and no IOMMU, I get a lock up. Running the same
domain/configuration/machine with the direct-io.hg tree worked fine. The
crash output is below. If you'd like more information, let me know.
John Byrne
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) pt_irq.c:81:d1 invalid assert_option value
(XEN) WARNING: send pio with something already pending (9)?
(XEN) domain_crash_sync called from hvm.c:485
(XEN) Domain 1 (vcpu#0) crashed on cpu#7:
(XEN) ----[ Xen-3.0-unstable x86_32 debug=n Not tainted ]----
(XEN) CPU: 7
(XEN) EIP: 0000:[<00100fcb>]
(XEN) EFLAGS: 00000002 CONTEXT: hvm
(XEN) eax: 00000064 ebx: 001390c4 ecx: 001390c4 edx: 000000e9
(XEN) esi: 00103762 edi: 00101bf0 ebp: 00139038 esp: 00139038
(XEN) cr0: 00000011 cr4: 00000000 cr3: 00000000 cr2: 00000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000
(XEN) domain_crash_sync called from hvm.c:132
(XEN) domain_crash_sync called from hvm.c:132
(XEN) domain_crash_sync called from hvm.c:132
(XEN) domain_crash_sync called from hvm.c:132
....
(XEN) *** [ Xen-3.0-unstable x86_32 debug=n Not tainted ]----(XEN)
----[ Xen-3.0-unstable x86_32 debug=n Not tainted ]----(XEN) e
x86_32 debug=n Not tainted ]----
(XEN) ----[ Xen-3.0-unstable x86_32 debug=n Not tainted ]----
(XEN) CPU: 6
(XEN) CPU: 6(XEN) idle_loop+0x1b/0x90+010246 CONTEXT: hypervisor
(XEN) EFLAGS: 00010246 CONTEXT: hypervisor
(XEN) eax: 00000300 ebx: ffbe7fb4 ecx: 00000000 edx: 00000006
(XEN) esi: ff1a8430 edi: 91d91b27 ebp: 0000001c esp: ffbe7fa8
(XEN) cr0: 8005003b cr4: 000026d0 cr3: 3c6ee000 cr2: b7bf7000
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) do_page_fault+0x45/0x3b0
(XEN) (XEN) Xen stac00010246Xen stac00010246
CR3: 00000000(XEN) ffbea080
ax: 6563696c ebx: 0000e010 ecx: 00010246 edx: ff1b7fb4(XEN)
ffbea080 00000001
si: 0000e010 edi: 00000000 ebp: ff1b40ec esp: ff1b40a8(XEN)
00000000
s: e010 es: e010 fs: 0000 gs: 0000 ss: e010(XEN) c1351f90
00000006 00000006
00000006
(XEN) c03d7180 00000000 000e0007 c01013a7 00000061 00000246 c1351f8c
00000069
(XEN) 0000007b 0000007b 00000000 00000000 00000006 ffbea080
(XEN) Xen call trace:
(XEN) [<ff1209fb>] idle_loop+0x1b/0x90
(XEN)
Kay, Allen M wrote:
> The following 6 patches contains merge of Intel VT-d and Neocleus' 1:1
> mapping patches for enabling HVM guest direct device access that were
> last submitted around end of May. These patches applied cleanly to
> changeset 15730.
>
> To enabled xen vt-d code, add "ioapic_ack=old" to xen boot parameter in
> grub.conf on systems with VT-d hardware.
>
> To enabled xen 1:1 mapping code, add "enabled_nativedom=1" to xen boot
> parameter in grub.conf.
>
> Signed-off-by: Allen Kay <allen.m.kay@intel.com>
> Signed-off-by: Guy Zana <guy@neocleus.com>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-09-06 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 0:08 [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough Kay, Allen M
2007-09-06 23:16 ` John Byrne [this message]
2007-09-07 0:00 ` Kay, Allen M
2007-09-07 23:44 ` John Byrne
2007-09-11 12:49 ` Keir Fraser
2007-09-11 13:04 ` Keir Fraser
2007-09-12 1:21 ` Kay, Allen M
2007-09-12 9:03 ` Keir Fraser
2007-09-12 22:37 ` Kay, Allen M
2007-09-11 21:27 ` Kay, Allen M
2007-09-12 9:01 ` Keir Fraser
2007-09-16 17:26 ` [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mregedcode " Guy Zana
2007-09-17 8:25 ` Keir Fraser
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=46E08A4D.8050706@hp.com \
--to=john.l.byrne@hp.com \
--cc=allen.m.kay@intel.com \
--cc=guy@neocleus.com \
--cc=keir@xensource.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.