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

>>> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 02.06.06 12:06 >>>
>
>On 2 Jun 2006, at 10:49, Jan Beulich wrote:
>
>> 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
>
>Nope. It's something that needs bringing in sync with i386.

Here we go.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

(if signing off on something almost entirely copied from elsewhere makes any 
sense at all)

xenlinux-x86_64-sys-ioperm.patch
Description: Text document

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

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] x86-64 linux' sys_ioperm(), Jan Beulich Re: [Xen-devel] x86-64 linux' sys_ioperm(), Keir Fraser Re: [Xen-devel] x86-64 linux' sys_ioperm(), Jan Beulich <=

Previous by Date:

[Xen-devel] Re: new load balancer scheduler, Emmanuel Ackaouy

Next by Date:

Re: [Xen-devel] A few outstanding xenstore/hotplug issues..., Matt Ayres

Previous by Thread:

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

Next by Thread:

[Xen-devel] [PATCH, resend] replacement for noirqdebug hack, Jan Beulich

Indexes:

[Date] [Thread] [Top] [All Lists]