All of lore.kernel.org
 help / color / mirror / Atom feed
From: arvid.brodin@enea.com (Arvid Brodin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Build scatterlist covering a process' text segment?
Date: Wed, 25 May 2011 22:27:40 +0200	[thread overview]
Message-ID: <4DDD663C.4060201@enea.com> (raw)
In-Reply-To: <4DDAE865.6000608@enea.com>

Arvid Brodin wrote:
> Hi,
> 
> How do I build a scatterlist covering the text segment of a process? I have
> found (struct task_struct).mm->start_code and ->end_code, that gives the address
> (in some - unknown to me - address space) of the text segment. Since my try to
> convert these addresses to an sglist:
> 
> 	sg_init_one(&sg, task->mm->start_code, <length>);
> 
> failed miserably, I'm guessing these addresses need to be converted to some
> address space compatible with sg_init_one()/sg_set_buf() before use? (I probably
> need to search for pages containing these addresses?)
> 

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?

-- 
Arvid Brodin
Enea Services Stockholm AB

  reply	other threads:[~2011-05-25 20:27 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 [this message]
2011-05-26  4:02   ` Mulyadi Santosa
2011-05-27 21:58     ` Arvid Brodin
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=4DDD663C.4060201@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.