From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [PATCH v2] KVM: SVM: Sync g_pat with guest-written PAT value Date: Tue, 21 Apr 2015 14:21:49 +0200 Message-ID: <20150421122148.GA15983@potion.brq.redhat.com> References: <552B5128.4010909@siemens.com> <552B6923.3020602@siemens.com> <20150420161401.GB26491@potion.brq.redhat.com> <5535368B.9060408@siemens.com> <55362FFC.1040905@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kiszka , kvm , Joel Schopp To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58542 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751430AbbDUMVw (ORCPT ); Tue, 21 Apr 2015 08:21:52 -0400 Content-Disposition: inline In-Reply-To: <55362FFC.1040905@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 2015-04-21 13:09+0200, Paolo Bonzini: > > > On 20/04/2015 19:25, Jan Kiszka wrote: > > When hardware supports the g_pat VMCB field, we can use it for emulating > > the PAT configuration that the guest configures by writing to the > > corresponding MSR. > > > > Signed-off-by: Jan Kiszka > > I'm not sure about this. The problem is that, unlike Intel, AMD has no > way for the host to force its PAT value and ignore the guest's. I'm > worried about potential performance problems in the guest. We already set g_pat to 0x0007040600070406ULL in init_vmcb(). This patch uses caching that the guest expects, which might improve performance as well. I think it's a step in right direction even if we somehow optimize cache coherent cases later.