 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] user mode access to kernel memory
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] user mode access to kernel memory |
| From: | "Jan Beulich" <JBeulich@xxxxxxxxxx> |
| Date: | Fri, 29 Jan 2010 10:12:29 +0000 |
| Delivery-date: | Fri, 29 Jan 2010 02:13:33 -0800 |
| 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 |
Tools like crash want to read /proc/mem to get access to RAM. This isn't allowed under Xen due to the physical/machine address spaces being distinct. I wonder, however, why this also isn't permitted through privcmd (or really, why direct_remap_pfn_range() rejects DOMID_SELF, but permits the resolved domain ID to be passed). Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Pasi Kärkkäinen |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden |
| Previous by Thread: | [Xen-devel] tmem - really default to on?, Jan Beulich |
| Next by Thread: | [Xen-devel] PoD issue, Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
