public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Kisel <romank@linux.microsoft.com>
To: Tianyu Lan <ltykernel@gmail.com>
Cc: arnd@arndb.de, bhelgaas@google.com, bp@alien8.de,
	catalin.marinas@arm.com, conor+dt@kernel.org,
	dave.hansen@linux.intel.com, decui@microsoft.com,
	haiyangz@microsoft.com, hpa@zytor.com, joey.gouly@arm.com,
	krzk+dt@kernel.org, kw@linux.com, kys@microsoft.com,
	lenb@kernel.org, lpieralisi@kernel.org,
	manivannan.sadhasivam@linaro.org, mark.rutland@arm.com,
	maz@kernel.org, mingo@redhat.com, oliver.upton@linux.dev,
	rafael@kernel.org, robh@kernel.org, ssengar@linux.microsoft.com,
	sudeep.holla@arm.com, suzuki.poulose@arm.com, tglx@linutronix.de,
	wei.liu@kernel.org, will@kernel.org, yuzenghui@huawei.com,
	devicetree@vger.kernel.org, kvmarm@lists.linux.dev,
	linux-acpi@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, x86@kernel.org, apais@microsoft.com,
	benhill@microsoft.com, bperkins@microsoft.com,
	sunilmut@microsoft.com
Subject: Re: [PATCH hyperv-next v5 09/11] Drivers: hv: vmbus: Introduce hv_get_vmbus_root_device()
Date: Mon, 10 Mar 2025 10:09:45 -0700	[thread overview]
Message-ID: <e3414583-0437-4fc4-b464-1426e5fe9628@linux.microsoft.com> (raw)
In-Reply-To: <CAMvTesCFZ6sxQp7qqSDjD9idRjVHxh96Sp4betomgFH-OFLZ3Q@mail.gmail.com>



On 3/10/2025 6:41 AM, Tianyu Lan wrote:
> On Sat, Mar 8, 2025 at 6:05 AM Roman Kisel <romank@linux.microsoft.com> wrote:
>>
>> The ARM64 PCI code for hyperv needs to know the VMBus root
>> device, and it is private.
>>
>> Provide a function that returns it. Rename it from "hv_dev"
>> as "hv_dev" as a symbol is very overloaded. No functional
>> changes.
>>
>> Signed-off-by: Roman Kisel <romank@linux.microsoft.com>
> 
> Why change all device's parent to vmbus_root_device?
> 

No changes from my account of the code. Please let me know if I am
misunderstanding the question.

> The ARM64 platform uses the device tree to enumerate vmbus
> devices..  Can we find the root device via device tree? vmbus
> code on the x86 use ACPI and it seems to work via ACPI.
> 
> 

Right, we find it from the DT as shown in the next patch:

+static struct irq_domain *hv_pci_of_irq_domain_parent(void)
+{
+	struct device_node *parent;
+	struct irq_domain *domain;
+
+	parent = of_irq_find_parent(hv_get_vmbus_root_device()->of_node);
+	domain = NULL;
+	if (parent) {
+		domain = irq_find_host(parent);
+		of_node_put(parent);
+	}
+
+	return domain;
+}
+

and later use it for `irq_create_hierarchy()`. Please let me know
if I missed anything in your question.

