lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1434990361.3700.228.camel@redhat.com>
Date:	Mon, 22 Jun 2015 10:26:01 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Eric Auger <eric.auger@...aro.org>
Cc:	Baptiste Reynal <b.reynal@...tualopensystems.com>,
	eric.auger@...com,
	ARM SMMU DRIVER <linux-arm-kernel@...ts.infradead.org>,
	open list <linux-kernel@...r.kernel.org>, patches@...aro.org,
	Christoffer Dall <christoffer.dall@...aro.org>
Subject: Re: [PATCH] VFIO: platform: enable ARM64 build

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@...tualopensystems.com>
> > Tested-by: Baptiste Reynal <b.reynal@...tualopensystems.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@...aro.org> wrote:
> >> This patch enables building VFIO platform and derivatives on ARM64.
> >>
> >> Signed-off-by: Eric Auger <eric.auger@...aro.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
> >>
> 



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