public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Miguel Botón" <mboton@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] x86: ioport_{32|64}.c unification -v2
Date: Sun, 6 Jan 2008 16:04:17 +0100	[thread overview]
Message-ID: <20080106150417.GA14146@elte.hu> (raw)
In-Reply-To: <4780EC61.4020007@gmail.com>


* Miguel Botón <mboton@gmail.com> 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 check whether they properly block/allow port IO?

	Ingo

  reply	other threads:[~2008-01-06 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 14:57 [PATCH] x86: ioport_{32|64}.c unification -v2 Miguel Botón
2008-01-06 15:04 ` Ingo Molnar [this message]
2008-01-06 15:49   ` Miguel Botón
2008-01-06 16:17     ` Ingo Molnar
2008-01-06 16:33       ` Miguel Botón

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080106150417.GA14146@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mboton@gmail.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox