All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
To: Drew Fustini <fustini@kernel.org>, Sunil V L <sunilvl@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Weiwei Li <liwei1518@gmail.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	Chao Liu <chao.liu@processmission.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Anup Patel <anup.patel@oss.qualcomm.com>,
	Prajwal N <prajwal.n@oss.qualcomm.com>,
	Shankar C <shankar.c@oss.qualcomm.com>,
	Jinjie Ruan <2118537295@qq.com>,
	ruanjinjie@huawei.com
Subject: Re: [PATCH v2 0/4] RISC-V: ACPI: Add PPTT support
Date: Tue, 20 Oct 2026 21:39:19 -0300	[thread overview]
Message-ID: <9c468ae3-e303-40da-bbc8-a22a82b9bc97@oss.qualcomm.com> (raw)
In-Reply-To: <atfrQY1w-er0onXV@thelio>

Hi Drew!

On 10/20/2026 7:29 PM, Drew Fustini wrote:
> On Thu, Oct 15, 2026 at 12:19:53PM +0530, Sunil V L wrote:
>> Hi all,
>>
>> This series adds ACPI Processor Properties Topology Table (PPTT) support to
>> the RISC-V virt machine. PPTT allows the guest to discover the processor and
>> cache topology exposed by the machine, which is useful for making better
>> scheduling and cache-management decisions.
> 
> Thanks for picking up PPTT support. I can now rebase the RQSC support
> [1] on this series.
> 
> However, RQSC actually needs PPTT revision 3, because it adds cache IDs
> to the PPTT. The RQSC table references a capacity controller's cache by
> the PPTT cache ID. In Linux, find_acpi_cache_level_from_id() and
> acpi_pptt_get_cpumask_from_cache_id() return -ENOENT if PPTT rev < 3.
> 
> There is a new MPAM series by Jinjie Ruan which contains the patch
> "[PATCH 04/37] hw/acpi: Build PPTT rev 3 with cache IDs for MPAM
> cross-references" [2]. It bumps build_pptt() to revision 3 and gives
> every cache node an ID.
> 
> I could just base the RQSC series on this PPTT series and that patch
> 03/37. But maybe there is a better way to coordinate adding PPTT v3?

This PPTT support is acked and I believe we'll queue it in riscv-to-apply.next
shortly.

As for the PPTT rev3 patch in the "Add Arm MPAM emulation", my suggestion is
to put that on top of your series (i.e. your series will contain that patch).
That ARM series has 37 patches and might take awhile to go through, and your
work relies only on patch 04 ...  which happens to be an arch agnostic patch.
I believe it's fine for us to push it via the riscv queue.

I see that the author from the ARM series is CCed here.  Jinjie Ruan, are you
okay with us pushing your patch via the RISC-V tree?  It'll unblock Drew's work
and you'll have one less patch to worry about in your ARM MPAM work.


Thanks,
Daniel





> 
> Thanks,
> Drew
> 
> [1] https://lore.kernel.org/all/20260202-riscv-rqsc-v1-0-dcf448a3ed73@kernel.org/
> [2] https://lore.kernel.org/all/tencent_F9C68A515AC6C40BE2C32DB314E14CCB7106@qq.com/



  reply	other threads:[~2026-10-21  0:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  6:49 [PATCH v2 0/4] RISC-V: ACPI: Add PPTT support Sunil V L
2026-10-15  6:49 ` [PATCH v2 1/4] tests/qtest/bios-tables-test: Allow PPTT for RISC-V Sunil V L
2026-10-15  6:49 ` [PATCH v2 2/4] hw/riscv/virt: Add ACPI PPTT table Sunil V L
2026-10-15 16:56   ` Daniel Henrique Barboza
2026-10-15  6:49 ` [PATCH v2 3/4] tests/qtest/bios-tables-test: Update riscv64 virt PPTT golden reference Sunil V L
2026-10-15  6:49 ` [PATCH v2 4/4] MAINTAINERS: Update Sunil's email id Sunil V L
2026-10-20 22:29 ` [PATCH v2 0/4] RISC-V: ACPI: Add PPTT support Drew Fustini
2026-10-21  0:39   ` Daniel Henrique Barboza [this message]
2026-10-21  1:14     ` Jinjie Ruan

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=9c468ae3-e303-40da-bbc8-a22a82b9bc97@oss.qualcomm.com \
    --to=daniel.barboza@oss.qualcomm.com \
    --cc=2118537295@qq.com \
    --cc=alistair.francis@wdc.com \
    --cc=anisinha@redhat.com \
    --cc=anup.patel@oss.qualcomm.com \
    --cc=chao.liu@processmission.com \
    --cc=fustini@kernel.org \
    --cc=imammedo@redhat.com \
    --cc=liwei1518@gmail.com \
    --cc=mst@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=prajwal.n@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=ruanjinjie@huawei.com \
    --cc=shankar.c@oss.qualcomm.com \
    --cc=sunilvl@oss.qualcomm.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.