From: Doug McNaught <doug@wireboard.com>
To: Mihai Moise <mcartoaj@mat.ulaval.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: adding a system call
Date: 09 Jan 2001 14:17:26 -0500 [thread overview]
Message-ID: <m3snmsbkmx.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <200101091441.JAA12925@taylor.mat>
In-Reply-To: Mihai Moise's message of "Tue, 9 Jan 2001 09:41:21 -0500 (EST)"
Mihai Moise <mcartoaj@mat.ulaval.ca> writes:
> My system call idea is to allow a superuser process to request a mmap on
> behalf of an user process. To see how this would be useful, let us consider
> svgalib.
[...]
> With my new system call, a superuser process can set the graphics mode in a
> safe manner and then ask for an mmap of the video array into the application
> data segment.
Ummm, couldn't the the root process open the video device, then pass
the file descriptor (via AF_UNIX socket) to the user process? The
user process would then call mmap() on the open file descriptor.
I'm not *completely* sure this would work, but it would avoid creating
a new system call if so.
-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 14:41 adding a system call Mihai Moise
2001-01-09 19:17 ` Doug McNaught [this message]
2001-01-09 19:34 ` Brian Pomerantz
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 15:14 mohit verma
2011-02-22 15:18 ` mohit verma
2011-02-22 17:50 ` Mulyadi Santosa
2011-02-22 18:01 ` mohit verma
2011-02-22 18:10 ` Mulyadi Santosa
2011-02-22 18:19 ` mohit verma
2011-02-22 18:39 ` Mulyadi Santosa
2011-02-22 18:44 ` mohit verma
2011-02-22 21:21 ` Anuz Pratap Singh Tomar
2001-01-09 0:49 Mihai Moise
2001-01-09 14:56 ` David Woodhouse
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=m3snmsbkmx.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcartoaj@mat.ulaval.ca \
/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.