WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] mem_sharing: summarized problems when domain is dying

To: Jui-Hao Chiang <juihaochiang@xxxxxxxxx>
Subject: Re: [Xen-devel] mem_sharing: summarized problems when domain is dying
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Fri, 21 Jan 2011 16:41:47 +0000
Cc: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Delivery-date: Fri, 21 Jan 2011 08:42:37 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DWPO33LpU9VxCkCtvxTchZGxcM5cob2ai6ef332m+LY=; b=ltcewTXxe+jlKCz4Jxq+6FqvxlNB2RnTxV2l03Srs2plpnWm4wVRCU9qLPI1OKt35V RZKI2SwL/oQjyTEjqhqFRZ/lsGRS6xKAbexGpMF/UA0oZ7yyAPdpv/xYhulrSxnXACj0 Y8LtaQ+Z5tybnI/TWWqknaaaXaCtP8UeUlV5s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=Cx25GGw/QL7exuBO4JgqsoS/TGBBv8HXRpUR7oeV+uD6UyE8mzBen1MpNvEufJ0geo 6UXgw/K0+9ykRCG2vFohQErF6/H97L8llslRJ3IDcUo4mY2zxkFLMA52cuBBR9aarYdc 75ubUnnU1phSIXndKU9f2FMWC/CYX7Kw38yEM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikpe-zo8hZNp3ERKS3uO5wpC2vWpun4MQqbWcTQ@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=wimfV7Wc6aEd2cYS-=dOb2V5Xy97eSCgW-gKh@xxxxxxxxxxxxxx> <AANLkTi=iECgZsjuPuR4LOQwzeAcsfG1eQLS+1krrfRFN@xxxxxxxxxxxxxx> <AANLkTikpe-zo8hZNp3ERKS3uO5wpC2vWpun4MQqbWcTQ@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Tim / Xiaoyun, do you think something like this might work?

 -George

On Fri, Jan 21, 2011 at 4:32 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
> [sorry, accidentally sent too early]
>
> On Fri, Jan 21, 2011 at 4:29 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
>> I'm not sure the exact rationale behind the "cannot fail" flag; but it
>> looks like in grant_table.c, both callers of gfn_to_mfn_unshare()
>> handle the case where the returned p2m entry is just
>
> ...invalid.  I wonder if "unsharing" the page, but marking the entry
> invalid during death would help.
>
> I suppose the problem there is that if you're keeping the VM around
> but paused for analysis, you'll have holes in your address space.  But
> just returning an invalid entry to the callers who try to unshare
> pages might work.
>
>  -George
>

Attachment: interpret_must_succeed_if_dying.diff
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel