From: Andrea Arcangeli <andrea@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
ak@muc.de, Alan Cox <alan@lxorguk.ukuu.org.uk>,
george anzinger <george@mvista.com>, Jeff Dike <jdike@karaya.com>,
Stephen Hemminger <shemminger@osdl.org>,
Bill Davidsen <davidsen@tmr.com>
Subject: Re: [RFC] linux-2.5.44_vsyscall-proc_A0
Date: Wed, 23 Oct 2002 03:51:58 +0200 [thread overview]
Message-ID: <20021023015157.GI11242@dualathlon.random> (raw)
In-Reply-To: <1035336772.954.95.camel@cog>
On Tue, Oct 22, 2002 at 06:32:51PM -0700, john stultz wrote:
> All
> Well, just to fan the flames a bit, here is a patch (applies on top of
> vsyscall_A1)that adds a /proc/vsyscall interface which gives the address
> of the vsyscall page if its mapped in. This could be then used to help
> the UML folks virtualize things, as well as give a cross platform
> interface that could be used. There's probably a better place in /proc
> for this, but this is just something to start from.
>
> Let me know your thoughts.
there is no point for this last patch. The vsyscall_ptr is the vsyscall
number.
This is equivalent to a proc that shows the syscall number of
sys_gettimeofday, useless, cat on unistd.h and vsyscall.h will avoid a
waste of kernel mem.
the uml folks need to replace the vsyscalls, they just know their
address, like they just know the syscall number of sys_gettimeofday.
Andrea
next prev parent reply other threads:[~2002-10-23 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 1:30 [PATCH] linux-2.5.44_vsyscall_A1 john stultz
2002-10-23 1:31 ` [EXAMPLE CODE] linux-2.5.43_vsyscall_A1 john stultz
2002-10-23 1:32 ` [RFC] linux-2.5.44_vsyscall-proc_A0 john stultz
2002-10-23 1:51 ` Andrea Arcangeli [this message]
2002-10-23 2:03 ` [PATCH] linux-2.5.44_vsyscall_A1 Jeff Garzik
2002-10-23 4:08 ` H. Peter Anvin
2002-10-23 16:56 ` john stultz
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=20021023015157.GI11242@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=george@mvista.com \
--cc=jdike@karaya.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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