Ingo Molnar wrote:
> * Miguel Botón <[EMAIL PROTECTED]> wrote:
>
>>> in what way have you tested it? Have you tried iopl() and ioperm()
>>> syscalls to check whether they properly block/allow port IO?
>> I made a little app to check that iopl() and ioperm() were working
>> properly.
>
> cool, t
* Miguel Botón <[EMAIL PROTECTED]> wrote:
> > in what way have you tested it? Have you tried iopl() and ioperm()
> > syscalls to check whether they properly block/allow port IO?
>
> I made a little app to check that iopl() and ioperm() were working
> properly.
cool, thx. Could you check wheth
Ingo Molnar wrote:
> * Miguel Botón <[EMAIL PROTECTED]> wrote:
>
>> ioport_{32|64}.c unification.
>>
>> This patch unifies the code from the ioport_32.c and ioport_64.c
>> files.
>>
>> Tested and working fine with i386 and x86_64 kernels.
>
> in what way have you tested it? Have you tried iopl()
* Miguel Botón <[EMAIL PROTECTED]> wrote:
> ioport_{32|64}.c unification.
>
> This patch unifies the code from the ioport_32.c and ioport_64.c
> files.
>
> Tested and working fine with i386 and x86_64 kernels.
in what way have you tested it? Have you tried iopl() and ioperm()
syscalls to che
ioport_{32|64}.c unification.
This patch unifies the code from the ioport_32.c and ioport_64.c files.
Tested and working fine with i386 and x86_64 kernels.
Signed-off-by: Miguel Botón <[EMAIL PROTECTED]>
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 0903bbf..92d9ac6 100
5 matches
Mail list logo