[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [qemu-s390x] [PATCH 3/3] qmp: add architecture specific cpu data for
From: |
Luiz Capitulino |
Subject: |
Re: [qemu-s390x] [PATCH 3/3] qmp: add architecture specific cpu data for query-cpus-fast |
Date: |
Mon, 12 Feb 2018 13:15:04 -0500 |
On Mon, 12 Feb 2018 13:14:32 +0100
Viktor Mihajlovski <address@hidden> wrote:
> -{ 'struct': 'CpuInfoFast',
> - 'data': {'cpu-index': 'int', 'qom-path': 'str',
> - 'thread-id': 'int', '*props': 'CpuInstanceProperties' } }
> +{ 'union': 'CpuInfoFast',
> + 'base': {'cpu-index': 'int', 'qom-path': 'str',
> + 'thread-id': 'int', '*props': 'CpuInstanceProperties',
> + 'arch': 'CpuInfoArch' },
> + 'discriminator': 'arch',
> + 'data': { 'x86': 'CpuInfoOther',
> + 'sparc': 'CpuInfoOther',
> + 'ppc': 'CpuInfoOther',
> + 'mips': 'CpuInfoOther',
> + 'tricore': 'CpuInfoOther',
> + 's390': 'CpuInfoS390Fast',
> + 'other': 'CpuInfoOther' } }
Consider this a minor comment (and QMP maintainers can give a much
better advice than me), but I think this arch list has problems. For
one thing, it's incomplete. And the second problem is the 'other'
field. What happens when QEMU starts supporting a new arch? 'other'
becomes the new arch. Is this compatible? I don't know.
I don't know if this would work with the QAPI, but you could have
a '*arch-data' field in the CpuInfoFast definition, like:
'data': { ..., '*arch-data': 'CpuInfoFastArchData' }
where 'CpuInfoFastArchData' is defined by each arch that supports
the field. An arch supporting the field could also export a
query_cpus_fast_arch() function, which is called by qmp_query_cpus_fast().
- Re: [qemu-s390x] [PATCH 1/3] qmp: expose s390-specific CPU info, (continued)
Re: [qemu-s390x] [PATCH 0/3] add query-cpu-fast and related s390 changes, Cornelia Huck, 2018/02/12