From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: x86: Don't report guest userspace emulation error to userspace,
 why ?
Date: Thu, 10 Dec 2015 18:59:15 +0100
Message-ID: <5669BD73.7030902@redhat.com>
References: <jpg6107gtaf.fsf@linux.bootlegged.copy>
 <56694209.5050800@redhat.com> <jpg7fkm89tk.fsf@linux.bootlegged.copy>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Bandan Das <bsd@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:51675 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753683AbbLJR7W (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 10 Dec 2015 12:59:22 -0500
Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26])
	by mx1.redhat.com (Postfix) with ESMTPS id D2C67C001247
	for <kvm@vger.kernel.org>; Thu, 10 Dec 2015 17:59:22 +0000 (UTC)
In-Reply-To: <jpg7fkm89tk.fsf@linux.bootlegged.copy>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



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.

Paolo

>> > possible denial of service, similar to L2 stopping L1 with an emulation
>> > failure.