21 Dec
2019
21 Dec
'19
3:48 a.m.
On Thu, Dec 12, 2019 at 07:23:46PM +0100, Paolo Bonzini wrote:
On 12/12/19 19:18, Sean Christopherson wrote:
Using v<feature> across the board makes sense to keep things consistent, i.e. vnmi, vtpr, vapic, etc...
Anyone have thoughts on how to shorten "APIC-register virtualization" without colliding with vapic or apicv? I currently have apic_reg_virt, which is a bit wordy. apic_regv isn't awful, but I don't love it.
Perhaps vapic_access and vapic_register?
I ended up going with vapic and vapic_reg, figured everyone looking at this knows what "reg" is short for, and I like the progression shown by vapic -> vapic_reg.