From: Igor Mammedov <imammedo@redhat.com>
To: Jon Doron <arilou@gmail.com>
Cc: rvkagan@yandex-team.ru, pbonzini@redhat.com, vkuznets@redhat.com,
mail@maciej.szmigiero.name, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/3] hyperv: vmbus: Remove the 2nd IRQ
Date: Tue, 23 Jun 2020 16:58:22 +0200 [thread overview]
Message-ID: <20200623165822.2fd73965@redhat.com> (raw)
In-Reply-To: <20200618030027.759594-2-arilou@gmail.com>
On Thu, 18 Jun 2020 06:00:25 +0300
Jon Doron <arilou@gmail.com> wrote:
> It seems like Windows does not really require 2 IRQs to have a
> functioning VMBus.
>
> Signed-off-by: Jon Doron <arilou@gmail.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/hyperv/vmbus.c | 3 +--
> hw/i386/acpi-build.c | 4 +---
> include/hw/hyperv/vmbus-bridge.h | 3 +--
> 3 files changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/hw/hyperv/vmbus.c b/hw/hyperv/vmbus.c
> index f371240176..a8bcb41026 100644
> --- a/hw/hyperv/vmbus.c
> +++ b/hw/hyperv/vmbus.c
> @@ -2741,8 +2741,7 @@ static const VMStateDescription vmstate_vmbus_bridge = {
> };
>
> static Property vmbus_bridge_props[] = {
> - DEFINE_PROP_UINT8("irq0", VMBusBridge, irq0, 7),
> - DEFINE_PROP_UINT8("irq1", VMBusBridge, irq1, 13),
> + DEFINE_PROP_UINT8("irq", VMBusBridge, irq, 7),
> DEFINE_PROP_END_OF_LIST()
> };
>
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index 900f786d08..91af0d2d0d 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -1082,9 +1082,7 @@ static Aml *build_vmbus_device_aml(VMBusBridge *vmbus_bridge)
> aml_append(dev, aml_name_decl("_PS3", aml_int(0x0)));
>
> crs = aml_resource_template();
> - aml_append(crs, aml_irq_no_flags(vmbus_bridge->irq0));
> - /* FIXME: newer HyperV gets by with only one IRQ */
> - aml_append(crs, aml_irq_no_flags(vmbus_bridge->irq1));
> + aml_append(crs, aml_irq_no_flags(vmbus_bridge->irq));
> aml_append(dev, aml_name_decl("_CRS", crs));
>
> return dev;
> diff --git a/include/hw/hyperv/vmbus-bridge.h b/include/hw/hyperv/vmbus-bridge.h
> index c0a06d832c..33f93de64d 100644
> --- a/include/hw/hyperv/vmbus-bridge.h
> +++ b/include/hw/hyperv/vmbus-bridge.h
> @@ -19,8 +19,7 @@ typedef struct VMBus VMBus;
> typedef struct VMBusBridge {
> SysBusDevice parent_obj;
>
> - uint8_t irq0;
> - uint8_t irq1;
> + uint8_t irq;
>
> VMBus *bus;
> } VMBusBridge;
next prev parent reply other threads:[~2020-06-23 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 3:00 [PATCH v3 0/3] hyperv: vmbus: ACPI various corrections Jon Doron
2020-06-18 3:00 ` [PATCH v3 1/3] hyperv: vmbus: Remove the 2nd IRQ Jon Doron
2020-06-23 14:58 ` Igor Mammedov [this message]
2020-06-18 3:00 ` [PATCH v3 2/3] i386: acpi: vmbus: Add _ADR definition Jon Doron
2020-06-23 15:06 ` Igor Mammedov
2020-06-25 2:23 ` Jon Doron
2020-06-18 3:00 ` [PATCH v3 3/3] acpi: i386: Move VMBus DSDT entry to SB Jon Doron
2020-06-23 15:09 ` Igor Mammedov
2020-06-25 2:25 ` Jon Doron
2020-06-25 4:46 ` Jon Doron
2020-06-25 18:39 ` Igor Mammedov
2020-06-18 3:23 ` [PATCH v3 0/3] hyperv: vmbus: ACPI various corrections no-reply
2020-06-23 15:11 ` Igor Mammedov
2020-06-23 15:45 ` Paolo Bonzini
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=20200623165822.2fd73965@redhat.com \
--to=imammedo@redhat.com \
--cc=arilou@gmail.com \
--cc=mail@maciej.szmigiero.name \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rvkagan@yandex-team.ru \
--cc=vkuznets@redhat.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).