Re: [RFC PATCH-for-10.1 v2 0/7] tcg: Move TCG_GUEST_DEFAULT_MO -> TCGCPUOps::guest_default_memory_order

["Philippe Mathieu-Daudé" <philmd@linaro.org>]

On 2/4/25 22:27, Philippe Mathieu-Daudé wrote:
> On 2/4/25 22:00, Richard Henderson wrote:
>> On 3/21/25 11:15, Philippe Mathieu-Daudé wrote:
>>> Since v1:
>>> - Do not use tcg_ctx in tcg_req_mo (rth)
>>>
>>> Hi,
>>>
>>> In this series we replace the TCG_GUEST_DEFAULT_MO definition
>>> from "cpu-param.h" by a 'guest_default_memory_order' field in
>>> TCGCPUOps.
>>>
>>> Since tcg_req_mo() now accesses tcg_ctx, this impact the
>>> cpu_req_mo() calls in accel/tcg/{cputlb,user-exec}.c.
>>>
>>> The long term goal is to be able to use targets with distinct
>>> guest memory order restrictions.
>>>
>>> Philippe Mathieu-Daudé (7):
>>>    tcg: Always define TCG_GUEST_DEFAULT_MO
>>>    tcg: Simplify tcg_req_mo() macro
>>>    tcg: Define guest_default_memory_order in TCGCPUOps
>>>    tcg: Remove use of TCG_GUEST_DEFAULT_MO in tb_gen_code()
>>>    tcg: Propagate CPUState argument to cpu_req_mo()
>>>    tcg: Have tcg_req_mo() useTCGCPUOps::guest_default_memory_order
>>>    tcg: Remove the TCG_GUEST_DEFAULT_MO definition globally
>>
>> Queued to tcg-next, thanks.
> 
> Thanks but I neglected to test on linux-user and found a pair of issues,
> so I'll respin with them addressed.

Oops, wrong series (I meant the one about TCGCPUOps::mttcg_supported).
This one is OK.