From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=36898 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PDH34-0004hT-Pe
	for qemu-devel@nongnu.org; Tue, 02 Nov 2010 09:37:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PDE9X-0002vk-6B
	for qemu-devel@nongnu.org; Tue, 02 Nov 2010 06:31:44 -0400
Received: from mx1.redhat.com ([209.132.183.28]:50069)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PDE9W-0002vd-VZ
	for qemu-devel@nongnu.org; Tue, 02 Nov 2010 06:31:43 -0400
Message-ID: <4CCFE884.8030804@redhat.com>
Date: Tue, 02 Nov 2010 11:31:32 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 28/40] xenner: libxc emu: evtchn
References: <1288623713-28062-1-git-send-email-agraf@suse.de>
	<1288623713-28062-29-git-send-email-agraf@suse.de>
	<4CCEE08F.4030403@codemonkey.ws>
	<F67E81A5-2164-4A2E-AEEB-EB693510971F@suse.de>
	<4CCEE463.3090406@codemonkey.ws> <4CCF176F.2020600@redhat.com>
	<4CCF17EF.8090502@codemonkey.ws>
	<0A26E838-7FF5-4E4C-98EB-5EB0821460B9@suse.de>
	<4CCF23E9.8070404@codemonkey.ws>
	<alpine.DEB.2.00.1011020031100.1407@kaball-desktop>
	<4CCFE2AB.1050204@redhat.com>
In-Reply-To: <4CCFE2AB.1050204@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>, Alexander Graf <agraf@suse.de>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>

   Hi,

> (BTW, I noticed that Xenner does not limit guest segments like Xen does.
> Does it mean the guest can overwrite the Xenner kernel and effectively
> run ring0?)

Yes.  The guest also can modify page tables as it pleases.  It is the 
vmx/svm container which protects the host, not the xenner kernel.

cheers,
   Gerd