From: vamsi krishna <vamsi.krishnak@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: roland@redhat.com
Subject: Forcing kernel to avoid vDSO mapping.
Date: Wed, 3 Aug 2005 21:51:04 +0530 [thread overview]
Message-ID: <3faf05680508030921277d78a9@mail.gmail.com> (raw)
Hello All,
Sorry to interrupt you.
There seem to be some architecture specific problems using ptrace in
the vDSO segment on IA32, ptrace and read fails from this segment with
BAD ADDRESS.
I was just wondering if there could be any why we can tell kernel not
to map this vDSO for optimization of system call overhead.
Your kind help and effort regarding this issue is greatly appreciated.
Thanks a lot.
Regards,
Vamsi kundeti
reply other threads:[~2005-08-03 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3faf05680508030921277d78a9@mail.gmail.com \
--to=vamsi.krishnak@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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.