public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Hellwig <hch@infradead.org>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: NUMA-Q sys_ioperm()/sys_iopl()
Date: Wed, 30 Apr 2003 05:57:17 -0700	[thread overview]
Message-ID: <20030430125717.GE8978@holomorphy.com> (raw)
In-Reply-To: <20030430135521.A5383@infradead.org>

On Wed, Apr 30, 2003 at 05:28:25AM -0700, William Lee Irwin III wrote:
>> NUMA-Q cannot support these operations without significant
>> infrastructure to emulate a global port io space for userspace to
>> manipulate, possibly even with hooks into the scheduler.
>> Not only are the applications depending on this particular form of
>> privilege elevation generally inappropriate uses of these machines
>> (they are large "server-class" machines, typically shipped and run
>> headless), but the devices typically managed with these interfaces
>> are already explicitly unsupported in UNIX configurations.
>> This patch removes sys_iopl() and sys_ioperm() support conditional on
>> #ifdef CONFIG_X86_NUMAQ to prevent the device register corruption
>> condition without significant impact on core i386 support.

On Wed, Apr 30, 2003 at 01:55:21PM +0100, Christoph Hellwig wrote:
> Please use cond_syscall to autogenerate the stubs, and make the compilation
> of /ioport.c conditional on !CONFIG_X86_NUMAQ.

Never heard of it before. Get a hold of me in the obvious way to fill
me in.

Thanks.

-- wli

      reply	other threads:[~2003-04-30 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 12:28 NUMA-Q sys_ioperm()/sys_iopl() William Lee Irwin III
2003-04-30 12:55 ` Christoph Hellwig
2003-04-30 12:57   ` William Lee Irwin III [this message]

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=20030430125717.GE8978@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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