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/
Home Products Support Community News


[Xen-devel] RE: [PATCH] Unmmap guest's EPT mapping for poison memory

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH] Unmmap guest's EPT mapping for poison memory
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Mon, 13 Sep 2010 21:41:42 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 13 Sep 2010 06:42:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100913133810.GI3844@xxxxxxxxxxxxxxxxxxxxxxx>
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: <789F9655DD1B8F43B48D77C5D30659731F571361@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100714092808.GB13291@xxxxxxxxxxxxxxxxxxxxxxx> <789F9655DD1B8F43B48D77C5D30659731F5714FA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100715151238.GG13291@xxxxxxxxxxxxxxxxxxxxxxx> <789F9655DD1B8F43B48D77C5D30659731F5C84E8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100716085217.GJ13291@xxxxxxxxxxxxxxxxxxxxxxx> <789F9655DD1B8F43B48D77C5D30659732A2FF407@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100913133810.GI3844@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActTSOqB+gp/LKc5SLaoFhpinuJagAAAHBVw
Thread-topic: [PATCH] Unmmap guest's EPT mapping for poison memory
Thanks for review. I will re-send it as patch submission.


>-----Original Message-----
>From: Tim Deegan [mailto:Tim.Deegan@xxxxxxxxxx]
>Sent: Monday, September 13, 2010 9:38 PM
>To: Jiang, Yunhong
>Cc: Keir Fraser; xen-devel
>Subject: Re: [PATCH] Unmmap guest's EPT mapping for poison memory
>At 10:19 +0100 on 13 Sep (1284373193), Jiang, Yunhong wrote:
>> I'm not sure if the change to the _gfn_to_mfn_type() is
>> acceptable. Especially, if it is right to change the mfn to be
>> INVALID_MFN. The idea to change the mfn to be INVALID_MFN is, we don't
>> need to change every caller for broken type (I noticed the PoD/sharing
>> etc checked each caller), but depends on caller will check the mfn to
>> be valid or not.
>That's fine.  All callers _should_ check the type but there's no harm in
>changing the mfn as a double precaution, even if everything else was right.
>Acked-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>Principal Software Engineer, XenServer Engineering
>Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>