From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel Schroeder <sec@dschroeder.info>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"He, Qing" <qing.he@intel.com>
Subject: Re: pvops dom0 20090821 issue (msi)
Date: Fri, 21 Aug 2009 15:47:07 -0700 [thread overview]
Message-ID: <4A8F23EB.2070403@goop.org> (raw)
In-Reply-To: <4A8E6BDA.2080600@dschroeder.info>
On 08/21/09 02:41, Daniel Schroeder wrote:
> Hi Jeremy,
>
> compilation[1] breaks with:
>
> grep -i msi .config
> CONFIG_ARCH_SUPPORTS_MSI=y
> # CONFIG_PCI_MSI is not set
>
> with msi configured it compiles...
>
> grep -i msi .config
> CONFIG_ARCH_SUPPORTS_MSI=y
> CONFIG_PCI_MSI=y
>
> may be its related, this compiled kernel is waiting forever at boot time
> during "starting xen control daemon"...three finger salute stalls after
> "unmounting network filesystems"...
>
> if i add pci=nomsi system boots up and everything is fine :)
>
Qing He, any thoughts?
J
> -
> daniel
>
>
>
> [1]
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-x86
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> CC arch/x86/xen/pci.o
> arch/x86/xen/pci.c: In function 'xen_setup_msi_irqs':
> arch/x86/xen/pci.c:96: error: 'struct pci_dev' has no member named
> 'msi_list'
> arch/x86/xen/pci.c:96: error: 'struct pci_dev' has no member named
> 'msi_list'
> make[2]: *** [arch/x86/xen/pci.o] Error 1
> make[1]: *** [arch/x86/xen] Error 2
> make: *** [arch/x86] Error 2
> make: *** Waiting for unfinished jobs....
>
>
next prev parent reply other threads:[~2009-08-21 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 9:41 pvops dom0 20090821 issue (msi) Daniel Schroeder
2009-08-21 22:47 ` Jeremy Fitzhardinge [this message]
[not found] ` <20090824094357.GA32567@ub-qhe2>
2009-08-24 11:27 ` Daniel Schroeder
2009-08-24 23:37 ` Jeremy Fitzhardinge
2009-08-25 9:11 ` [PATCH][RESEND] xen: fix msi build errors Qing He
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=4A8F23EB.2070403@goop.org \
--to=jeremy@goop.org \
--cc=qing.he@intel.com \
--cc=sec@dschroeder.info \
--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.