Date: Thu, 5 Jul 2018 16:35:42 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Pete French <petefrench@ingresso.co.uk> Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <20180705133542.GG5562@kib.kiev.ua> In-Reply-To: <b1e2dd4e-31e2-e98d-1324-1464bb40233b@ingresso.co.uk> References: <20180705103135.GD5562@kib.kiev.ua> <E1fb1jV-0000yT-B2@dilbert.ingresso.co.uk> <20180705104720.GE5562@kib.kiev.ua> <b1e2dd4e-31e2-e98d-1324-1464bb40233b@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 05, 2018 at 02:23:15PM +0100, Pete French wrote: > > > On 05/07/2018 11:47, Konstantin Belousov wrote: > > Why do you state that they are saved/restored ? What is the evidence ? > > > https://software.intel.com/en-us/blogs/2009/06/25/virtualization-and-performance-understanding-vm-exits > > specificly... > > 3) "Save MSRs in the VM-exit MSR-store area." > > and > > 5) "Load MSRs from the VM-exit MSR-load area." > > but maybe thats not actyually true, I assumed it was given its an Intel > document, but admittedly its not an actual specification. This is true, but absolutely irrelevant. Modern CPUs have hundreds, if not thousands, MSR registers. Only some of them define architectural state, and saved/restored on the context switches. Chicken bits are global knobs not relevant to the vmm entry. > > > > On VM the patch should be NOP, testing it is a waste of time IMO. > > > OK, will ignore that then. I am running the new patch on my workstation > now - I still need the old patch for the other files, yes ? Which other files ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180705133542.GG5562>