[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC 2/9] target/arm: parse cpu feature related options
|
From: |
Andrew Jones |
|
Subject: |
Re: [RFC 2/9] target/arm: parse cpu feature related options |
|
Date: |
Thu, 13 Aug 2020 14:21:13 +0200 |
On Thu, Aug 13, 2020 at 06:26:50PM +0800, Peng Liang wrote:
> The implementation of CPUClass::parse_features only supports CPU
> features in "feature=value" format. However, libvirt maybe send us a
> CPU feature string in "+feature/-feature" format.
Why would libvirt do that? If we have a boolean feature, then I'd think
libvirt should be capable of sending feature=on/off just as easily as a
+/-feature. Indeed libvirt seems to do the right thing with all the
CPU features we already have: pmu, sve*, ...
Thanks,
drew
[RFC 7/9] target/arm: Add CPU features to query-cpu-model-expansion, Peng Liang, 2020/08/13
[RFC 1/9] target/arm: convert isar regs to array, Peng Liang, 2020/08/13
[RFC 9/9] target/arm: Add more CPU features, Peng Liang, 2020/08/13