Re: Tagged memory (was Re: Memory Upgrade)

Leif,
after watching your posts for the last year or so, a thought strikes me -
you definitely know a lot about AS/400 (certainly a lot more than me); you
definitely despise the platform very much; and you definitely know lots of
easy ways to circumvent security and asset protection etc.
Why won't you create an ultimate virus program for AS/400 - this should be
easy for you, this will prove your point and this will wipe out system from
the market ?

    Alexei Pytel,
     as usual, speaking only for myself





                    "Leif Svalgaard"
                    <leif@attglobal.net       To:     <midrange-l@midrange.com>
                    >                         cc:
                    Sent by:                  Subject:     Re: Tagged memory 
(was Re: Memory
                    midrange-l-admin@mi        Upgrade)
                    drange.com


                    09/27/2001 01:55 PM
                    Please respond to
                    midrange-l





From: Alexei Pytel <pytel@us.ibm.com>
> > 2) the tagged pointer protection is not hardware, but is done in
> > software, so need not contribute to make memory more expensive.
>
> With all respect, the tagged pointer protection *is* hardware.
> It could in theory be done by software, but it would incur unacceptable
> overhead.
>

Well, the RISC code to check if a pointer is valid is:
LQ R6, addr  ;  load pointer into R6, R7. set bit in exception reg if no
tag
TXER nn ; trap if no tag

to me that is software. The trap can be disabled by replacing the TXER
instruction by a NOOP.

The overhead is the TXER instruction and is not unacceptable.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.