linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alex.williamson@redhat.com (Alex Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] VFIO: platform: enable ARM64 build
Date: Mon, 22 Jun 2015 10:26:01 -0600	[thread overview]
Message-ID: <1434990361.3700.228.camel@redhat.com> (raw)
In-Reply-To: <55883038.9060405@linaro.org>

On Mon, 2015-06-22 at 17:56 +0200, Eric Auger wrote:
> Hi Baptiste,
> 
> No unfortunately I don't have any HW to test this currently. I just
> test-compiled this. Up to you to decide whether you prefer waiting for a
> functional test for this. I sent that patch since I expect ARM64 to be
> the main platform where the VFIO platform drivermight be used for
> virtualization use case.

FWIW, I've been occasionally removing the arch condition entirely to
build test on x86 as well.  The Intel VT-d code certainly allows for
devices described by ACPI, which I assume would fall under the platform
category, but I don't know of any systems that do this, let alone any
x86 platform devices that we'd actually want to expose to the user.
Eventually we might want to consider decoupling this from an arch-based
Kconfig option, but we could just as easily let the first non-ARM user
think about that problem.  Thanks,

Alex

> On 06/22/2015 05:49 PM, Baptiste Reynal wrote:
> > Acked-by: Baptiste Reynal <b.reynal@virtualopensystems.com>
> > Tested-by: Baptiste Reynal <b.reynal@virtualopensystems.com>
> > 
> > Out of curiosity, have you get VFIO running on ARM64 without any problems ?
> > 
> > On Mon, Jun 15, 2015 at 11:13 AM, Eric Auger <eric.auger@linaro.org> wrote:
> >> This patch enables building VFIO platform and derivatives on ARM64.
> >>
> >> Signed-off-by: Eric Auger <eric.auger@linaro.org>
> >> ---
> >>  drivers/vfio/platform/Kconfig | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/vfio/platform/Kconfig b/drivers/vfio/platform/Kconfig
> >> index 1df7477..bb30128 100644
> >> --- a/drivers/vfio/platform/Kconfig
> >> +++ b/drivers/vfio/platform/Kconfig
> >> @@ -1,6 +1,6 @@
> >>  config VFIO_PLATFORM
> >>         tristate "VFIO support for platform devices"
> >> -       depends on VFIO && EVENTFD && ARM
> >> +       depends on VFIO && EVENTFD && (ARM || ARM64)
> >>         select VFIO_VIRQFD
> >>         help
> >>           Support for platform devices with VFIO. This is required to make
> >> --
> >> 1.9.1
> >>
> 

  reply	other threads:[~2015-06-22 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  9:13 [PATCH] VFIO: platform: enable ARM64 build Eric Auger
2015-06-22 15:49 ` Baptiste Reynal
2015-06-22 15:56   ` Eric Auger
2015-06-22 16:26     ` Alex Williamson [this message]
2015-06-23  6:56       ` Baptiste Reynal
2015-06-23  7:06         ` Eric Auger

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=1434990361.3700.228.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).