|
From: | Richard Henderson |
Subject: | Re: [PATCH 0/2] target/arm: Look up ARMCPRegInfo at runtime |
Date: | Tue, 17 Jan 2023 05:20:49 -1000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
On 1/17/23 00:28, Peter Maydell wrote:
On Mon, 16 Jan 2023 at 20:16, Richard Henderson <richard.henderson@linaro.org> wrote:Ping.What did you think of my suggestion in the other thread of hashing the info we need to determine the cpreg set (ID regs, feature flags, etc) and using that to look up whether we've already created a cpreg hashtable for this config? If we did that, we could refcount the cpreg hashtable and only free it when all CPUs are done with it, which would mean we don't need this indirection.
I thought it a decent idea, but not small.While we currently have a struct for some isar regs, we'd want a larger struct containing every bit of info that wants hashing. I think it would take 40-50 patches to get all of the properties etc moved out of ARMCPU and CPUARMState.
Anyway, I didn't want to leave the user-only thread leak blocked in the meantime. r~
[Prev in Thread] | Current Thread | [Next in Thread] |