From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bandan Das Subject: Re: x86: Don't report guest userspace emulation error to userspace, why ? Date: Thu, 10 Dec 2015 15:35:28 -0500 Message-ID: References: <56694209.5050800@redhat.com> <5669BD73.7030902@redhat.com> <1932322445.37662446.1449778844466.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Cc: kvm To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42174 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753503AbbLJUfa (ORCPT ); Thu, 10 Dec 2015 15:35:30 -0500 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 88974C1FC438 for ; Thu, 10 Dec 2015 20:35:30 +0000 (UTC) In-Reply-To: <1932322445.37662446.1449778844466.JavaMail.zimbra@redhat.com> (Paolo Bonzini's message of "Thu, 10 Dec 2015 15:20:44 -0500 (EST)") Sender: kvm-owner@vger.kernel.org List-ID: Paolo Bonzini writes: >> 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. I don't buy that. As userspace, I prefer getting to know what error the guest I launched hit and decide what to do. Well, atleast whenever I can. This seems to be one such case. > Paolo