From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752745AbbERIbz (ORCPT ); Mon, 18 May 2015 04:31:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56487 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752087AbbERIbp (ORCPT ); Mon, 18 May 2015 04:31:45 -0400 Message-ID: <5559A367.5000305@redhat.com> Date: Mon, 18 May 2015 10:31:35 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Avi Kivity , linux-kernel@vger.kernel.org, kvm@vger.kernel.org CC: rkrcmar@redhat.com, bsd@redhat.com, guangrong.xiao@linux.intel.com, Yang Zhang , wanpeng.li@linux.intel.com Subject: Re: [PATCH 12/13] KVM: x86: add KVM_MEM_X86_SMRAM memory slot flag References: <1430393772-27208-1-git-send-email-pbonzini@redhat.com> <1430393772-27208-13-git-send-email-pbonzini@redhat.com> <555657D0.5080500@gmail.com> In-Reply-To: <555657D0.5080500@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15/05/2015 22:32, Avi Kivity wrote: > Alternative approach: store the memslot pointer in the vcpu, instead of > of vcpu->kvm. The uapi interface code can generate two memslot tables > to be stored in kvm->, one for smm and one for !smm. That's a great suggestion---and easy to implement too. Thanks Avi for chiming in! Paolo