All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	linux-kernel@vger.kernel.org, davej@redhat.com, mingo@elte.hu,
	tglx@tglx.de
Subject: Re: [PATCH] x86: introduce /dev/mem restrictions with a config option
Date: Thu, 31 Jan 2008 09:42:07 -0800	[thread overview]
Message-ID: <47A2086F.2040501@zytor.com> (raw)
In-Reply-To: <20080131090839.7f610a6a@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Thu, 31 Jan 2008 17:53:04 +0100 (CET)
> Jan Engelhardt <jengelh@computergmbh.de> wrote:
> 
>> On Jan 30 2008 12:48, Arjan van de Ven wrote:
>>> Subject: [PATCH] x86: introduce /dev/mem restrictions with a config
>>> option
>>>
>>> This patch introduces a restriction on /dev/mem: Only non-memory can
>>> be read or written unless the newly introduced config option is set.
>> Would not it be nicer to add a /dev/pcimem that implements the given 
>> restrictive semantics?
>>
>> Maybe it's just wishful thinking, but I am dreaming of an
>> unprivileged X, and /dev/pcimem (owned by an 'x11' user or so) would
>> be a step in that direction.
> 
> /dev/pcimem is wrong; X can use the exact bar in sysfs already.
> This is more for compatibility with legacy X
> 

Legacy X, and non-BAR X memory (originally ISA, of course; now probably 
more often "stolen system memory").

	-hpa

  reply	other threads:[~2008-01-31 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 20:48 [PATCH] x86: introduce /dev/mem restrictions with a config option Arjan van de Ven
2008-01-31 16:53 ` Jan Engelhardt
2008-01-31 17:08   ` Arjan van de Ven
2008-01-31 17:42     ` H. Peter Anvin [this message]
2008-01-31 22:02       ` Jesse Barnes
2008-01-31 22:05         ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 14:04 devzero
2008-01-31 14:41 ` Arjan van de Ven

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=47A2086F.2040501@zytor.com \
    --to=hpa@zytor.com \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@tglx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.