9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Anyone handy with Alpha assembler?
Date: Tue, 26 Aug 2008 17:24:27 +0200	[thread overview]
Message-ID: <9f3897940808260824k4e6059bdrb82bd4820ca8db81@mail.gmail.com> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB362@dolly.ntdom.cupdx>

On Tue, Aug 26, 2008 at 01:53, Benjamin Huntsman
<BHuntsman@mail2.cu-portland.edu> wrote:
> Anyone around here still familiar with Alpha assembler (and the Alpha kernel in general) willing to point me in the right direction?
>
> Supposing one wanted to implement instruction emulation for the BWX extensions, etc, like Tru64 and OpenVMS do, so that you can run the same binaries on EV4 and EV5, where would be the best place to hook in?  illegal0 in /sys/src/9/alphapc/l.s or illegal in /sys/src/9/alphapc/trap.c?
>
> Furthermore, how would one obtain the faulting instruction?  Best I can tell, it's the Ureg *ur passed to illegal in trap.c or 8(R30) from illegal0.
>
> Thanks in advance!
>
> -Ben
>

I think trap.c would be easier to work with or extend to other
instructions, l.s might give better performance. PALcode would be
probably the best option if it was properly patched during boot, but I
don't know where one might get apropriate SDK nowadays.

Anyway, If you want to check your code on an old Avanti-based EV45
Alpha, I am of service (unless I'll have to get rid of it when I move
to Scotland...)

Good luck with Alpha hacking, and remember about memory barriers...
("Program Counter is not reliable source of information about which
instruction caused the exception" - It's like a mantra in Alpha
manuals...)

-- 
Paweł Lasek

  reply	other threads:[~2008-08-26 15:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 23:23 [9fans] lguest on 2.6.25 Alex Lee
2008-08-25  4:26 ` ron minnich
2008-08-25  4:32 ` ron minnich
2008-08-25  4:58   ` Alex Lee
2008-08-25  9:03     ` John Soros
2008-08-25 10:56       ` erik quanstrom
2008-08-25 14:52         ` ron minnich
2008-08-25 14:52           ` ron minnich
2008-08-25 14:59           ` erik quanstrom
2008-08-25 15:09             ` ron minnich
2008-08-25 18:48             ` John Soros
2008-08-25 18:54               ` lucio
2008-08-25 20:39                 ` John Soros
2008-08-25 21:27                 ` John Soros
2008-08-25 23:53                   ` [9fans] Anyone handy with Alpha assembler? Benjamin Huntsman
2008-08-26 15:24                     ` Paweł Lasek [this message]
2008-08-26 17:56                       ` Benjamin Huntsman
2008-08-26 22:03                         ` Paweł Lasek
2008-08-26 23:09                           ` Benjamin Huntsman
2008-08-25 22:44               ` [9fans] lguest on 2.6.25 ron minnich
2008-08-26  6:44                 ` John Soros
2008-08-28  2:28                   ` Alex Lee
2008-08-28  2:38                     ` ron minnich
2008-08-28 12:06                       ` erik quanstrom
2008-08-28  8:21                     ` John Soros
2008-08-28 15:38                       ` ron minnich
2008-08-28 16:50                         ` John Soros
2008-08-28 16:59                           ` erik quanstrom
2008-08-28 17:24                         ` Alex Lee
2008-08-28 18:07                           ` John Soros
2008-08-28  8:27                     ` Richard Miller
2008-08-28 11:55                     ` erik quanstrom
2008-08-28 17:34                       ` Alex Lee
2008-08-28  2:39                   ` ron minnich

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=9f3897940808260824k4e6059bdrb82bd4820ca8db81@mail.gmail.com \
    --to=pawel.lasek@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).