Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Jul 2019 22:32:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 224476] [patch] bhyve: emulate MSR_EXTFEATURES
Message-ID:  <bug-224476-27103-Jpi0Ij7mNH@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224476-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-224476-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224476

--- Comment #3 from commit-hook@freebsd.org ---
A commit references this bug:

Author: jhb
Date: Fri Jul 12 22:31:15 UTC 2019
New revision: 349958
URL: https://svnweb.freebsd.org/changeset/base/349958

Log:
  MFC 339911,339936,343075,343166,348592: Various AMD CPU-specific fixes.

  339911:
  Emulate machine check related MSR_EXTFEATURES to allow guest OSes to
  boot on AMD FX Series.

  339936:
  Merge cases with upper block.
  This is a cosmetic change only to simplify code.

  343075:
  vmm(4): Take steps towards multicore bhyve AMD support

  vmm's CPUID emulation presented Intel topology information to the guest, =
but
  disabled AMD topology information and in some cases passed through garbag=
e.
  I.e., CPUID leaves 0x8000_001[de] were passed through to the guest, but
  guest CPUs can migrate between host threads, so the information presented
  was not consistent.  This could easily be observed with 'cpucontrol -i 0x=
foo
  /dev/cpuctl0'.

  Slightly improve this situation by enabling the AMD topology feature flag
  and presenting at least the CPUID fields used by FreeBSD itself to probe
  topology on more modern AMD64 hardware (Family 15h+).  Older stuff is
  probably less interesting.  I have not been able to empirically confirm it
  is sufficient, but it should not regress anything either.

  343166:
  vmm(4): Mask Spectre feature bits on AMD hosts

  For parity with Intel hosts, which already mask out the CPUID feature
  bits that indicate the presence of the SPEC_CTRL MSR, do the same on
  AMD.

  Eventually we may want to have a better support story for guests, but
  for now, limit the damage of incorrectly indicating an MSR we do not yet
  support.

  Eventually, we may want a generic CPUID override system for
  administrators, or for minimum supported feature set in heterogenous
  environments with failover.  That is a much larger scope effort than
  this bug fix.

  348592:
  Emulate the AMD MSR_LS_CFG MSR used for various Ryzen errata.

  Writes are ignored and reads always return zero.

  PR:           224476, 235010

Changes:
_U  stable/11/
  stable/11/sys/amd64/vmm/amd/svm_msr.c
  stable/11/sys/amd64/vmm/x86.c
  stable/11/sys/amd64/vmm/x86.h
  stable/11/sys/x86/x86/mp_x86.c
  stable/11/usr.sbin/bhyve/xmsr.c
_U  stable/12/
  stable/12/sys/amd64/vmm/amd/svm_msr.c
  stable/12/sys/amd64/vmm/x86.c
  stable/12/sys/amd64/vmm/x86.h
  stable/12/sys/x86/x86/mp_x86.c
  stable/12/usr.sbin/bhyve/xmsr.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224476-27103-Jpi0Ij7mNH>