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] Re: changeset 22526:7a5ee3800417

To: George Dunlap <george.dunlap@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: changeset 22526:7a5ee3800417
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 9 Mar 2011 13:59:11 +0000
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, 张鹏飞 <zpfalpc23@xxxxxxxxx>
Delivery-date: Wed, 09 Mar 2011 06:03:05 -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 :content-transfer-encoding; bh=w1eXGB9YkVHKbOgUu4qGnyf2Tw6B1M7DsW2UScPLd+Y=; b=xKa7xqKzpgPFNeLu+NdepFBPK/2wRE56d7h4CKMBzMwtlzk46mNAfxXJYcBIJVOTNm uSE5hQUcjoFF5gLYxO7Rjh8buS1B5+HXAFhm6KmfUif5ITfdeau402MEitpoxKWOXAO9 RPf89ZMBVPay2t9pdaimEF+of54AMumGon2u0=
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 :content-transfer-encoding; b=IZD2p2tkkzPjuJqC+gSy2mIT7PxSh2OYJ3/l1Bku8lWnLoJnt83sKg1KSc+qDN5sPs mYkf/4mw0PMQRroOvHY0kQKAiyvNC8YZwkR2rJ/j5hxdJtgJb5CP9FaAwDPEWZDuBSZm /P5+29XXDsutEbcns00Im7JsqRzEHw4Ct0jHY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimqzZc7B0MG-PoD0ny=mdjrfvbc9ZAWkqQ526VH@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: <AANLkTimqNJWRWzSj1BYPP5T7GAhSK_=70T9dq5CW94iB@xxxxxxxxxxxxxx> <1299514840.19262.4698.camel@elijah> <AANLkTimqzZc7B0MG-PoD0ny=mdjrfvbc9ZAWkqQ526VH@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Peng fei,

I just noticed this patch has a bug -- it doesn't set new_entry.mfn if
the new mfn is the same as the one already in ept_entry!  Standby for
a new one...

 -George

On Mon, Mar 7, 2011 at 4:41 PM, George Dunlap
<George.Dunlap@xxxxxxxxxxxxx> wrote:
> Peng fei,
>
> Can you test the attached patch (to xen-unstable)?  I don't have
> EPT-enabled hardware handy...
>
>  -George
>
> On Mon, Mar 7, 2011 at 4:20 PM, George Dunlap <george.dunlap@xxxxxxxxxx> 
> wrote:
>> Hmm, yeah, that's obviously not right!  Let me take a look...
>>
>>  -George
>>
>> On Mon, 2011-03-07 at 09:55 +0000, 张鹏飞 wrote:
>>> Hi,
>>>     Recently, I did a research on the p2m and EPT,and did apply your
>>> patch(22526) to the source code of mine. But there is one place
>>> confused me:
>>>
>>>
>>>
>>> ept_entry = table + index;
>>> 1.91
>>>     1.92 -        ept_entry->emt = epte_get_entry_emt(d, gfn, mfn, &ipat, 
>>> direct_mmio);
>>>     1.93 -        ept_entry->ipat = ipat;
>>>     1.94 -        ept_entry->sp = i ? 1 : 0;
>>>     1.95 -        ept_entry->avail1 = p2mt;
>>>     1.96 -        ept_entry->avail2 = 0;
>>>     1.97 +        new_entry.emt = epte_get_entry_emt(d, gfn, mfn, &ipat, 
>>> direct_mmio);
>>>     1.98 +        new_entry.ipat = ipat;
>>>     1.99 +        new_entry.sp = i ? 1 : 0;
>>>    1.100 +        new_entry.avail1 = p2mt;
>>>    1.101 +        new_entry.avail2 = 0;
>>>    1.102
>>>    1.103 -        if ( ept_entry->mfn == mfn_x(mfn) )
>>>    1.104 +        if ( new_entry.mfn == mfn_x(mfn) )
>>>    1.105               need_modify_vtd_table = 0;
>>>    1.106          else /* the caller should take care of the previous page 
>>> */
>>>    1.107 -            ept_entry->mfn = mfn_x(mfn);
>>>    1.108 +            new_entry.mfn = mfn_x(mfn);
>>>
>>> I think, The new_entry.mfn is used without assigned any value. Maybe there 
>>> was something else I did not think of.
>>> Thank you for your kindness!
>>>
>>> http://xenbits.xen.org/xen-unstable.hg/rev/7a5ee3800417
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>

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