From: Philipp Rumpf <prumpf@inwestnet.de>
To: "HOLBROOK,SCOTT HP-FtCollins,ex1\"" <scott_holbrook@am.exch.hp.com>
Cc: "'willy@thepuffingroup.com'" <willy@thepuffingroup.com>,
"'parisc-linux@thepuffingroup.com'"
<parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] code 28 trap
Date: Fri, 25 Feb 2000 22:49:34 +0100 [thread overview]
Message-ID: <20000225224934.D812@abacus.local> (raw)
In-Reply-To: <E97137CF9A25D311902E00A0C9F484E0027985F4@xfc03.fc.hp.com>; from scott_holbrook@am.exch.hp.com on Fri, Feb 25, 2000 at 01:23:51PM -0700
> > Years ago I wrote an unaligned load/store emulator (trap handler) for
> > a port of an evil OS to PA-RISC. I still have the code -- it would take
> > a little bit of work to massage it into a real low-level trap handler,
> > but that task should be very straight-forward.
>
> The code I have is for PA-RISC running in little-endian mode. There would
> be some additional work to make it bit-endian.
>
> Do you just love endian issues?
Well, I've got an unaligned handler for another architecture here, the tricky
part is to parse the instructions, and not forget about side-effects of ,M
modifiers.
As for how the code would be run, the most likely way would be to call it
in virtual mode with interrupts disabled and pass in a pointer to a pt_regs
(defined in include/asm/ptrace.h) structure.
Philipp Rumpf
next prev parent reply other threads:[~2000-02-25 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 20:23 [parisc-linux] code 28 trap HOLBROOK,SCOTT (HP-FtCollins,ex1)
2000-02-25 21:49 ` Philipp Rumpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-26 0:35 John Marvin
2000-02-26 0:53 ` Philipp Rumpf
2000-02-25 20:42 Mike Hibler
2000-02-25 20:17 HOLBROOK,SCOTT (HP-FtCollins,ex1)
2000-02-25 2:59 Grant Grundler
2000-02-25 3:49 ` willy
2000-02-25 20:36 ` Grant Grundler
2000-02-25 22:03 ` Philipp Rumpf
2000-03-03 21:53 ` Thomas Bogendoerfer
2000-02-25 23:17 ` Philipp Rumpf
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=20000225224934.D812@abacus.local \
--to=prumpf@inwestnet.de \
--cc=parisc-linux@thepuffingroup.com \
--cc=scott_holbrook@am.exch.hp.com \
--cc=willy@thepuffingroup.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