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

[Xen-devel] [PATCH] Handle PoD case in hvm_hap_nested_page_fault()

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Handle PoD case in hvm_hap_nested_page_fault()
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Wed, 6 Jan 2010 12:19:37 +0000
Delivery-date: Wed, 06 Jan 2010 04:19:57 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Qg2g6aYZox7+xFILGJwqqj+xpInnkbmRrJn/bWlRDgA=; b=e/awqnK6F0AztpTX6IHfdIpIZ3fdcObMTig6YT4XhwOwG5xz99dvf9EvGf5KYl++6E YtxncGM4PiwaAO284pDSZQrZcdMMtLvBL8S+avM7lUdE9mF/iNvnwuA/Ou3Y70saptbj WWpagOuQKOPm3GEAros2Gn61C3AEiFO5QSLps=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=VESkhVpUTiAi1l+flCwzYYen73P7ltdXHQ44WMj9/1mcUZ6IMaPpJC82nkeO/Dvrb0 Zn3fzeOFpHcv/KcEdjbJOOJwmokyvmKKsNAlYy+RzSYu9H0kZlh1ldIlxc4tOW9OUpOg kFV2TzVBY+yE73i0nXuC3ER3eQGD464/2ta38=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The new combined nested page fault handling doesn't consider the case
where the gfn_to_mfn() translation caused the page to be transparently
populated.  Attached patch is one solution; a more robust solution
would be to take the access type (read or write) and check it against
the type returned by gfn_to_mfn() to handle spurious NPFs as well (if
such things ever happen).

Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>

Attachment: 20100106-handle-pod-populate.diff
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>