CVS commit: [netbsd-11] src/sys/dev/nvmm/x86

"Martin Husemann" <[email protected]>
Newsgroups gmane.os.netbsd.devel.cvs
Message-ID <[email protected]>
Module Name:	src
Committed By:	martin
Date:		Thu May  7 15:27:48 UTC 2026

Modified Files:
	src/sys/dev/nvmm/x86 [netbsd-11]: nvmm_x86_svm.c nvmm_x86_vmx.c

Log Message:
Pull up following revision(s) (requested by riastradh in ticket #264):

	sys/dev/nvmm/x86/nvmm_x86_svm.c: revision 1.94
	sys/dev/nvmm/x86/nvmm_x86_vmx.c: revision 1.94

nvmm: Don't report physical lapic freq as virtual lapic freq.

The virtual lapic emulated by qemu in software always ticks at 1 GHz,
but the physical lapic on my laptop, for example, ticks at 24 MHz.

In order for this to work as iMil intended, we need some way for the
hypervisor (such as qemu) to tell nvmm what its lapic frequency is.

Until we have that, we can't correctly report any alleged lapic
frequency to the guest.

PR kern/59424: hardclock ticks run at breakneck pace under qemu


To generate a diff of this commit:
cvs rdiff -u -r1.89 -r1.89.2.1 src/sys/dev/nvmm/x86/nvmm_x86_svm.c
cvs rdiff -u -r1.90.2.1 -r1.90.2.2 src/sys/dev/nvmm/x86/nvmm_x86_vmx.c

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.