xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Edge <bruce.edge@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Tue, 5 Oct 2010 11:21:38 -0700	[thread overview]
Message-ID: <AANLkTim7RceMqdnj0wxvTUWHTtSEtGptSs+oFHurM9BA@mail.gmail.com> (raw)
In-Reply-To: <20101004144859.GA4484@dumpdata.com>

On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> 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

  reply	other threads:[~2010-10-05 18:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-09-27 19:16   ` Bruce Edge
2010-09-27 19:54     ` Konrad Rzeszutek Wilk
2010-09-27 23:54       ` Bruce Edge
2010-09-28  1:15         ` Jiang, Yunhong
2010-09-28  3:16           ` Bruce Edge
2010-09-28  3:26             ` Jiang, Yunhong
2010-09-28  4:45               ` Bruce Edge
2010-09-28 16:08                 ` Lin, Ray
2010-09-28 16:19                   ` Konrad Rzeszutek Wilk
2010-09-28 18:35                     ` Lin, Ray
2010-09-28 20:14                       ` Konrad Rzeszutek Wilk
2010-09-28 20:38                         ` Lin, Ray
2010-09-29  0:53                     ` Jiang, Yunhong
2010-09-30 16:30                       ` Lin, Ray
2010-09-28 14:56         ` Konrad Rzeszutek Wilk
2010-09-30 18:55           ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19   ` Bruce Edge
2010-10-01 23:30   ` Bruce Edge
2010-10-03  5:46     ` Bruce Edge
2010-10-03 12:08       ` Pasi Kärkkäinen
2010-10-04 14:48     ` Konrad Rzeszutek Wilk
2010-10-05 18:21       ` Bruce Edge [this message]
2010-10-06 14:21         ` Konrad Rzeszutek Wilk
2010-10-06 18:21           ` Bruce Edge
2010-10-08 16:48             ` Lin, Ray
2010-10-08 17:30               ` Konrad Rzeszutek Wilk
2010-10-08 17:40                 ` Lin, Ray
2010-10-08 17:52                 ` Bruce Edge
2010-10-08 21:01                   ` Lin, Ray
2010-10-08 17:56   ` Bruce Edge
2010-10-11 21:12   ` Bruce Edge
2010-10-11 21:46     ` Konrad Rzeszutek Wilk
2010-10-13 21:36       ` Bruce Edge
2010-10-13 21:46         ` Konrad Rzeszutek Wilk
2010-10-13 22:00           ` Bruce Edge
2010-10-13 22:08             ` Bruce Edge
2010-10-14 13:57               ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` Konrad Rzeszutek Wilk

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=AANLkTim7RceMqdnj0wxvTUWHTtSEtGptSs+oFHurM9BA@mail.gmail.com \
    --to=bruce.edge@gmail.com \
    --cc=konrad.wilk@oracle.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 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).