From: Dmitry Safonov <dsafonov@virtuozzo.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [RFC 1/3] x86/vdso: create vdso file, use it for mapping
Date: Mon, 29 Aug 2016 12:50:42 +0300 [thread overview]
Message-ID: <fdc408f7-f5c1-3c00-e344-d7c2ae1da652@virtuozzo.com> (raw)
In-Reply-To: <CALCETrWmDFiK0HACo0-dJgtFOijxzr=ApJoTNMDHmb+P=9=_TA@mail.gmail.com>
On 08/29/2016 12:28 PM, Andy Lutomirski wrote:
> On Thu, Aug 25, 2016 at 8:21 AM, Dmitry Safonov <dsafonov@virtuozzo.com> wrote:
>> I added here a new in-kernel fs with ramfs-like options.
>> Created vdso file in this fs (yet for testing, only 64-bit vdso).
>> Mapped this file to process's mm on setup_additional_pages.
>> Just for testing purpose it's done only for specific UID.
>
> I'm wondering whether all this code could be easily moved into the
> core special mapping helpers so that all special mappings get the same
> benefit. We could embed a struct file * (or struct inode or whatever)
> in special_mapping if needed.
Hmm, yes, I guess. The only thing -- we'll still need per-arch changes
to initialize those files on booting. But that looks like the proper
generic place to move this code.
> Also, could this be simplified to use anon_inode?
>
> (I'm not a VFS expert at all, so I could be way off base.)
Well, I'll try to do the second version with anon_inode.
Thanks,
Dmitry
next prev parent reply other threads:[~2016-08-29 10:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:21 [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) Dmitry Safonov
2016-08-25 15:21 ` [RFC 1/3] x86/vdso: create vdso file, use it for mapping Dmitry Safonov
2016-08-25 19:49 ` Dmitry Safonov
2016-08-25 20:05 ` Dmitry Safonov
2016-08-28 20:14 ` Cyrill Gorcunov
2016-08-29 9:18 ` Dmitry Safonov
2016-08-29 9:28 ` Andy Lutomirski
2016-08-29 9:50 ` Dmitry Safonov [this message]
2016-08-30 14:58 ` Andy Lutomirski
2016-09-03 0:08 ` Al Viro
2016-08-30 14:33 ` Oleg Nesterov
2016-08-30 14:53 ` Dmitry Safonov
2016-09-03 0:13 ` Al Viro
2016-09-03 0:20 ` Al Viro
2016-09-03 7:32 ` Dmitry Safonov
2016-08-25 15:21 ` [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe Dmitry Safonov
2016-08-29 22:58 ` Steven Rostedt
2016-08-29 22:59 ` Steven Rostedt
2016-08-29 23:01 ` Dmitry Safonov
2016-08-30 14:37 ` Oleg Nesterov
2016-08-30 21:15 ` Steven Rostedt
2016-08-31 12:07 ` Oleg Nesterov
2016-08-30 14:57 ` Srikar Dronamraju
2016-08-25 15:21 ` [RFC 3/3] uprobe: add vdso support Dmitry Safonov
2016-08-25 20:49 ` [RFC 0/3] Put vdso in ramfs-like filesystem (vdsofs) H. Peter Anvin
2016-08-25 22:53 ` Dmitry Safonov
2016-08-25 23:00 ` H. Peter Anvin
2016-08-26 11:16 ` Dmitry Safonov
2016-08-26 14:32 ` Andy Lutomirski
2016-08-26 14:42 ` Dmitry Safonov
2016-08-26 14:44 ` Dmitry Safonov
2016-09-21 0:22 ` H. Peter Anvin
2016-09-21 0:32 ` H. Peter Anvin
2016-09-21 0:54 ` Andy Lutomirski
2016-09-21 1:07 ` H. Peter Anvin
2016-09-21 1:17 ` H. Peter Anvin
2016-09-21 6:39 ` Andy Lutomirski
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=fdc408f7-f5c1-3c00-e344-d7c2ae1da652@virtuozzo.com \
--to=dsafonov@virtuozzo.com \
--cc=0x7f454c46@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®