From: Eric Auger <eric.auger@linaro.org>
To: Sinan Kaya <okaya@codeaurora.org>,
kvm@vger.kernel.org, timur@codeaurora.org, cov@codeaurora.org,
jcm@redhat.com, Baptiste Reynal <b.reynal@virtualopensystems.com>
Cc: shankerd@codeaurora.org, vikrams@codeaurora.org,
marc.zyngier@arm.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, vinod.koul@intel.com,
agross@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Alex Williamson <alex.williamson@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/3] vfio, platform: make reset driver a requirement
Date: Sun, 27 Mar 2016 17:21:50 +0200 [thread overview]
Message-ID: <56F7FA8E.9000707@linaro.org> (raw)
In-Reply-To: <56E96D4C.3080008@codeaurora.org>
Hi Sinan,
On 03/16/2016 03:27 PM, Sinan Kaya wrote:
> Hi Baptiste,
>
>>> I couldn't see a reset function for AMBA devices.
>>>
>>> Is there anyway to write reset function for it? I have no experience with
>>> AMBA devices.
>> To my knowledge only the PL330 DMA controller (drivers/dma/pl330.c) was
>> passthrough'ed at some point, rather for development purpose than
>> production purpose. This was done by Virtual Open Systems (ask Baptiste
>> for more details). But I don't think this is really used.
>
> Are you OK with requiring reset driver for AMBA devices too? The PL330
> driver won't work until a reset driver is submitted for it.
>
>>>
>>> Would you include a reset needed flag and just not require it for AMBA?
>>> (I honestly don't like this idea)
>>>
>> I think the requirement also makes sense for AMBA.
>>
>> Maybe an option would be to add a module parameter that would allow to
>> use the vfio platform/amba driver without reset module (with explicit
>> opt-in from the user). Maybe this can be done later on.
>
> I can see this flag useful for testing purposes but it should not be used in
> production.
>
> How about I add a module parameter which is not set by default? When set,
> I don't perform the reset requirement check.
Yes that's what I meant
Best Regards
Eric
>
>>
>> FYI I will not have access to my mailbox until the end of the week.
>
> OK, no rush.
>
>>
>> Best Regards
>>
>> Eric
>>
>
>
next prev parent reply other threads:[~2016-03-27 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 16:54 [PATCH V2 0/3] vfio, platform: add HIDMA and ACPI support Sinan Kaya
2016-03-11 16:54 ` [PATCH V2 1/3] vfio, platform: add support for ACPI while detecting the reset driver Sinan Kaya
2016-03-11 16:54 ` [PATCH V2 2/3] vfio, platform: make reset driver a requirement Sinan Kaya
2016-03-13 17:25 ` Sinan Kaya
[not found] ` <56E5A271.6000408-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-03-16 4:36 ` Eric Auger
[not found] ` <56E8E2CD.3020604-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-03-16 14:27 ` Sinan Kaya
2016-03-27 15:21 ` Eric Auger [this message]
2016-03-27 17:55 ` Sinan Kaya
2016-03-11 16:54 ` [PATCH V2 3/3] vfio, platform: add QTI HIDMA reset driver Sinan Kaya
2016-03-11 17:00 ` Sinan Kaya
[not found] ` <1457715275-11925-4-git-send-email-okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-03-11 18:35 ` kbuild test robot
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=56F7FA8E.9000707@linaro.org \
--to=eric.auger@linaro.org \
--cc=agross@codeaurora.org \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=jcm@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=okaya@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=vikrams@codeaurora.org \
--cc=vinod.koul@intel.com \
/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).