From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: load-store emulation with SIGSEGV
Date: Fri, 17 Oct 2003 18:54:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106641693501580@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106634457403703@msgid-missing>
>>>>> On Fri, 17 Oct 2003 11:16:41 -0700, "Jim Hull" <jim.hull@hp.com> said:
Jim> Matt Chapman wrote:
>> Yep, I do similar things in a virtual machine that I wrote.
>> Here are some notes in case you've overlooked some of the finer
Jim> details
>> (and perhaps I've overlooked some of the finer details as well :)).
>> Incrementing the IP:
sc-> sc_ip += ((sc->sc_ip & 0xf) = 2) ? 0xe : 1;
Jim> I think there's one scenario where this won't work. If it's possible
Jim> for your signal handler to be invoked in cases where the instruction
Jim> you're trying to skip over is a two-slot "L+X" instruction from an MLX
Jim> bundle (e.g., movl or brl), then the "slot" bits of sc_ip will be 1,
Jim> you'll increment them to 2, and when you return to slot 2 of the MLX
Jim> bundle you'll immediately take an Illegal Instruction fault.
Jim> Probably most "skip an instruction" signal handlers don't need to worry
Jim> about this case, because they'll always be pointing at an ordinary
Jim> single-slot instruction, but it's something to be aware of.
The kernel's ia64_increment_ip() function in arch/ia64/kernel/ptrace.c
could be used as a template here. Of course, you do need to read the
bundle in order to determine whether it's an MLX template.
--david
prev parent reply other threads:[~2003-10-17 18:54 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
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 [this message]
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-106641693501580@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.