From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Guest memory backed by PCI BAR (x86) Date: Thu, 26 Mar 2015 17:40:22 +0100 Message-ID: <55143676.1040709@redhat.com> References: <1790936111.88330.1427298998015.JavaMail.zimbra@xes-inc.com> <55141183.9000304@redhat.com> <1757049852.48328.1427385718889.JavaMail.zimbra@xes-inc.com> <55142EBF.8030600@redhat.com> <57551226.56219.1427387686368.JavaMail.zimbra@xes-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Nate Case Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45530 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752283AbbCZQk1 (ORCPT ); Thu, 26 Mar 2015 12:40:27 -0400 In-Reply-To: <57551226.56219.1427387686368.JavaMail.zimbra@xes-inc.com> Sender: kvm-owner@vger.kernel.org List-ID: On 26/03/2015 17:34, Nate Case wrote: > 0x52: add al,dh > 0x54: pop cx > 0x55: clc > 0x56: add al,dh > => 0x58: cs > 0x59: call 0xf05c > 0x5c: shr bh,cl > 0x5e: add al,dh > 0x60: add ax,0xcf > 0x63: lock repnz out 0x0,al This code makes no sense, it looks like the processor has gone into the weeds. :( Based on this: cs 0x9020 36896 I could guess, based on your use of resource2_wc, that the host is bypassing the processor cache but the guest is not. This use is not supported on x86 KVM, sorry. Paolo