[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH for-4.14] x86/ucode: Fix errors with start/end_update()


  • To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Date: Mon, 1 Jun 2020 17:48:32 +0200
  • Authentication-results: esa3.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Paul Durrant <paul@xxxxxxx>
  • Delivery-date: Mon, 01 Jun 2020 15:48:49 +0000
  • Ironport-sdr: qWPRz7rXOFHQ5gaus6W6RV8ThmlGiE8Hyrh1P5QTrKD5qAw3qreZTAdqRkWGnJcvlzn0PFDkt6 sZ7BLqXPlJEoV9I2+7C6VqJ/uDWS0NKXbDXMlXc2mK1GAK3A/z6jEPER/NzGUg/niezwUiMD/5 z+GpvtqE/SJKeQkMLE+KLDL8kcqydySSDG4Ky3hKLOfB3/r20vNjLi3cNKWiuQQflRorAVNDv+ ptjRkhFZI2w7aQa/JEdvyhqs8rkR7tNUM7Fc3hEVunYY5/Ahww94CX46KmAB39W5T53guA+4HO EnA=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, Jun 01, 2020 at 03:57:55PM +0100, Andrew Cooper wrote:
> c/s 9267a439c "x86/ucode: Document the behaviour of the microcode_ops hooks"
> identified several poor behaviours of the start_update()/end_update_percpu()
> hooks.
> 
> AMD have subsequently confirmed that OSVW don't, and are not expected to,
> change across a microcode load, rendering all of this complexity unecessary.

Is there a reference to some AMD PM or similar document that can be
added here for completeness?

> Instead of fixing up the logic to not leave the OSVW state reset in a number
> of corner cases, delete the logic entirely.  This in turn allows for the
> removal of the poorly-named 'start_update' parameter to
> microcode_update_one().
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

Thanks, Roger.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.