|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
>> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>>
>> Your devel/xen-pcifront-0.7 isn't visible:
>
> It should be now. I pushed it late on Friday and repushed it today since it
> had
> some commits with the wrong committer field.
>
Is there anything special one needs to do when building this kernel?
The bzImage target err's out with undef'd syms:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `notify_remote_via_evtchn':
xen-pcifront.c:(.text+0x15b79): undefined reference to `hypercall_page'
xen-pcifront.c:(.text+0x15b9d): undefined reference to `hypercall_page'
drivers/built-in.o: In function `do_pci_op':
xen-pcifront.c:(.text+0x15cce): undefined reference to `xen_clear_irq_pending'
xen-pcifront.c:(.text+0x15ce6): undefined reference to `xen_poll_irq_timeout'
xen-pcifront.c:(.text+0x15cee): undefined reference to `xen_clear_irq_pending'
drivers/built-in.o: In function `pcifront_xenbus_probe':
xen-pcifront.c:(.text+0x161db): undefined reference to `xen_features'
xen-pcifront.c:(.text+0x161fc): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.text+0x16209): undefined reference to `get_phys_to_machine'
xen-pcifront.c:(.text+0x16221): undefined reference to `xenbus_grant_ring'
xen-pcifront.c:(.text+0x1623b): undefined reference to `xenbus_alloc_evtchn'
xen-pcifront.c:(.text+0x16261): undefined reference to
`bind_evtchn_to_irqhandler'
xen-pcifront.c:(.text+0x16273): undefined reference to `xenbus_free_evtchn'
xen-pcifront.c:(.text+0x1628b): undefined reference to
`xenbus_transaction_start'
xen-pcifront.c:(.text+0x162a6): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.text+0x162ce): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x162f8): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x1631e): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x16332): undefined reference to `xenbus_transaction_end'
xen-pcifront.c:(.text+0x16348): undefined reference to `xenbus_transaction_end'
xen-pcifront.c:(.text+0x16370): undefined reference to `xenbus_switch_state'
drivers/built-in.o: In function `pcifront_xenbus_remove':
xen-pcifront.c:(.text+0x16861): undefined reference to `unbind_from_irqhandler'
xen-pcifront.c:(.text+0x16871): undefined reference to `xenbus_free_evtchn'
xen-pcifront.c:(.text+0x16883): undefined reference to
`gnttab_end_foreign_access'
drivers/built-in.o: In function `pcifront_backend_changed':
xen-pcifront.c:(.ref.text+0xcca): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xd0c): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xd24): undefined reference to `xenbus_dev_error'
xen-pcifront.c:(.ref.text+0xd6e): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0xdb5): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xe07): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xe38): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xe63): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xed7): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xf39): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xfc9): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xff4): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0x100c): undefined reference to `xenbus_dev_error'
xen-pcifront.c:(.ref.text+0x1083): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0x10a8): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0x10d6): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0x10f2): undefined reference to `xenbus_switch_state'
drivers/built-in.o: In function `pcifront_cleanup':
xen-pcifront.c:(.exit.text+0x36): undefined reference to
`xenbus_unregister_driver'
make: *** [.tmp_vmlinux1] Error 1
I noticed the defconfig target had a couple of warnings too:
%> make defconfig
*** Default configuration is based on 'x86_64_defconfig'
warning: (XEN_PCIDEV_FRONTEND && X86) selects PCI_XEN which has unmet
direct dependencies (XEN)
warning: (XEN_PCIDEV_FRONTEND && X86) selects PCI_XEN which has unmet
direct dependencies (XEN)
#
# configuration written to .config
#
-Bruce
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Konrad Rzeszutek Wilk
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Konrad Rzeszutek Wilk
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem,
Bruce Edge <=
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Konrad Rzeszutek Wilk
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
- RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Lin, Ray
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Konrad Rzeszutek Wilk
- RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Lin, Ray
- Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
- RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Lin, Ray
Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem, Bruce Edge
|
|
|
|
|