From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH] KVM: x86: Avoid zapping mmio sptes twice for generation wraparound Date: Wed, 03 Jul 2013 16:50:10 +0800 Message-ID: <51D3E5C2.7000007@linux.vnet.ibm.com> References: <20130703171804.89d6cc2c.yoshikawa_takuya_b1@lab.ntt.co.jp> <51D3E093.3020408@redhat.com> <51D3E33D.1090704@linux.vnet.ibm.com> <20130703175005.8e02a5d4.yoshikawa_takuya_b1@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , gleb@redhat.com, kvm@vger.kernel.org To: Takuya Yoshikawa Return-path: Received: from e23smtp02.au.ibm.com ([202.81.31.144]:58192 "EHLO e23smtp02.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754628Ab3GCIuh (ORCPT ); Wed, 3 Jul 2013 04:50:37 -0400 Received: from /spool/local by e23smtp02.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 3 Jul 2013 18:40:27 +1000 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [9.190.234.120]) by d23dlp03.au.ibm.com (Postfix) with ESMTP id F04D73578055 for ; Wed, 3 Jul 2013 18:50:13 +1000 (EST) Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r638ZEK81245490 for ; Wed, 3 Jul 2013 18:35:15 +1000 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r638oCOX026474 for ; Wed, 3 Jul 2013 18:50:12 +1000 In-Reply-To: <20130703175005.8e02a5d4.yoshikawa_takuya_b1@lab.ntt.co.jp> Sender: kvm-owner@vger.kernel.org List-ID: On 07/03/2013 04:50 PM, Takuya Yoshikawa wrote: > On Wed, 03 Jul 2013 16:39:25 +0800 > Xiao Guangrong wrote: > >> Please wait a while. I can not understand it very clearly. >> >> This conditional check will cause caching a overflow value into mmio spte. >> The simple case is that kvm adds new slots for many times, the mmio-gen is easily >> more than MMIO_MAX_GEN. > > Unconditional checking in commit_memory_region() is still there > to treat such cases. WHY?