From: Babis Chalios <bchalios@amazon.es>
To: Alexander Graf <graf@amazon.de>, Sudan Landge <sudanl@amazon.com>,
<tytso@mit.edu>, <Jason@zx2c4.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<sathyanarayanan.kuppuswamy@linux.intel.com>,
<thomas.lendacky@amd.com>, <dan.j.williams@intel.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <dwmw@amazon.co.uk>, <xmarcalx@amazon.co.uk>
Subject: Re: [PATCH v4 5/5] virt: vmgenid: add support for devicetree bindings
Date: Tue, 16 Apr 2024 17:49:47 +0200 [thread overview]
Message-ID: <c4caca2d-8840-4ed5-b580-f984bd0ee5cd@amazon.es> (raw)
In-Reply-To: <1e4fad99-76d4-4c45-a924-b78b597c7cd6@amazon.de>
On 16/4/24 12:49, Alexander Graf wrote:
>
> On 09.04.24 20:11, Sudan Landge wrote:
>> Extend the vmgenid platform driver to support devicetree bindings.
>> With this support, hypervisors can send vmgenid notifications to
>> the virtual machine without the need to enable ACPI.
>> The bindings are located at:
>> Documentation/devicetree/bindings/rng/microsoft,vmgenid.yaml
>>
>> Signed-off-by: Sudan Landge <sudanl@amazon.com>
>> ---
>> drivers/virt/vmgenid.c | 53 ++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 51 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/virt/vmgenid.c b/drivers/virt/vmgenid.c
>> index 3d93e3fb94c4..e1ad74116c0c 100644
>> --- a/drivers/virt/vmgenid.c
>> +++ b/drivers/virt/vmgenid.c
>> @@ -2,12 +2,13 @@
>> /*
>> * Copyright (C) 2022 Jason A. Donenfeld <Jason@zx2c4.com>. All
>> Rights Reserved.
>> *
>> - * The "Virtual Machine Generation ID" is exposed via ACPI and
>> changes when a
>> + * The "Virtual Machine Generation ID" is exposed via ACPI or DT and
>> changes when a
>> * virtual machine forks or is cloned. This driver exists for
>> shepherding that
>> * information to random.c.
>> */
>> #include <linux/acpi.h>
>> +#include <linux/interrupt.h>
>> #include <linux/kernel.h>
>> #include <linux/module.h>
>> #include <linux/platform_device.h>
>> @@ -20,6 +21,7 @@ enum { VMGENID_SIZE = 16 };
>> struct vmgenid_state {
>> u8 *next_id;
>> u8 this_id[VMGENID_SIZE];
>> + int irq;
>> };
>> static void vmgenid_notify(struct device *device)
>> @@ -43,6 +45,14 @@ vmgenid_acpi_handler(acpi_handle __always_unused
>> handle,
>> vmgenid_notify(dev);
>> }
>> +static __maybe_unused irqreturn_t
>
>
> Why is this maybe_unused? It seems to be always referenced by
> vmgenid_add_of(), no?
You are right, Alex. I removed the attribute and build the kernel
without `CONFIG_OF`
without any warnings. I will remove it in the next version.
>
>
>> +vmgenid_of_irq_handler(int __always_unused irq, void *dev)
>> +{
>> + vmgenid_notify(dev);
>> +
>> + return IRQ_HANDLED;
>> +}
>> +
>> static int __maybe_unused
>> setup_vmgenid_state(struct vmgenid_state *state, u8 *next_id)
>> {
>> @@ -106,6 +116,35 @@ static int vmgenid_add_acpi(struct device
>> __maybe_unused *dev,
>> #endif
>> }
>> +static int vmgenid_add_of(struct platform_device *pdev,
>> + struct vmgenid_state *state)
>> +{
>> + u8 *virt_addr;
>> + int ret = 0;
>> +
>> + virt_addr = (u8 *)devm_platform_get_and_ioremap_resource(pdev,
>> 0, NULL);
>> + if (IS_ERR(virt_addr))
>> + return PTR_ERR(virt_addr);
>> +
>> + ret = setup_vmgenid_state(state, virt_addr);
>> + if (ret)
>> + return ret;
>> +
>> + ret = platform_get_irq(pdev, 0);
>> + if (ret < 0)
>> + return ret;
>
>
> Doesn't this error path need to do something about the ioremap'ed
> resource? Or does devm do that automatically for you?
devm should be doing this automatically according to this:
https://docs.kernel.org/driver-api/driver-model/devres.html#devres
Also, I took a quick look in other drivers and it looks like the virtio-mmio
probe callback follows the same pattern:
https://elixir.bootlin.com/linux/latest/source/drivers/virtio/virtio_mmio.c#L636
Cheers,
Babis
>
> Alex
>
>
>> +
>> + state->irq = ret;
>> + pdev->dev.driver_data = state;
>> +
>> + ret = devm_request_irq(&pdev->dev, state->irq,
>> vmgenid_of_irq_handler,
>> + IRQF_SHARED, "vmgenid", &pdev->dev);
>> + if (ret)
>> + pdev->dev.driver_data = NULL;
>> +
>> + return ret;
>> +}
>> +
>> static int vmgenid_add(struct platform_device *pdev)
>> {
>> struct vmgenid_state *state;
>> @@ -116,7 +155,10 @@ static int vmgenid_add(struct platform_device
>> *pdev)
>> if (!state)
>> return -ENOMEM;
>> - ret = vmgenid_add_acpi(dev, state);
>> + if (dev->of_node)
>> + ret = vmgenid_add_of(pdev, state);
>> + else
>> + ret = vmgenid_add_acpi(dev, state);
>> if (ret)
>> devm_kfree(dev, state);
>> @@ -124,6 +166,12 @@ static int vmgenid_add(struct platform_device
>> *pdev)
>> return ret;
>> }
>> +static const struct of_device_id vmgenid_of_ids[] = {
>> + { .compatible = "microsoft,vmgenid", },
>> + { },
>> +};
>> +MODULE_DEVICE_TABLE(of, vmgenid_of_ids);
>> +
>> static const struct acpi_device_id vmgenid_acpi_ids[] = {
>> { "VMGENCTR", 0 },
>> { "VM_GEN_COUNTER", 0 },
>> @@ -136,6 +184,7 @@ static struct platform_driver
>> vmgenid_plaform_driver = {
>> .driver = {
>> .name = "vmgenid",
>> .acpi_match_table = vmgenid_acpi_ids,
>> + .of_match_table = vmgenid_of_ids,
>> },
>> };
next prev parent reply other threads:[~2024-04-16 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 18:11 [PATCH v4 0/5] virt: vmgenid: Add devicetree bindings support Sudan Landge
2024-04-09 18:11 ` [PATCH v4 1/5] virt: vmgenid: rearrange code to make review easier Sudan Landge
2024-04-09 18:11 ` [PATCH v4 2/5] virt: vmgenid: change implementation to use a platform driver Sudan Landge
2024-04-09 18:11 ` [PATCH v4 3/5] virt: vmgenid: enable driver regardless of ACPI config Sudan Landge
2024-04-09 18:11 ` [PATCH v4 4/5] dt-bindings: rng: Add vmgenid support Sudan Landge
2024-04-10 20:09 ` Rob Herring
2024-04-09 18:11 ` [PATCH v4 5/5] virt: vmgenid: add support for devicetree bindings Sudan Landge
2024-04-16 10:49 ` Alexander Graf
2024-04-16 15:49 ` Babis Chalios [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 17:07 Sudan Landge
2024-04-09 18:07 ` Landge, Sudan
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=c4caca2d-8840-4ed5-b580-f984bd0ee5cd@amazon.es \
--to=bchalios@amazon.es \
--cc=Jason@zx2c4.com \
--cc=conor+dt@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=graf@amazon.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sudanl@amazon.com \
--cc=thomas.lendacky@amd.com \
--cc=tytso@mit.edu \
--cc=xmarcalx@amazon.co.uk \
/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).