From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: Re: [PATCH 0/5] x86: properly propagate errors to
	hypercall callee
Date: Fri, 11 Mar 2011 09:25:30 +0000
Message-ID: <4D79F89A0200007800035C4D@vpn.id2.novell.com>
References: <4D776A320200007800035752@vpn.id2.novell.com>
	<C99D1005.145F1%keir.xen@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C99D1005.145F1%keir.xen@gmail.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.xen@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

>>> On 09.03.11 at 12:07, Keir Fraser <keir.xen@gmail.com> wrote:
> It seems unfortunate to propagate this to guests. Perhaps we should be
> making a memory pool for Xen's 1:1 mappings, big enough to allow a 4kB
> mapping of every page of RAM in the system, and allocate/free pagetables =
to
> that pool? The overhead of this would be no more than 0.2% of system =
memory,
> which seems reasonable to avoid an error case that is surely hard for a
> guest to react to or fix.

Before starting to look into eventual Linux side changes - do you
then have plans to go that pool route (which would make guest=20
side recovery attempts pointless)?

Jan