[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] x86-64 linux' sys_ioperm()

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 02 Jun 2006 11:49:46 +0200
Delivery-date: Fri, 02 Jun 2006 02:49:24 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Follow-Ups:
- Re: [Xen-devel] x86-64 linux' sys_ioperm()
  - From: Keir Fraser

Prev by Date: [Xen-devel] Documentation suggestions and VMX success report...
Next by Date: [Xen-devel] [PATCH, resend] replacement for noirqdebug hack
Previous by thread: [Xen-devel] Documentation suggestions and VMX success report...
Next by thread: Re: [Xen-devel] x86-64 linux' sys_ioperm()
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.