From: Baptiste Reynal <b.reynal@virtualopensystems.com>
To: Eric Auger <eric.auger@linaro.org>
Cc: eric.auger@st.com,
"moderated list:ARM SMMU DRIVER"
<linux-arm-kernel@lists.infradead.org>,
Alex Williamson <alex.williamson@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
patches@linaro.org,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [PATCH] VFIO: platform: enable ARM64 build
Date: Mon, 22 Jun 2015 17:49:15 +0200 [thread overview]
Message-ID: <CAN9JPjHh_DPzB1PRhkyaXjKvq47SYb6a4M0M=fO78Mp+YYefrQ@mail.gmail.com> (raw)
In-Reply-To: <1434359632-20278-1-git-send-email-eric.auger@linaro.org>
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-22 15:49 UTC|newest]
Thread overview: 5+ 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 [this message]
[not found] ` <55883038.9060405@linaro.org>
2015-06-22 16:26 ` Alex Williamson
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='CAN9JPjHh_DPzB1PRhkyaXjKvq47SYb6a4M0M=fO78Mp+YYefrQ@mail.gmail.com' \
--to=b.reynal@virtualopensystems.com \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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).