Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs)

From	"H. Peter Anvin" <hpa@zytor.com>
Newsgroups	linux.kernel
Subject	Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs)
Date	2016-09-21 02:30 +0200
Message-ID	<sjDAe-1MD-21@gated-at.bofh.it> (permalink)
References	<sa8YG-5nC-19@gated-at.bofh.it> <sa9UK-619-15@gated-at.bofh.it> <sacSB-84O-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

The more I'm thinking about this, why don't we simply have these (the
various possible vdsos as well as vvar) as actual files in sysfs instead
of introducing a new filesystem?  I don't believe sysfs actually has to
be mounted in order for sysfs files to have an inode.

It could also be in procfs, I guess, but sysfs probably makes more sense.

I'm thinking something like:

/sys/kernel/vdso/{i386,x86_64,x32,vvar}

Not only would this let the container people and so on do weird things
much easier, but it ought to eliminate a whole slew of special cases.


	-hpa

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) "H. Peter Anvin" <hpa@zytor.com> - 2016-09-21 02:30 +0200
  Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) "H. Peter Anvin" <hpa@zytor.com> - 2016-09-21 02:40 +0200
    Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) Andy Lutomirski <luto@amacapital.net> - 2016-09-21 03:00 +0200
      Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) "H. Peter Anvin" <hpa@zytor.com> - 2016-09-21 03:10 +0200
        Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) "H. Peter Anvin" <hpa@zytor.com> - 2016-09-21 03:20 +0200
          Re: [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) Andy Lutomirski <luto@amacapital.net> - 2016-09-21 08:50 +0200

csiph-web