|
From: | Richard Henderson |
Subject: | Re: [PATCH 16/22] target/arm: Extract verify_accel_features() from cpu_realize() |
Date: | Fri, 29 Sep 2023 14:25:34 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 |
On 9/18/23 09:02, Philippe Mathieu-Daudé wrote:
When looking at the arm_cpu_realizefn() method, most of the code run before the cpu_exec_realizefn() call checks whether the requested CPU features are compatible with the requested accelerator. Extract this code to a dedicated handler matching our recently added CPUClass::verify_accel_features() handler.
How much verification is this intended to do? Can realize now be required to succeed?For instance, the error for unset gt_cntfrq_hz just before timer_new could be moved to within this new function.
r~
[Prev in Thread] | Current Thread | [Next in Thread] |