From: Eric Auger <eric.auger@linaro.org>
To: Sinan Kaya <okaya@codeaurora.org>,
dmaengine@vger.kernel.org, marc.zyngier@arm.com,
mark.rutland@arm.com, timur@codeaurora.org,
devicetree@vger.kernel.org, cov@codeaurora.org,
vinod.koul@intel.com, jcm@redhat.com
Cc: shankerd@codeaurora.org, vikrams@codeaurora.org,
agross@codeaurora.org, arnd@arndb.de,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V14 8/9] vfio, platform: add support for ACPI while detecting the reset driver
Date: Tue, 8 Mar 2016 05:46:38 +0100 [thread overview]
Message-ID: <56DE592E.6010403@linaro.org> (raw)
In-Reply-To: <56DD9E7E.6000406@codeaurora.org>
Hi Sinan,
On 03/07/2016 04:30 PM, Sinan Kaya wrote:
> On 3/6/2016 11:09 PM, Eric Auger wrote:
>>> #define module_vfio_reset_handler(compat, acpihid, reset) \
>>>> MODULE_ALIAS("vfio-reset:" acpihid? acpihid: compat); \
>>>>
>>>> This way, we'll create an alias with one of the provided strings.
>> What if you want to use vfio platform driver for HiDMA in dt mode? the
>> HiDma reset module advertises both acpihid and dt compat support but an
>> alias module will be created only for acpihid. Then I think we will not
>> be able to load the reset module in dt mode with existing code.
>>
>
> Right, it won't work. Now that we know what MODULE_ALIAS does, there is no
> harm in doing this. I think we should do this.
>
> #define module_vfio_reset_handler(compat, acpihid, reset) \
> MODULE_ALIAS("vfio-reset:" compat); \
> MODULE_ALIAS("vfio-reset:" acpihid); \
>
> If we prefer ACPI over DT, there is no guarantee that somebody can boot DT
> kernel with ACPI kernel compilation option enabled.
>
> If one of these are null, then the module alias will be "vfio-reset:"
>
> Of course to make things prettier, we could use "NOT SUPPORTED" as a string
> instead of NULL. then, the module alias will be vfio-reset: NOT SUPPORTED".
>
> We could go one step further, and do.
>
> #define module_vfio_reset_handler(compat, acpihid, reset) \
> MODULE_ALIAS("vfio-reset: dt: " compat); \
> MODULE_ALIAS("vfio-reset: acpi: " acpihid); \
My gut feeling is we must not create a dummy alias when the mode
(dt/acpi) is not supported/tested. It fills the modinfo section with
spurious data, aliases are visible to modinfo, ...
So I personally foresee 2 solutions,
1) we create a single alias using acpihid if supported or compat if not.
Then even in dt mode we try to load this module through the acpihid
alias. Looks weird but should work.
2) We simply move the module alias declaration out of this macro (to the
reset module itself), define 2 aliases in case both dt and acpi are
supported & tested.
My personal preference is 2 I think.
Best Regards
Eric
>
> and change the code below for this too.
>
>
>> This could work however with some rework in vfio_platform_common.c. In
>> vfio_platform_get_reset we should try to load the module using the
>> acpihid if the module load using compat alias fails. In the look-up
>> table we can find the acpihid corresponding to the dt compat.
>
> I was planning to submit this for the next review. Still, I don't want to
> assume that acpihid is the only working option. Somebody can boot DT kernel.
>
> diff --git a/drivers/vfio/platform/vfio_platform_common.c b/drivers/vfio/platform/vfio_platform_common.c
> index 42d7545..ba585ad 100644
> --- a/drivers/vfio/platform/vfio_platform_common.c
> +++ b/drivers/vfio/platform/vfio_platform_common.c
> @@ -58,16 +58,30 @@ static vfio_platform_reset_fn_t vfio_platform_lookup_reset(const char *compat,
> return reset_fn;
> }
>
> -static void vfio_platform_get_reset(struct vfio_platform_device *vdev)
> +static int vfio_platform_get_reset(struct vfio_platform_device *vdev)
> {
> + int rc;
> +
> vdev->reset = vfio_platform_lookup_reset(vdev->compat, vdev->acpihid,
> &vdev->reset_module);
> - if (!vdev->reset) {
> - request_module("vfio-reset:%s", vdev->compat);
> - vdev->reset = vfio_platform_lookup_reset(vdev->compat,
> - vdev->acpihid,
> - &vdev->reset_module);
> - }
> + if (vdev->reset)
> + return 0;
> +
> + if (vdev->acpihid)
> + rc = request_module("vfio-reset:%s", vdev->acpihid);
> +
> + if (rc && vdev->compat)
> + rc = request_module("vfio-reset:%s", vdev->compat);
> +
> + if (rc)
> + return rc;
> +
> + vdev->reset = vfio_platform_lookup_reset(vdev->compat, vdev->acpihid,
> + &vdev->reset_module);
> + if (vdev->reset)
> + return 0;
> +
> + return -ENODEV;
> }
>
> static void vfio_platform_put_reset(struct vfio_platform_device *vdev)
> @@ -620,7 +634,11 @@ int vfio_platform_probe_common(struct vfio_platform_device *vdev,
> return ret;
> }
>
> - vfio_platform_get_reset(vdev);
> + ret = vfio_platform_get_reset(vdev);
> + if (ret) {
> + iommu_group_put(group);
> + return ret;
> + }
>
> mutex_init(&vdev->igate);
>
>
> Let me know what you think.
>
>
next prev parent reply other threads:[~2016-03-08 4:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 4:34 [PATCH V14 0/9] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-02-05 4:34 ` [PATCH V14 1/9] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2016-03-11 2:13 ` Vinod Koul
2016-02-05 4:34 ` [PATCH V14 2/9] dma: hidma: Add Device Tree binding Sinan Kaya
2016-03-11 2:16 ` Vinod Koul
2016-02-05 4:34 ` [PATCH V14 3/9] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2016-03-11 2:16 ` Vinod Koul
2016-02-05 4:34 ` [PATCH V14 4/9] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2016-03-11 2:17 ` Vinod Koul
2016-02-05 4:34 ` [PATCH V14 5/9] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-03-11 2:06 ` Vinod Koul
2016-03-11 3:08 ` Okaya
2016-03-11 16:02 ` Sinan Kaya
2016-03-11 16:32 ` Vinod Koul
2016-03-11 16:44 ` Sinan Kaya
2016-03-11 19:29 ` Sinan Kaya
2016-03-11 21:59 ` Sinan Kaya
2016-03-13 16:00 ` Vinod Koul
2016-03-14 13:53 ` Sinan Kaya
2016-03-13 15:59 ` Vinod Koul
2016-03-14 13:56 ` Sinan Kaya
2016-02-05 4:34 ` [PATCH V14 6/9] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-02-05 4:34 ` [PATCH V14 7/9] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-02-05 4:34 ` [PATCH V14 8/9] vfio, platform: add support for ACPI while detecting the reset driver Sinan Kaya
2016-02-26 16:24 ` Sinan Kaya
2016-02-26 17:15 ` Eric Auger
2016-02-26 19:21 ` Sinan Kaya
2016-03-02 18:34 ` Sinan Kaya
2016-03-03 23:14 ` Eric Auger
2016-03-04 5:20 ` Sinan Kaya
2016-03-07 4:09 ` Eric Auger
2016-03-07 15:30 ` Sinan Kaya
2016-03-08 4:46 ` Eric Auger [this message]
2016-03-08 5:07 ` Sinan Kaya
2016-03-08 15:44 ` Sinan Kaya
2016-02-05 4:34 ` [PATCH V14 9/9] vfio, platform: add QTI HIDMA " Sinan Kaya
2016-02-26 17:52 ` Eric Auger
2016-02-26 19:05 ` Sinan Kaya
2016-02-08 10:14 ` [PATCH V14 0/9] dma: add Qualcomm Technologies HIDMA driver Christoffer Dall
2016-02-08 14:24 ` Sinan Kaya
2016-02-08 17:00 ` Christoffer Dall
2016-02-26 16:21 ` Sinan Kaya
2016-02-26 16:52 ` Timur Tabi
2016-03-02 18:40 ` Sinan Kaya
2016-03-03 3:44 ` Vinod Koul
2016-03-03 15:22 ` Sinan Kaya
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=56DE592E.6010403@linaro.org \
--to=eric.auger@linaro.org \
--cc=agross@codeaurora.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jcm@redhat.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).