Re: [PATCH] i386 vsyscall DSO implementation

[H. Peter Anvin]

David Mosberger wrote:
> 
>   >> To complete the picture, it would be nice if the kernel ELF
>   >> images were mappable files (either in /sysfs or /proc) and would
>   >> show up in /proc/PID/maps.  That way, a distributed application
>   >> such as a remote debugger could gain access to the kernel unwind
>   >> tables on a remote machine (assuming you have a remote
>   >> filesystem).
> 
>   hpa> How about /boot?
> 
> You mean a regular file?  I'm not sure whether this could be made to
> work.  The /proc/PID/maps entry (really: the vm_area for the kernel
> ELF images) would have to be created by the kernel, at a time when no
> real filesystem is available.  Also, since the kernel needs to store
> the data in kernel-memory anyhow, I don't think there is much point in
> storing it on disk as well.
> 

Perhaps I misunderstood the statement.  With "kernel ELF images" above,
I am now gathering you're talking about only the segments exported to
userspace (i.e. vsyscall code), not the kernel itself, which was my
original reading of that statement.

	-hpa