From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: x86: Don't report guest userspace emulation error to userspace, why ? Date: Thu, 10 Dec 2015 15:20:44 -0500 (EST) Message-ID: <1932322445.37662446.1449778844466.JavaMail.zimbra@redhat.com> References: <56694209.5050800@redhat.com> <5669BD73.7030902@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: kvm To: Bandan Das Return-path: Received: from mx4-phx2.redhat.com ([209.132.183.25]:36546 "EHLO mx4-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752675AbbLJUUp (ORCPT ); Thu, 10 Dec 2015 15:20:45 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: > Paolo Bonzini writes: > > On 10/12/2015 18:58, Bandan Das wrote: > >>> > Allowing userspace to stop the guest with an emulation failure is a > >> This one I don't :) Userspace started the guest after all, there are other > >> ways for it to kill the guest if it wanted to. > > > > I mean allowing guest userspace to stop the guest. > > Sure! Userspace (Qemu) can just reenter the guest when it sees the failure. > Doing it in the host kvm seems overkill. Most userspaces will get it wrong. Doing it once makes sure that you do it right. Paolo