From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH 1/2] kvm: Force IOMMU remapping on memory slot read-only flag changes Date: Fri, 25 Jan 2013 10:58:43 +0800 Message-ID: <5101F4E3.2020001@linux.vnet.ibm.com> References: <20130124220027.11061.76400.stgit@bling.home> <20130124220403.11061.61738.stgit@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: gleb@redhat.com, kvm@vger.kernel.org, yoshikawa_takuya_b1@lab.ntt.co.jp, linux-kernel@vger.kernel.org To: Alex Williamson Return-path: Received: from e23smtp09.au.ibm.com ([202.81.31.142]:39729 "EHLO e23smtp09.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754633Ab3AYC67 (ORCPT ); Thu, 24 Jan 2013 21:58:59 -0500 Received: from /spool/local by e23smtp09.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 25 Jan 2013 12:52:38 +1000 In-Reply-To: <20130124220403.11061.61738.stgit@bling.home> Sender: kvm-owner@vger.kernel.org List-ID: On 01/25/2013 06:04 AM, Alex Williamson wrote: > Memory slot flags can be altered without changing other parameters of > the slot. The read-only attribute is the only one the IOMMU cares > about, so generate an un-map, re-map when this occurs. This also > avoid unnecessarily re-mapping the slot when no IOMMU visible changes > are made. > Reviewed-by: Xiao Guangrong