From: arvid.brodin@enea.com (Arvid Brodin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Build scatterlist covering a process' text segment?
Date: Fri, 27 May 2011 23:58:44 +0200 [thread overview]
Message-ID: <4DE01E94.8000505@enea.com> (raw)
In-Reply-To: <BANLkTim_mR5ns1N8J6HudGrwHZKJEBgDug@mail.gmail.com>
Mulyadi Santosa wrote:
> On 26/05/2011, Arvid Brodin <arvid.brodin@enea.com> wrote:
>> Am I correct in that the addresses in (struct task_struct).mm->start_code
>> and
>> ->end_code belong to the address space of the process whose task_struct I'm
>> looking
>> at?
>
>
> I believe yes....
>
Ok. And looking at e.g. sg_set_buf(), the scatterlist expects a kernel virtual
address (it uses virt_to_page() on its "buf" parameter internally, which
requires a kernel virtual adress, if I understand correctly).
There seems to be no way to map process adresses to kernel addresses. (Well I
guess one could follow the page tables to get the physical page, and then map
back to kernel space, but this only works as long as the memory is paged in.)
Please correct me if I'm wrong.
Perhaps a better idea is to do_mmap() the "exe_file", (struct mm_struct).exe_file?
I'm still confused about this though:
1) do_mmap() returns unsigned long - not the void * expected by sg_set_buf().
Is this a sign that I'm again mixing different address spaces, or is it ok
just to cast this?
2) I believe do_mmap() maps a file into the address space of the "current process",
and that this address space is also the one used in kernel space at any moment.
Is this correct, or is there an additional, kernel-only memory space that I
should map the file to instead? If so, how do I do that?
Thanks,
Arvid Brodin
Enea Services Stockholm AB
next prev parent reply other threads:[~2011-05-27 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 23:06 Build scatterlist covering a process' text segment? Arvid Brodin
2011-05-25 20:27 ` Arvid Brodin
2011-05-26 4:02 ` Mulyadi Santosa
2011-05-27 21:58 ` Arvid Brodin [this message]
2011-05-28 9:42 ` Mulyadi Santosa
2011-06-17 0:47 ` Arvid Brodin
2011-06-17 15:10 ` Jonathan Neuschäfer
2011-06-17 15:18 ` Metin KAYA
2011-06-17 17:59 ` Dave Hylands
2011-06-17 18:46 ` Jonathan Neuschäfer
2011-06-17 18:53 ` Dave Hylands
2011-06-17 19:00 ` Jonathan Neuschäfer
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=4DE01E94.8000505@enea.com \
--to=arvid.brodin@enea.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).