> On 21. Jan 2026, at 10:27, Peter Maydell <[email protected]> wrote:
>
> On Tue, 20 Jan 2026 at 18:44, Mohamed Mediouni <[email protected]>
> wrote:
>>
>>
>>
>>> On 20. Jan 2026, at 19:02, Peter Maydell <[email protected]> wrote:
>>
>>
>>> The MSI controller selection logic is already pretty confusing,
>>> and this is making it more complicated. I don't think we should
>>> need this machine back compatibility, because currently there
>>> is no setup where you can have a GICv3 that doesn't also have
>>> either an ITS or no MSI controller.
>>>
>> Hello,
>>
>> This was to replicate the “no_tcg_its” where this was done when introducing
>> TCG.
>> And for the purpose of VM save/restore on HVF with the older machine type
>> continuing to work as expected.
>
> no_tcg_its is there for backwards compatibility: on older
> QEMU versions before we added the TCG ITS, if you said
> "-machine virt,gic-version=3 -accel tcg" you didn't get an
> ITS; we wanted to change the default in new machine versions,
> so we needed the back compat switch.
>
> What is the command line that works today and where we
> want to go from "default to GICv3 without ITS or v2m"
> to "default to GICv3 with v2m" ? I might have missed it
> but back last year when I was looking at the current
> configs I didn't think we had one.
Hello,
None, was thinking about what its=off should mean but perhaps
the right behaviour to do there is to have it mean no MSI-X controller.
The no_gicv3_with_gicv2m flag is solely used for the its
config option (which is legacy) and not used for the msi
config option.
Will make the next patch rev make its=off mean no MSI-X controller at all
and remove the no_gicv3_with_gicv2m flag then.
> thanks
> -- PMM
