qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, mst@redhat.com,
	qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hw/acpi: fix GSI links UID
Date: Mon, 14 Mar 2016 10:43:57 +0100	[thread overview]
Message-ID: <20160314104357.6a7fc878@nial.brq.redhat.com> (raw)
In-Reply-To: <1457869229-9989-1-git-send-email-marcel@redhat.com>

On Sun, 13 Mar 2016 13:40:29 +0200
Marcel Apfelbaum <marcel@redhat.com> wrote:

> According to the ACPI spec, each UID must be unique.
> Use the irq number as UID for GSI links.
> 
> Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
> ---
> 
> Hi,
> 
> This patch was tested with Windows XP/2003/2012R2/7/10 and Fedora.
tested it with RHEL6/7

Reviewed-by: Igor Mammedov <imammedo@redhat.com>


> 
> Thanks,
> Marcel
>     
>  hw/i386/acpi-build.c | 20 ++++++++------------
>  1 file changed, 8 insertions(+), 12 deletions(-)
> 
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index adbf354..83e031d 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -1748,18 +1748,14 @@ static void build_q35_pci0_int(Aml *table)
>      aml_append(sb_scope, build_link_dev("LNKG", 6, aml_name("PRQG")));
>      aml_append(sb_scope, build_link_dev("LNKH", 7, aml_name("PRQH")));
>  
> -    /*
> -     * TODO: UID probably shouldn't be the same for GSIx devices
> -     * but that's how it was in original ASL so keep it for now
> -     */
> -    aml_append(sb_scope, build_gsi_link_dev("GSIA", 0, 0x10));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIB", 0, 0x11));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIC", 0, 0x12));
> -    aml_append(sb_scope, build_gsi_link_dev("GSID", 0, 0x13));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIE", 0, 0x14));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIF", 0, 0x15));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIG", 0, 0x16));
> -    aml_append(sb_scope, build_gsi_link_dev("GSIH", 0, 0x17));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIA", 0x10, 0x10));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIB", 0x11, 0x11));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIC", 0x12, 0x12));
> +    aml_append(sb_scope, build_gsi_link_dev("GSID", 0x13, 0x13));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIE", 0x14, 0x14));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIF", 0x15, 0x15));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIG", 0x16, 0x16));
> +    aml_append(sb_scope, build_gsi_link_dev("GSIH", 0x17, 0x17));
>  
>      aml_append(table, sb_scope);
>  }

  reply	other threads:[~2016-03-14  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13 11:40 [Qemu-devel] [PATCH] hw/acpi: fix GSI links UID Marcel Apfelbaum
2016-03-14  9:43 ` Igor Mammedov [this message]
2016-03-15 17:27 ` Paolo Bonzini
2016-03-16 12:17   ` Marcel Apfelbaum
2016-03-16 14:03     ` Michael S. Tsirkin

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=20160314104357.6a7fc878@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).