HP3000-L Archives

October 2008, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Peter M. Eggers" <[log in to unmask]>
Reply To:
Peter M. Eggers
Date:
Fri, 31 Oct 2008 11:44:15 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Hardware Emulation

As has been pointed out, QEMU has had a PA-RISC project.  I don't know the
details, but it seems to me it was harder than expected due to things like
PA-RISC's ability to preload branches ahead of execution, and significant
hardware variations in the CPU design.  HP certainly has the talent and
resources to add PA-RISC support to QEMU.  So why not?  Are the purported
millions of dollars available, not available?  Does it not fit in with HP's
business plan?  QEMU is already a highly reguarded hardware emulator for a
variety of architectures, great and small..  Adding another architecture to
it would greatly minimize the cost of developing one, and unlike a
commercial emulator, there is no chance that you are going to be held
hostage or have it abandoned due to some business plan.


Code and Data Pages

This is not an OS feature, it is a hardware feature!  It is a feature of the
HP3000 and other business servers and mainframes.  The Intel CPU's and their
clones did not support it for a long time, because their CPUs were designed
for PERSONAL COMPUTERS.  Linux has supported code and data page separation
for years, though it did intially have some pieces that performed some
"magic" by executing a data page.  A bit of knowledge and/or understanding
would be helpful here to have an intelligent discussion about this.


Files

Linux files are decent containers.  How they are accessed is a function of
the intrinsics.  Much of the controls that MPE exerts is due to the system
file label which I proposed would be just another Linux file with special
handling by the MPE layer.  This can be enforced using extended attributes
in Linux for all of the special files in MPE.  I think it is pretty secure,
but not absolutely certain.  Here is the description of how EAs should be
used in Linux: http://www.freedesktop.org/wiki/CommonExtendedAttributes  If
for some reason the security model for EAs in Linux is not sufficient to
keep hackers in check, I can assure you that SELinux is, but is a lot more
bother and complexity.


Where to Start?

How about create sample Linux user and home directory on a Linux with a
sample Linux directory structure to support MPE?

Then how about a command interpreter (shell) for the MPE Linux user to run
accessing the its Linux home directory, presenting an MPE view?

--------------------

James H. seems to have a grasp of the subject, though I may disagree with
him on some points.  Wirt is apparently keeping low and out of the line of
fire (the smartest "Windows Weenie" ;-) I know by far).  Alfredo apparently
lost interest years ago.  HP3000 lab people are probably under strict orders
to not get involved.  Is there anyone left capable, knowledgeable, and
interested?  I guess I may be getting tired of the boisterous arm waving,
and looking for some intellectual meat.  I do appreciate the honest
questions and concerns, no matter at what technical level.

Pete

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2