From owner-freebsd-stable@freebsd.org  Thu Jul  5 13:23:18 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB580102895C
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu,  5 Jul 2018 13:23:18 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 44CF97BDF2;
 Thu,  5 Jul 2018 13:23:18 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fb4E7-0002G7-7n; Thu, 05 Jul 2018 13:23:15 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, truckman@FreeBSD.org
References: <20180705103135.GD5562@kib.kiev.ua>
 <E1fb1jV-0000yT-B2@dilbert.ingresso.co.uk>
 <20180705104720.GE5562@kib.kiev.ua>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <b1e2dd4e-31e2-e98d-1324-1464bb40233b@ingresso.co.uk>
Date: Thu, 5 Jul 2018 14:23:15 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180705104720.GE5562@kib.kiev.ua>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 13:23:18 -0000



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.


> 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 ?

-pete.