[Xen-devel] [PATCH 0 of 5] mem_access: introduction of per-page

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] [PATCH 0 of 5] mem_access: introduction of per-page access controls
From:	Joe Epstein <jepstein@xxxxxxxxxxxxxxxxxxxx>
Date:	Tue, 28 Dec 2010 23:27:12 -0800
Delivery-date:	Tue, 28 Dec 2010 23:28:39 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=33pVzhqBd4jEhQTdL9pq0WBiDbfgypu6989/gp0OpIU=; b=AIQsWZziJeYAid7mN0UXGuUJ8u2x3EsVRoU3H4F6iuGIXzBWYXcTfbr2EHyynYzIQ1 52LXKnfBb6Aehj9lk7gD5IaMG1gWeO4D7In9p53jR/omRCZ64flTsVteK4DtUogl+F4x gTBLh7Y/5nrGxxXXKNSRvprEH4GpaKchyxaXQ=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=If8p329ev/5jSIU1u1ZxqBT3uiGqz6BXRqcd92DB71WI/Fz5avcvCg2ltC6g0WiVn7 Hg9ioVRBMzKE/6DJf5hKedIRAsW/CXmf1hYHubZntzj3wTvrR5MnAaXTxpGwX8P2I5gA N5scPyaGdYYYpYDzlPZzlgIV/DQgpl5W1x89U=
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

This patch series introduces the notion of memory access permissions per
page, overlaid (or rather, laid underneath) the memory types, for independent
control and memory event handling of faults based on the page types.

Access permission violations are set to the memory event handler for
resolution.

The permissions provide independent read, write, and execute permissions,
and are currently only implemented for Intel EPT.

Descriptions:
1: Sends memory access page faults in HVM to the memory event interface
2: Establishes the p2m interface changes to accommodate access permissions
3: Domain creation can require an access handler
4: EPT and interface changes
5: libxc changes for the new memory events and HVM operations

Thanks

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH 0 of 5] mem_access: introduction of per-page access c