From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Subject: Re: [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to
 Guest
Date: Tue, 7 May 2013 18:40:43 -0500
Message-ID: <1367970043.3398.39@snotra>
References: <1367924791-24394-1-git-send-email-tiejun.chen@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed
Content-Transfer-Encoding: 8BIT
Cc: <agraf@suse.de>, <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>,
	<linuxppc-dev@lists.ozlabs.org>
To: Tiejun Chen <tiejun.chen@windriver.com>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <1367924791-24394-1-git-send-email-tiejun.chen@windriver.com>
	(from tiejun.chen@windriver.com on Tue May  7 06:06:30 2013)
Content-Disposition: inline
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 05/07/2013 06:06:30 AM, Tiejun Chen wrote:
> We also can direct ISI exception to Guest like DSI.
> 
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
> ---
>  arch/powerpc/kvm/booke_emulate.c |    3 +++
>  arch/powerpc/kvm/e500mc.c        |    3 ++-
>  2 files changed, 5 insertions(+), 1 deletion(-)

Are you seeing a real performance improvement from this?  This will  
interfere somewhat with using the VF bit, if we were to ever do so,  
since VF only affects data accesses (and so the guest would see an ISI  
storm rather than a machine check if it tries to execute from such an  
address).

-Scott