Hi Yang, On 2024/3/12 19:46, Yang Xiwen wrote: > On 3/12/2024 7:33 PM, Wei Xu wrote: >> Hi Yang, >> >> On 2024/3/12 19:19, Yang Xiwen wrote: >>> On 2/19/2024 11:05 PM, Yang Xiwen via B4 Relay wrote: >>>> The patchset fixes some warnings reported by the kernel during boot. >>>> >>>> The cache size info is from Processor_Datasheet_v2XX.pdf [1], Section >>>> 2.2.1 Master Processor. >>>> >>>> The cache line size and the set-associative info are from Cortex-A53 >>>> Documentation [2]. >>>> >>>> From the doc, it can be concluded that L1 i-cache is 4-way assoc, L1 >>>> d-cache is 2-way assoc and L2 cache is 16-way assoc. Calculate the dts >>>> props accordingly. >>>> >>>> Also, to use KVM's VGIC code, GICH, GICV registers spaces and maintenance >>>> IRQ are added to the dts with verification. >>>> >>>> [1]: https://github.com/96boards/documentation/blob/master/enterprise/poplar/hardware-docs/Processor_Datasheet_v2XX.pdf >>>> [2]: https://developer.arm.com/documentation/ddi0500/j/Level-1-Memory-System >>>> >>>> Signed-off-by: Yang Xiwen <forbidden405@xxxxxxxxxxx> >>>> --- >>>> Changes in v3: >>>> - send patches to stable (Andrew Lunn) >>>> - rewrite the commit logs more formally (Andrew Lunn) >>>> - rename l2-cache0 to l2-cache (Krzysztof Kozlowski) >>>> - Link to v2: https://lore.kernel.org/r/20240218-cache-v2-0-1fd919e2bd3e@xxxxxxxxxxx >>>> >>>> Changes in v2: >>>> - arm64: dts: hi3798cv200: add GICH, GICV register spces and >>>> maintainance IRQ. >>>> - Link to v1: https://lore.kernel.org/r/20240218-cache-v1-0-2c0a8a4472e7@xxxxxxxxxxx >>>> >>>> --- >>>> Yang Xiwen (3): >>>> arm64: dts: hi3798cv200: fix the size of GICR >>>> arm64: dts: hi3798cv200: add GICH, GICV register space and irq >>>> arm64: dts: hi3798cv200: add cache info >>>> >>>> arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 43 +++++++++++++++++++++++++- >>>> 1 file changed, 42 insertions(+), 1 deletion(-) >>>> --- >>>> base-commit: 8d3dea210042f54b952b481838c1e7dfc4ec751d >>>> change-id: 20240218-cache-11c8bf7566c2 >>>> >>>> Best regards, >>> May someone apply this patchset to their tree so that it can land in stable at the end? This is a fix, not adding new functionalities. It's been 2 weeks already. >>> >> Sorry for the delay, I am too busy to catch up with this cycle. >> I will go through this patch set and maybe apply it during the next cycle. > > > No problem. I'm just a bit worried if this patch is getting lost. It's good to know it's still maintained. Because i've seen some maintainers not reviewing any patches for over 1 year already, with their names and emails still in MAINTAINERS. Thanks for the understanding! > > > By the way, I think fixes and new features are in different cycles? Most maintainers seem to have multiple branches to handle this. Yes, they can be in different cycle. But now is the merge window. Best Regards, Wei > > >> >> Best Regards, >> Wei > >
