public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gavin Shan <gwshan@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] vfio: Fix build failure seen if vfio is built as module and EEH is enabled
Date: Sat, 09 Aug 2014 15:28:08 -0700	[thread overview]
Message-ID: <53E6A078.6040907@roeck-us.net> (raw)
In-Reply-To: <1407612480.9800.1.camel@ul30vt.home>

On 08/09/2014 12:28 PM, Alex Williamson wrote:
> On Sat, 2014-08-09 at 10:04 -0700, Guenter Roeck wrote:
>> The following build failure is seen with ppc:allmodconfig.
>>
>> ERROR: ".vfio_spapr_iommu_eeh_ioctl" [drivers/vfio/vfio_iommu_spapr_tce.ko] undefined!
>> ERROR: ".vfio_spapr_pci_eeh_open" [drivers/vfio/pci/vfio-pci.ko] undefined!
>> ERROR: ".vfio_spapr_pci_eeh_release" [drivers/vfio/pci/vfio-pci.ko] undefined!
>>
>> Simply exporting the missing symbols is insufficient, since drivers/vfio
>> can be built as module but drivers/vfio/vfio_spapr_eeh.c depends on
>> EEH which is boolean. The combination of obj-m for drivers/vfio and obj-y
>> for drivers/vfio/vfio_spapr_eeh.o results in the symbols being missed even
>> if exported.
>>
>> Export missing symbols and introduce new tristate configuration option
>> VFIO_EEH depending on both EEH and VFIO to fix the problem.
>>
>> Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>
> Please try:
>
> git://github.com/awilliam/linux-vfio.git next
>
> This will be part of the next linux-next build, should resolve the
> problem, and I plan to ask for a pull early this coming week.  Thanks,
>

That should do for the most part, but it will select VFIO_SPAPR_EEH
even if EEH is not configured. You would need something like
	select VFIO_SPAPR_EEH if (PPC_POWERNV || PPC_PSERIES) && EEH
to prevent that.

Guenter

  reply	other threads:[~2014-08-09 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 17:04 [PATCH] vfio: Fix build failure seen if vfio is built as module and EEH is enabled Guenter Roeck
2014-08-09 19:28 ` Alex Williamson
2014-08-09 22:28   ` Guenter Roeck [this message]
2014-08-09 23:18     ` Alex Williamson
2014-08-09 23:27       ` Guenter Roeck

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=53E6A078.6040907@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alex.williamson@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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