>> ---
>>   drivers/hv/vmbus_drv.c | 23 +++++++++++++++--------
>>   include/linux/hyperv.h |  2 ++
>>   2 files changed, 17 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
>> index c8474b48dcd2..7bfafe702963 100644
>> --- a/drivers/hv/vmbus_drv.c
>> +++ b/drivers/hv/vmbus_drv.c
>> @@ -45,7 +45,8 @@ struct vmbus_dynid {
>>          struct hv_vmbus_device_id id;
>>   };
>>
>> -static struct device  *hv_dev;
>> +/* VMBus Root Device */
>> +static struct device  *vmbus_root_device;
>>
>>   static int hyperv_cpuhp_online;
>>
>> @@ -80,9 +81,15 @@ static struct resource *fb_mmio;
>>   static struct resource *hyperv_mmio;
>>   static DEFINE_MUTEX(hyperv_mmio_lock);
>>
>> +struct device *hv_get_vmbus_root_device(void)
>> +{
>> +       return vmbus_root_device;
>> +}
>> +EXPORT_SYMBOL_GPL(hv_get_vmbus_root_device);
>> +
>>   static int vmbus_exists(void)
>>   {
>> -       if (hv_dev == NULL)
>> +       if (vmbus_root_device == NULL)
>>                  return -ENODEV;
>>
>>          return 0;
>> @@ -861,7 +868,7 @@ static int vmbus_dma_configure(struct device *child_device)
>>           * On x86/x64 coherence is assumed and these calls have no effect.
>>           */
>>          hv_setup_dma_ops(child_device,
>> -               device_get_dma_attr(hv_dev) == DEV_DMA_COHERENT);
>> +               device_get_dma_attr(vmbus_root_device) == DEV_DMA_COHERENT);
>>          return 0;
>>   }
>>
>> @@ -1930,7 +1937,7 @@ int vmbus_device_register(struct hv_device *child_device_obj)
>>                       &child_device_obj->channel->offermsg.offer.if_instance);
>>
>>          child_device_obj->device.bus = &hv_bus;
>> -       child_device_obj->device.parent = hv_dev;
>> +       child_device_obj->device.parent = vmbus_root_device;
>>          child_device_obj->device.release = vmbus_device_release;
>>
>>          child_device_obj->device.dma_parms = &child_device_obj->dma_parms;
>> @@ -2292,7 +2299,7 @@ static int vmbus_acpi_add(struct platform_device *pdev)
>>          struct acpi_device *ancestor;
>>          struct acpi_device *device = ACPI_COMPANION(&pdev->dev);
>>
>> -       hv_dev = &device->dev;
>> +       vmbus_root_device = &device->dev;
>>
>>          /*
>>           * Older versions of Hyper-V for ARM64 fail to include the _CCA
>> @@ -2383,7 +2390,7 @@ static int vmbus_device_add(struct platform_device *pdev)
>>          struct device_node *np = pdev->dev.of_node;
>>          int ret;
>>
>> -       hv_dev = &pdev->dev;
>> +       vmbus_root_device = &pdev->dev;
>>
>>          ret = of_range_parser_init(&parser, np);
>>          if (ret)
>> @@ -2702,7 +2709,7 @@ static int __init hv_acpi_init(void)
>>          if (ret)
>>                  return ret;
>>
>> -       if (!hv_dev) {
>> +       if (!vmbus_root_device) {
>>                  ret = -ENODEV;
>>                  goto cleanup;
>>          }
>> @@ -2733,7 +2740,7 @@ static int __init hv_acpi_init(void)
>>
>>   cleanup:
>>          platform_driver_unregister(&vmbus_platform_driver);
>> -       hv_dev = NULL;
>> +       vmbus_root_device = NULL;
>>          return ret;
>>   }
>>
>> diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
>> index 7f4f8d8bdf43..1f0851fde041 100644
>> --- a/include/linux/hyperv.h
>> +++ b/include/linux/hyperv.h
>> @@ -1333,6 +1333,8 @@ static inline void *hv_get_drvdata(struct hv_device *dev)
>>          return dev_get_drvdata(&dev->device);
>>   }
>>
>> +struct device *hv_get_vmbus_root_device(void);
>> +
>>   struct hv_ring_buffer_debug_info {
>>          u32 current_interrupt_mask;
>>          u32 current_read_index;
>> --
>> 2.43.0
>>
>>
> 
> 

-- 
Thank you,
Roman


  reply	other threads:[~2025-03-10 17:09 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 22:02 [PATCH hyperv-next v5 00/11] arm64: hyperv: Support Virtual Trust Level Boot Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 01/11] arm64: kvm, smccc: Introduce and use API for detectting hypervisor presence Roman Kisel
2025-03-08 21:08   ` Arnd Bergmann
2025-03-10 21:16   ` Michael Kelley
2025-03-10 21:54     ` Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 02/11] arm64: hyperv: Use SMCCC to detect " Roman Kisel
2025-03-10 21:17   ` Michael Kelley
2025-03-07 22:02 ` [PATCH hyperv-next v5 03/11] Drivers: hv: Enable VTL mode for arm64 Roman Kisel
2025-03-08 21:05   ` Arnd Bergmann
2025-03-10 17:35     ` Roman Kisel
2025-03-10 21:01     ` Michael Kelley
2025-03-10 21:20       ` Arnd Bergmann
2025-03-10 22:18         ` Michael Kelley
2025-03-12 18:33           ` Roman Kisel
2025-03-12 20:25             ` Arnd Bergmann
2025-03-12 21:21               ` Roman Kisel
2025-03-13  5:10                 ` Michael Kelley
2025-03-12 20:31             ` Wei Liu
2025-03-12 21:30               ` Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 04/11] Drivers: hv: Provide arch-neutral implementation of get_vtl() Roman Kisel
2025-03-10 13:44   ` Tianyu Lan
2025-03-07 22:02 ` [PATCH hyperv-next v5 05/11] arm64: hyperv: Initialize the Virtual Trust Level field Roman Kisel
2025-03-10 23:07   ` Michael Kelley
2025-03-07 22:02 ` [PATCH hyperv-next v5 06/11] arm64, x86: hyperv: Report the VTL the system boots in Roman Kisel
2025-03-10  0:31   ` Wei Liu
2025-03-10 16:42     ` Roman Kisel
2025-03-10 16:53       ` Wei Liu
2025-03-10 17:20         ` Roman Kisel
2025-03-07 22:02 ` [PATCH hyperv-next v5 07/11] dt-bindings: microsoft,vmbus: Add interrupts and DMA coherence Roman Kisel
2025-03-10  9:28   ` Krzysztof Kozlowski
2025-03-10 17:05     ` Roman Kisel
2025-03-10 17:40       ` Krzysztof Kozlowski
2025-03-10 18:07         ` Roman Kisel
2025-03-10 21:17           ` Krzysztof Kozlowski
2025-03-10 21:51             ` Roman Kisel
2025-03-07 22:03 ` [PATCH hyperv-next v5 08/11] Drivers: hv: vmbus: Get the IRQ number from DeviceTree Roman Kisel
2025-03-08 21:11   ` Arnd Bergmann
2025-03-10 17:36     ` Roman Kisel
2025-03-10 23:09   ` Michael Kelley
2025-03-13 18:44   ` Rob Herring
2025-03-13 18:46     ` Roman Kisel
2025-03-07 22:03 ` [PATCH hyperv-next v5 09/11] Drivers: hv: vmbus: Introduce hv_get_vmbus_root_device() Roman Kisel
2025-03-10 13:41   ` Tianyu Lan
2025-03-10 17:09     ` Roman Kisel [this message]
2025-03-10 23:12   ` Michael Kelley
2025-03-07 22:03 ` [PATCH hyperv-next v5 10/11] ACPI: irq: Introduce acpi_get_gsi_dispatcher() Roman Kisel
2025-03-10 23:26   ` Michael Kelley
2025-03-07 22:03 ` [PATCH hyperv-next v5 11/11] PCI: hv: Get vPCI MSI IRQ domain from DeviceTree Roman Kisel
2025-03-10 16:41   ` Bjorn Helgaas
2025-03-10 17:15     ` Roman Kisel
2025-03-10 23:42   ` Michael Kelley

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=e3414583-0437-4fc4-b464-1426e5fe9628@linux.microsoft.com \
    --to=romank@linux.microsoft.com \
    --cc=apais@microsoft.com \
    --cc=arnd@arndb.de \
    --cc=benhill@microsoft.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=bperkins@microsoft.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=devicetree@vger.kernel.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=joey.gouly@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=kw@linux.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=ltykernel@gmail.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oliver.upton@linux.dev \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=ssengar@linux.microsoft.com \
    --cc=sudeep.holla@arm.com \
    --cc=sunilmut@microsoft.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@kernel.org \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yuzenghui@huawei.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