From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: KVM: How does is PAT emulation supposed to work? Date: Fri, 17 Apr 2015 19:12:27 +0200 Message-ID: <55313EFB.8000300@siemens.com> References: <552B5128.4010909@siemens.com> <20150417164310.GA3419@potion.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: Received: from thoth.sbs.de ([192.35.17.2]:39731 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932630AbbDQRMf (ORCPT ); Fri, 17 Apr 2015 13:12:35 -0400 In-Reply-To: <20150417164310.GA3419@potion.brq.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2015-04-17 18:43, Radim Kr=C4=8Dm=C3=A1=C5=99 wrote: > 2015-04-13 07:16+0200, Jan Kiszka: >> PS: If someone has a good idea for a simple test case on machines >> without IOMMU (like my current boxes), thus without a chance to use >> device pass-through to stress guest PAT settings, I would be all ear= s. >=20 > Not a good one: KVM sets VMX_EPT_IPAT_BIT for RAM unless > kvm_arch_has_noncoherent_dma(). You can comment the line in > vmx_get_mt_mask(), or call kvm_arch_register_noncoherent_dma(), > for guest PAT to work on normal memory. That's for VMX (where I do have IOMMUs), but I would need something for AMD. :) Jan --=20 Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux