From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
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 14:02:46 -0800 [thread overview]
Message-ID: <200801311402.46833.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <47A2086F.2040501@zytor.com>
On Thursday, January 31, 2008 9:42 am H. Peter Anvin wrote:
> 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").
For legacy memory, we actually have /sys/bus/pci/<busno>/legacy_mem
(though ia64 may be the only supported platform). It's actually
required on some arches due to the way this space is allocated across
the system.
Jesse
next prev parent reply other threads:[~2008-01-31 22:10 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
2008-01-31 22:02 ` Jesse Barnes [this message]
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=200801311402.46833.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox