https://bugzilla.kernel.org/show_bug.cgi?id=206579 --- Comment #40 from muncrief (rmuncrief@xxxxxxxxxxxxxxx) --- (In reply to Anthony from comment #39) > (In reply to muncrief from comment #38) > > (In reply to Anthony from comment #37) > ... Oh if that's the case then my understanding has just been poor as I assumed > the kvm_apicv_update_request counter should be higher to show the times > where apicv has been activated and deactivated which should also be > reflected in a trace. At least that is what it reads like to me reading this > patch - https://lore.kernel.org/patchwork/patch/1153605/ I took a look at that just out of curiosity Anthony but unfortunately I don't know anything about the Linux kernel code, I've just been following along with the devs as best I can. I'm simply a retired hardware/firmware/software designer from the olden days. And by "olden" I mean before Linux, and even things like CGA graphics, existed :) I was just passing along what I learned from Suravee, and some cursory observation of tiny related code segments. All I was ever able to accomplish was a partial understanding of the first 5 bits of the avic_inhibit_reasons output :) Your question is an interesting one though, I wasn't even aware that a request counter existed! -- You are receiving this mail because: You are watching the assignee of the bug.
