On 26.03.2021 19:59, Andrew Cooper wrote: > If Legacy Replacement mode doesn't help in check_timer(), restore the old > configuration before falling back to other workarounds. > > Signed-off-by: Andrew Cooper <[email protected]> > --- > CC: Jan Beulich <[email protected]> > CC: Roger Pau Monné <[email protected]> > CC: Wei Liu <[email protected]> > CC: Ian Jackson <[email protected]> > CC: Marek Marczykowski-Górecki <[email protected]> > CC: Frédéric Pierret <[email protected]> > > v2: > * New. > > For 4.15: Attempt to unbreak AMD Ryzen 1800X systems. > > I'm tempted to fold this into the previous patch, but its presented here in > isolation for ease of review.
Both combined Reviewed-by: Jan Beulich <[email protected]> (i.e. I think they strictly should be folded). Just as a (further) consideration: While I continue to think that undoing immediately is what we want, I wonder whether every further fallback attempt wouldn't want to also be accompanied by trying if it _combined_ with legacy replacement mode actually helps if alone it didn't. Perhaps we want to cross that bridge only if we get a respective report ... Jan
