[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/2] hw/intc/arm_gicv3: Make ITT entry size configurable
From: |
Joelle van Dyne |
Subject: |
Re: [PATCH 1/2] hw/intc/arm_gicv3: Make ITT entry size configurable |
Date: |
Thu, 9 Mar 2023 20:55:55 -0800 |
On Fri, Dec 23, 2022 at 12:50 AM Alexander Graf <agraf@csgraf.de> wrote:
>
> An ITT entry is opaque to the OS. The only thing it does get told by HW is
> its size. In theory, that size can be any byte aligned number, in practice
> HW will always use power of 2s to simplify offset calculation. We currently
> expose the size as 12, which is not a power of 2.
>
> To prepare for a future where we expose power of 2 sized entry sizes, let's
> make the size itself configurable. We only need to watch out that we don't
> have an entry be smaller than the fields we want to access inside. Bigger
> is always fine.
>
> Signed-off-by: Alexander Graf <agraf@csgraf.de>
> ---
Tested-by: Joelle van Dyne <j@getutm.app>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [PATCH 1/2] hw/intc/arm_gicv3: Make ITT entry size configurable,
Joelle van Dyne <=