linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: Baptiste Reynal <b.reynal@virtualopensystems.com>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: eric.auger@st.com,
	ARM SMMU DRIVER <linux-arm-kernel@lists.infradead.org>,
	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: Tue, 23 Jun 2015 09:06:56 +0200	[thread overview]
Message-ID: <55890590.3070003@linaro.org> (raw)
In-Reply-To: <CAN9JPjFNZrgiK5dVQcLAhvE1_ceJ=mc3qXfKy7Q3gmVOmjwY0A@mail.gmail.com>

Hi Baptiste, Alex,
On 06/23/2015 08:56 AM, Baptiste Reynal wrote:
> On Mon, Jun 22, 2015 at 6:26 PM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
>> 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.
> 
> 
> On my side, VFIO has been tested on ARM64 using Fastmodels without
> problems, we can go ahead with the patch.

OK great

> 
>>
>> 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
>>
> 
> Indeed, I'd rather wait for someone to show up with some use cases and
> tests before removing this condition.
OK

Eric
> 
> Regards,
> Baptiste
> 
>>> 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
>>>>>
>>>
>>
>>
>>

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

      reply	other threads:[~2015-06-23  7:07 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
     [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 [this message]

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=55890590.3070003@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=christoffer.dall@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).