From: manojnayak2005@gmail.com (Manoj Nayak)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel_thread() causes segfault
Date: Tue, 22 Mar 2016 15:44:23 +0530 [thread overview]
Message-ID: <CAOsfsFL4-syi0szL81hKfMW2Ln4rCUEp9rf1O50aNJqb3rM3Tw@mail.gmail.com> (raw)
What is the usecase here ? Do we need to share the entire process address
space to a kernel thread ?
If address space sharing between userspace thread and kernel thread space
is the whole idea then we can mmap process address space and do
get_user_pages() to allocate physcial page and pin it.
kernel thread can do kmap() and kumap() to use the pages from process
address space.
http://lxr.free-electrons.com/source/fs/aio.c?v=3.8#L99
Regards
Manoj Nayak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160322/e025e14b/attachment.html
next reply other threads:[~2016-03-22 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 10:14 Manoj Nayak [this message]
2016-03-22 11:21 ` kernel_thread() causes segfault Shashank Khasare
2016-03-22 17:13 ` Valdis.Kletnieks at vt.edu
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 13:45 Manoj Nayak
2016-03-21 6:16 Shashank Khasare
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=CAOsfsFL4-syi0szL81hKfMW2Ln4rCUEp9rf1O50aNJqb3rM3Tw@mail.gmail.com \
--to=manojnayak2005@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).