qemu-kvm upstreaming: Do we need -no-kvm-pit and -no-kvm-pit-reinjection semantics?

[Jan Kiszka <jan.kiszka@siemens.com>]

Hi all,

I've finished a first version of cleaned-up in-kernel KVM PIT support.
That will be rolled out once the base support for irqchip has been merged.

I'm now wondering if and how to model two control knobs we have in qemu-kvm:

 o -no-kvm-pit, ie. disable the in-kernel PIT even when {A,IOA,}PIC
   are kernel based (default: off, ie. use in-kernel PIT)

 o -no-kvm-pit-reinjection, ie. control over the lost ticks reinjection
   logic in the kernel (default: off, ie. do reinject)

So far I dropped the former and modeled the latter via a qdev property.
But I tend to think that even the latter knob is superfluous. In that
case I would also deprecate the original switches in qemu-kvm, just like
recently done with -tdf.

Other thoughts?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux