From: Karim Yaghmour <karim@opersys.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
"Frank Ch. Eigler" <fche@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
SystemTAP <systemtap@sources.redhat.com>,
Satoshi Oshima <soshima@redhat.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Tom Zanussi <zanussi@us.ibm.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
William Cohen <wcohen@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Does this work? "dcprobes" an x86-hack simple djprobes-equivalent?
Date: Mon, 25 Sep 2006 00:46:32 -0400 [thread overview]
Message-ID: <45175F28.3090109@opersys.com> (raw)
In-Reply-To: <45163D3D.4010108@opersys.com>
Slight binary typo ...
Karim Yaghmour wrote:
> Of course, this means hardwiring a multiplexing function at
> 0xCCCC,0xCCCCCCCC, if that makes any sense (offset 0xCCCCCCCC
> of code segment entry 7,099 of the LDT with an RPL of 1).
Actually 0xCCCC is code segment entry 6,553 of the LDT with an
RPL of 0.
Karim
--
President / Opersys Inc.
Embedded Linux Training and Expertise
www.opersys.com / 1.866.677.4546
next prev parent reply other threads:[~2006-09-25 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 8:09 Does this work? "dcprobes" an x86-hack simple djprobes-equivalent? Karim Yaghmour
2006-09-25 4:46 ` Karim Yaghmour [this message]
2006-09-28 2:30 ` Masami Hiramatsu
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=45175F28.3090109@opersys.com \
--to=karim@opersys.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=soshima@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox