From mboxrd@z Thu Jan  1 00:00:00 1970
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Subject: Re: [PATCH 9/9] KVM: x86: pass struct kvm_mmu_page to
 account/unaccount_shadowed
Date: Wed, 20 May 2015 22:12:48 +0200
Message-ID: <20150520201248.GA24014@potion.brq.redhat.com>
References: <1432056313-36100-1-git-send-email-pbonzini@redhat.com>
 <1432056313-36100-10-git-send-email-pbonzini@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <1432056313-36100-10-git-send-email-pbonzini@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

2015-05-19 19:25+0200, Paolo Bonzini:
> Prepare for multiple address spaces this way, since a VCPU is not available
> where unaccount_shadowed is called.  We will get to the right kvm_memslots
> 1truct through the role field in struct kvm_mmu_page.

struct kvm_mmu_page contains enough information to retrieve a memslot;
is it impractical to cache the memslot pointer there?