From: Sunil V L <sunilvl@ventanamicro.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
qemu-riscv@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <anisinha@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Sia Jee Heng" <jeeheng.sia@starfivetech.com>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Bin Meng" <bmeng.cn@gmail.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Alistair Francis" <alistair.francis@wdc.com>
Subject: Re: [PATCH v4 16/16] tests/qtest/bios-tables-test: Add expected ACPI data files for RISC-V
Date: Mon, 8 Jul 2024 09:56:14 +0530 [thread overview]
Message-ID: <ZotqZsO2QdPG4tsg@sunil-laptop> (raw)
In-Reply-To: <CAKmqyKPMW0WMJQn7=2ebuqf0c=ow87LCtPd1bOdiWVP_xjoTJA@mail.gmail.com>
On Mon, Jul 08, 2024 at 01:16:49PM +1000, Alistair Francis wrote:
> On Thu, Jul 4, 2024 at 12:57 AM Sunil V L <sunilvl@ventanamicro.com> wrote:
> >
> > On Wed, Jul 03, 2024 at 03:53:08PM +0530, Sunil V L wrote:
> > > On Tue, Jul 02, 2024 at 03:02:36PM +0100, Jonathan Cameron wrote:
> > > > On Mon, 1 Jul 2024 17:03:43 -0400
> > > > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > > >
> > > > > On Thu, Jun 27, 2024 at 02:18:03PM +0200, Igor Mammedov wrote:
> > > > > > On Tue, 25 Jun 2024 20:38:39 +0530
> > > > > > Sunil V L <sunilvl@ventanamicro.com> wrote:
> > > > > >
> > > > > > > As per the step 5 in the process documented in bios-tables-test.c,
> > > > > > > generate the expected ACPI AML data files for RISC-V using the
> > > > > > > rebuild-expected-aml.sh script and update the
> > > > > > > bios-tables-test-allowed-diff.h.
> > > > > > >
> > > > > > > These are all new files being added for the first time. Hence, iASL diff
> > > > > > > output is not added.
> > > > > > >
> > > > > > > Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
> > > > > > > Acked-by: Alistair Francis <alistair.francis@wdc.com>
> > > > > > > Acked-by: Igor Mammedov <imammedo@redhat.com>
> > > > > >
> > > > > > Michael,
> > > > > > can it go via risc-v tree or
> > > > > > do you plan to merge it via your tree?
> > > > >
> > > > > given patch 1 is merged, I took the rest.
> > > >
> > > > Looks like your CI runs are catching this as well but
> > > > RHCT here is failing. I rebased the GI/GP set on top of this
> > > > and ignored that failure by skipping riscv64 tests.
> > > >
> > > > Jonathan
> > > >
> > > Hi Jonathan, Michael,
> > >
> > > Looks like a recent RISC-V PR updated the rva22s64 ISA string affecting
> > > the RHCT I had in my series. I see that Michael dropped those 3 RISC-V
> > > patches from the PR. So, let me update the expected RHCT AML file in a
> > > new series. I will also include Igor's feedback to remove fallback path
> > > in that series.
> > >
> > Hi Alistair,
> >
> > This issue is because, below 3 extensions are present in the ISA string
> > for rva22s64 profile cpu after recent RISC-V PR.
> >
> > zmmul_zaamo_zalrsc
>
> zmmul (multiply) is implied by M (multiply and divide). The other two
> are similar.
>
> >
> > However, IIUC, they are not mentioned in the RVA22S64 profile spec. Because of
> > this change, my AML files are having a difference and failing CI. The
> > question is, is this correct behavior? If so, I can update the AML files
> > and resubmit the patches. Let me know.
>
> This does feel correct. Is software only needed zmmul for multiplying
> then reporting zmmul when we support M feels like the right thing to
> do.
>
> I can't find a spec that says either way though. So unless anyone else
> knows of one I think this current approach is correct
>
Thanks a lot, Alistair. I had a discussion with Daniel as well and we
concluded the same. I will update the AML files.
Thanks,
Sunil
prev parent reply other threads:[~2024-07-08 4:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 15:08 [PATCH v4 00/16] Add support for RISC-V ACPI tests Sunil V L
2024-06-25 15:08 ` [PATCH v4 01/16] hw/riscv/virt.c: Make block devices default to virtio Sunil V L
2024-06-25 15:08 ` [PATCH v4 02/16] uefi-test-tools/UefiTestToolsPkg: Add RISC-V support Sunil V L
2024-06-25 15:08 ` [PATCH v4 03/16] uefi-test-tools: Add support for python based build script Sunil V L
2024-06-25 15:08 ` [PATCH v4 04/16] tests/data/uefi-boot-images: Add RISC-V ISO image Sunil V L
2024-06-25 15:08 ` [PATCH v4 05/16] qtest: bios-tables-test: Rename aarch64 tests with aarch64 in them Sunil V L
2024-06-25 15:08 ` [PATCH v4 06/16] tests/qtest/bios-tables-test.c: Add support for arch in path Sunil V L
2024-07-02 8:30 ` Igor Mammedov
2024-07-02 8:33 ` Sunil V L
2024-06-25 15:08 ` [PATCH v4 07/16] tests/qtest/bios-tables-test.c: Set "arch" for aarch64 tests Sunil V L
2024-06-25 15:08 ` [PATCH v4 08/16] tests/qtest/bios-tables-test.c: Set "arch" for x86 tests Sunil V L
2024-06-25 15:08 ` [PATCH v4 09/16] tests/data/acpi: Move x86 ACPI tables under x86/${machine} path Sunil V L
2024-06-25 15:08 ` [PATCH v4 10/16] tests/data/acpi/virt: Move ARM64 ACPI tables under aarch64/${machine} path Sunil V L
2024-06-25 15:08 ` [PATCH v4 11/16] meson.build: Add RISC-V to the edk2-target list Sunil V L
2024-06-25 15:08 ` [PATCH v4 12/16] pc-bios/meson.build: Add support for RISC-V in unpack_edk2_blobs Sunil V L
2024-06-25 15:08 ` [PATCH v4 13/16] tests/data/acpi/rebuild-expected-aml.sh: Add RISC-V Sunil V L
2024-06-25 15:08 ` [PATCH v4 14/16] tests/qtest/bios-tables-test: Add empty ACPI data files for RISC-V Sunil V L
2024-06-25 15:08 ` [PATCH v4 15/16] tests/qtest/bios-tables-test.c: Enable basic testing " Sunil V L
2024-06-25 15:08 ` [PATCH v4 16/16] tests/qtest/bios-tables-test: Add expected ACPI data files " Sunil V L
2024-06-27 12:18 ` Igor Mammedov
2024-07-01 21:03 ` Michael S. Tsirkin
2024-07-02 14:02 ` Jonathan Cameron via
2024-07-02 14:02 ` Jonathan Cameron via
2024-07-03 10:22 ` Sunil V L
2024-07-03 14:57 ` Sunil V L
2024-07-08 3:16 ` Alistair Francis
2024-07-08 4:26 ` Sunil V L [this message]
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=ZotqZsO2QdPG4tsg@sunil-laptop \
--to=sunilvl@ventanamicro.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=anisinha@redhat.com \
--cc=berrange@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=imammedo@redhat.com \
--cc=jeeheng.sia@starfivetech.com \
--cc=kraxel@redhat.com \
--cc=liwei1518@gmail.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=thuth@redhat.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.