On Wed, Apr 19, 2023 at 1:38 PM Ley Foon Tan <lftan@xxxxxxxxxx> wrote: > > On Thu, Apr 6, 2023 at 10:45 AM Atish Kumar Patra <atishp@xxxxxxxxxxxx> wrote: > > > > > > > > > > > Hi Sunil > > > > > > > > One question regarding PMU in ACPI flow. > > > > > > > > We use DT to decode the supported HPM counters/events for the > > > > different platforms now. > > > > How do we enable PMU (drivers/perf/riscv_pmu_sbi.c) when using ACPI method? > > > > Note, this might be in separate patch series. > > > > > > > Hi Lay Foon, > > > > > > This driver uses SBI calls and hence should work in case of ACPI also. > > > > > > There is one minor change required in this driver for overflow > > > interrupt. I have a patch for that in future series. > > > > Just to add further clarification: OpenSBI will continue to use the > > device tree so that > > the firmware will have access to all the PMU details. > > > Sorry for the late reply, missed out on this email in my kernel.org mailbox. > > Do you mean OpenSBI still using the device tree, but EDK II and Linux > using the ACPI table? Normally Linux shouldn't mix between ACPI and Yes. For Linux, it will only be ACPI. Otherwise, we have to define all those bindings in ACPI as well. In the future, we will have supervisor counter delegation ISA extension(in progress) that allows the kernel to directly program the hpmevents & modify counters without needing SBI PMU extension. > device tree. > > Regards > Ley Foon > > _______________________________________________ > linux-riscv mailing list > linux-riscv@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-riscv -- Regards, Atish
