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

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

To: "Jan Beulich" <jbeulich@xxxxxxxxxx>
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 2 Jun 2006 11:06:20 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 02 Jun 2006 03:06:41 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On 2 Jun 2006, at 10:49, Jan Beulich wrote:

Is there any reason other than lack of time during the initial portthat this function is not usingPHYSDEVOP_SET_IOBITMAP (like i386 is doing), but rather grants accessto all I/O ports by calling sys_iopl(3)? Jan


Nope. It's something that needs bringing in sync with i386.

 -- Keir


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

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

References:
- [Xen-devel] x86-64 linux' sys_ioperm()
  - From: Jan Beulich

Prev by Date: [Xen-devel] [PATCH, resend] x86-64 linux: don't use hlt instruction
Next by Date: Re: [Xen-devel] [PATCH, resend] blkfront: ioctls/geometry, 2.6
Previous by thread: [Xen-devel] x86-64 linux' sys_ioperm()
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®.