From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Yicong Yang <yangyicong@huawei.com>,
Alireza Sanaee <alireza.sanaee@huawei.com>,
<yangyicong@hisilicon.com>, <qemu-devel@nongnu.org>,
<anisinha@redhat.com>, <imammedo@redhat.com>,
<linuxarm@huawei.com>, <peter.maydell@linaro.org>,
<prime.zeng@hisilicon.com>,
<shameerali.kolothum.thodi@huawei.com>, <wangyanan55@huawei.com>
Subject: Re: [PATCH v3 4/5] hw/acpi/aml-build: Update the revision of PPTT table
Date: Wed, 23 Apr 2025 16:47:20 +0100 [thread overview]
Message-ID: <20250423164720.000070b9@huawei.com> (raw)
In-Reply-To: <20250423113447-mutt-send-email-mst@kernel.org>
On Wed, 23 Apr 2025 11:35:46 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Apr 23, 2025 at 10:15:42PM +0800, Yicong Yang wrote:
> > On 2025/4/23 20:39, Michael S. Tsirkin wrote:
> > > On Wed, Apr 23, 2025 at 12:41:29PM +0100, Alireza Sanaee wrote:
> > >> From: Yicong Yang <yangyicong@hisilicon.com>
> > >>
> > >> The lastest ACPI spec 6.5 support PPTT revision 3. Update it
> > >> by handy. This is compatible with previous revision.
> > >>
> > >> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> > >> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > >> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
> > >
> > >
> > > I don't get it. Why are you updating it? Which features
> > > from the new one are you using?
> > >
> >
> > no new features for this patchset. considered updating it to the latest ACPI
> > spec since we're going to touch the PPTT table and tested data.
>
> it's best to wait until there are actual features you need.
> don't make changes for the sake of changes, there's always
> some risk.
Once we add the cache description (Ali's other set) can we make
sure we arbitrary decide to have separate cache structures. The
earlier table version allowed sharing of the entrees in the table
which then became not allowed in the newer spec. That will smooth
the path quite a bit and is a valid way to interpret the earlier spec.
If we do that, we can bring the IDs + the version update as a
precursor to MPAM support series. I don't think we need them until
that series (which is a way off being ready to merge yet!)
Jonathan
>
> > >> ---
> > >> hw/acpi/aml-build.c | 2 +-
> > >> 1 file changed, 1 insertion(+), 1 deletion(-)
> > >>
> > >> diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
> > >> index 3010325ca423..e5401dfdb1a8 100644
> > >> --- a/hw/acpi/aml-build.c
> > >> +++ b/hw/acpi/aml-build.c
> > >> @@ -2155,7 +2155,7 @@ void build_pptt(GArray *table_data, BIOSLinker *linker, MachineState *ms,
> > >> uint32_t pptt_start = table_data->len;
> > >> uint32_t root_offset;
> > >> int n;
> > >> - AcpiTable table = { .sig = "PPTT", .rev = 2,
> > >> + AcpiTable table = { .sig = "PPTT", .rev = 3,
> > >> .oem_id = oem_id, .oem_table_id = oem_table_id };
> > >>
> > >> acpi_table_begin(&table, table_data);
> > >> --
> > >> 2.34.1
> > >
> > >
> > > .
> > >
>
>
next prev parent reply other threads:[~2025-04-23 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 11:41 [PATCH v3 0/5] Building PPTT with root node and identical implementation flag Alireza Sanaee via
2025-04-23 11:41 ` [PATCH v3 1/5] tests: virt: Allow changes to PPTT test table Alireza Sanaee via
2025-04-23 11:41 ` [PATCH v3 2/5] hw/acpi/aml-build: Set identical implementation flag for PPTT processor nodes Alireza Sanaee via
2025-04-23 11:41 ` [PATCH v3 3/5] hw/acpi/aml-build: Build a root node in the PPTT table Alireza Sanaee via
2025-04-23 12:41 ` Michael S. Tsirkin
2025-04-23 13:51 ` Yicong Yang via
2025-04-23 11:41 ` [PATCH v3 4/5] hw/acpi/aml-build: Update the revision of " Alireza Sanaee via
2025-04-23 12:39 ` Michael S. Tsirkin
2025-04-23 14:15 ` Yicong Yang via
2025-04-23 15:35 ` Michael S. Tsirkin
2025-04-23 15:47 ` Jonathan Cameron via [this message]
2025-04-23 15:51 ` Michael S. Tsirkin
2025-04-28 11:20 ` Alireza Sanaee via
2025-04-23 11:41 ` [PATCH v3 5/5] tests: virt: Update expected ACPI tables for virt test Alireza Sanaee via
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=20250423164720.000070b9@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alireza.sanaee@huawei.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=prime.zeng@hisilicon.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=wangyanan55@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@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;
as well as URLs for NNTP newsgroup(s).