 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] x86-64 linux' sys_ioperm()
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] x86-64 linux' sys_ioperm() |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Fri, 02 Jun 2006 11:49:46 +0200 |
| Delivery-date: | Fri, 02 Jun 2006 02:49:24 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| 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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Is there any reason other than lack of time during the initial port that this function is not using PHYSDEVOP_SET_IOBITMAP (like i386 is doing), but rather grants access to all I/O ports by calling sys_iopl(3)? 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: | [Xen-devel] Documentation suggestions and VMX success report..., George Styles |
|---|---|
| Next by Date: | [Xen-devel] [PATCH, resend] replacement for noirqdebug hack, Jan Beulich |
| Previous by Thread: | [Xen-devel] Documentation suggestions and VMX success report..., George Styles |
| Next by Thread: | Re: [Xen-devel] x86-64 linux' sys_ioperm(), Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
