All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: load-store emulation with SIGSEGV
Date: Thu, 16 Oct 2003 23:57:53 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106634869106973@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106634457403703@msgid-missing>

>>>>> On Thu, 16 Oct 2003 23:49:20 +0100, "R. Lake" <rich@lakes.plus.com> said:

  Rich> I'm investigating a means of emulating causes of SEGV where
  Rich> they can be isolated from genuine failure. For example, a rule
  Rich> stating a load from address 0x100 "loads" the value 42 into
  Rich> the target register.

  Rich> A simple test to decode the instruction, locate and modify the
  Rich> operand register in the sigcontext or backing store, then
  Rich> increment sc_ip shows the expected behaviour. But, for
  Rich> practical usage I'm not entirely confident I've taken all the
  Rich> necessary steps to return to the kernel in a robust manner.
  Rich> I've thus far taken insight from the unaligned handler albeit
  Rich> without altering the psr.ri field. So, my question is... am I
  Rich> missing a vital stage to this process, some piece of
  Rich> information the kernel expects to receive when avoiding the
  Rich> faulting instruction?

I'm not entirely sure I understand what you're trying to do and
whether you're doing it in the kernel or user (signal-handler).  If
the latter, adjusting the sc_ip should be sufficient (the slot number
is encoded in bits 0 and 1 of sc_ip).

	--david

  parent reply	other threads:[~2003-10-16 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 22:49 load-store emulation with SIGSEGV R. Lake
2003-10-16 22:49 ` R. Lake
2003-10-16 22:49 ` R. Lake
2003-10-16 22:51 ` R. Lake
2003-10-16 22:51 ` R. Lake
2003-10-16 23:57 ` David Mosberger [this message]
2003-10-17  8:13 ` R. Lake
2003-10-17 15:11 ` Matt Chapman
2003-10-17 18:16 ` Jim Hull
2003-10-17 18:54 ` David Mosberger

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=marc-linux-ia64-106634869106973@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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.