All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Weiwei Li <liwei1518@gmail.com>,
	Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Andrew Jones <ajones@ventanamicro.com>,
	Anup Patel <anup@brainfault.org>,
	Atish Kumar Patra <atishp@rivosinc.com>
Subject: Re: [PATCH 2/3] hw/riscv/virt-acpi-build.c: Update FADT and MADT versions
Date: Wed, 16 Jul 2025 12:34:14 -0400	[thread overview]
Message-ID: <20250716123314-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250716144140.3954431-3-sunilvl@ventanamicro.com>

On Wed, Jul 16, 2025 at 08:11:39PM +0530, Sunil V L wrote:
> RISC-V support is added only in ACPI 6.6. According to the ACPI 6.6
> specification, the minor version of the Fixed ACPI Description Table
> (FADT) should be 6, and the Multiple APIC Description Table (MADT)
> should use revision 7. So, update the RISC-V FADT and MADT to reflect
> correct versions.
> 
> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
> ---
>  hw/riscv/virt-acpi-build.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/riscv/virt-acpi-build.c b/hw/riscv/virt-acpi-build.c
> index ee1416d264..d7e57cbb1f 100644
> --- a/hw/riscv/virt-acpi-build.c
> +++ b/hw/riscv/virt-acpi-build.c
> @@ -429,7 +429,7 @@ static void build_fadt_rev6(GArray *table_data,
>  {
>      AcpiFadtData fadt = {
>          .rev = 6,
> -        .minor_ver = 5,
> +        .minor_ver = 6,
>          .flags = 1 << ACPI_FADT_F_HW_REDUCED_ACPI,
>          .xdsdt_tbl_offset = &dsdt_tbl_offset,
>      };
> @@ -537,7 +537,7 @@ static void build_madt(GArray *table_data,
>  
>      hart_index_bits = imsic_num_bits(imsic_max_hart_per_socket);
>  
> -    AcpiTable table = { .sig = "APIC", .rev = 6, .oem_id = s->oem_id,
> +    AcpiTable table = { .sig = "APIC", .rev = 7, .oem_id = s->oem_id,
>                          .oem_table_id = s->oem_table_id };

Add comments citing the spec version and chapter.


>      acpi_table_begin(&table, table_data);
> -- 
> 2.43.0



  reply	other threads:[~2025-07-16 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 14:41 [PATCH 0/3] RISC-V: ACPI: Update FADT and MADT versions Sunil V L
2025-07-16 14:41 ` [PATCH 1/3] bios-tables-test-allowed-diff.h: Allow RISC-V FADT and MADT changes Sunil V L
2025-07-16 14:41 ` [PATCH 2/3] hw/riscv/virt-acpi-build.c: Update FADT and MADT versions Sunil V L
2025-07-16 16:34   ` Michael S. Tsirkin [this message]
2025-07-16 14:41 ` [PATCH 3/3] tests/data/acpi/riscv64: Update expected FADT and MADT Sunil V L
2025-07-24  7:45 ` [PATCH 0/3] RISC-V: ACPI: Update FADT and MADT versions 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=20250716123314-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ajones@ventanamicro.com \
    --cc=alistair.francis@wdc.com \
    --cc=anisinha@redhat.com \
    --cc=anup@brainfault.org \
    --cc=atishp@rivosinc.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=imammedo@redhat.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sunilvl@ventanamicro.com \
    --cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.