From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bandan Das <bsd@redhat.com>
Subject: Re: x86: Don't report guest userspace emulation error to userspace, why ?
Date: Thu, 10 Dec 2015 13:36:14 -0500
Message-ID: <jpg4mfqywv5.fsf@linux.bootlegged.copy>
References: <jpg6107gtaf.fsf@linux.bootlegged.copy>
	<56694209.5050800@redhat.com> <jpg7fkm89tk.fsf@linux.bootlegged.copy>
	<5669BD73.7030902@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: kvm <kvm@vger.kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:40640 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751424AbbLJSgQ (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 10 Dec 2015 13:36:16 -0500
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	by mx1.redhat.com (Postfix) with ESMTPS id 66B9CC1A0BC5
	for <kvm@vger.kernel.org>; Thu, 10 Dec 2015 18:36:16 +0000 (UTC)
In-Reply-To: <5669BD73.7030902@redhat.com> (Paolo Bonzini's message of "Thu,
	10 Dec 2015 18:59:15 +0100")
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Paolo Bonzini <pbonzini@redhat.com> 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.

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