From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bandan Das Subject: Re: [PATCH 12/13] KVM: x86: add KVM_MEM_X86_SMRAM memory slot flag Date: Wed, 06 May 2015 14:15:09 -0400 Message-ID: References: <1430393772-27208-1-git-send-email-pbonzini@redhat.com> <1430393772-27208-13-git-send-email-pbonzini@redhat.com> <20150505171747.GB17198@potion.brq.redhat.com> <5549E337.1090606@redhat.com> <20150506162437.GA27205@potion.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Paolo Bonzini , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, guangrong.xiao@linux.intel.com, Yang Zhang , wanpeng.li@linux.intel.com To: Radim =?utf-8?B?S3LEjW3DocWZ?= Return-path: In-Reply-To: <20150506162437.GA27205@potion.brq.redhat.com> ("Radim \=\?utf-8\?B\?S3LEjW3DocWZIidz\?\= message of "Wed, 6 May 2015 18:24:41 +0200") Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Radim Kr=C4=8Dm=C3=A1=C5=99 writes: =2E.. > > That doesn't improve the main issue, so x86 is good. > >>> Another option is adding something like "vcpu kvm_arch_fake_vcpu(kv= m)" >>> for cases where the access doesn't have an associated vcpu, so it w= ould >>> always succeed. (Might not be generic enough.) >>=20 >> That's ugly... > > Yes. (And I still prefer it.) Ooh, I hope we don't go this route :) I understand the motivation but=20 if there would be cases where we would have to fake the condition to be true, maybe we should reconsider our design. Bandan