Ok, so now it's time to reveal the new 'device' I've been working on
that I mentioned a few days ago. It is in fact the MA780 multi-port
memory as used by the VAX-11/782. Simulator source is now on Github and
binaries (for Win32) are available on my website along with a guide on
how to setup VAX/VM
> On May 19, 2017, at 6:15 PM, Matt Burke wrote:
>
> Ok, so now it's time to reveal the new 'device' I've been working on
> that I mentioned a few days ago. It is in fact the MA780 multi-port
> memory as used by the VAX-11/782. Simulator source is now on Github and
> binaries (for Win32) are ava
Interesting! Thanks for let us know about MP version of VAX-11/780. Will it be
787/789 emulation (VAX-11/785)? How about 784 (4 processors)? I recommend
atomic variables for interlocking. Check C++ reference for more information. It
requires least C++11 revisions (least GCC version 4.7). Also it
> On May 21, 2017, at 10:54 AM, Tim Stark wrote:
>
> Interesting! Thanks for let us know about MP version of VAX-11/780. Will it
> be 787/789 emulation (VAX-11/785)? How about 784 (4 processors)? I recommend
> atomic variables for interlocking.
Instead of relying on exotic C features, it migh
>> On May 20, 2017, at 12:00 PM, Paul Koning wrote:
>>
>> Interesting. So you have the two CPUs as two processes? I wonder if doing
>> them as threads in a single process might be more straightforward. I did an
>> implementation of dual CPU CDC 6000 emulation that way (an extension to Tom
>
On 21/05/2017 15:54, Tim Stark wrote:
> Interesting! Thanks for let us know about MP version of VAX-11/780. Will it
> be 787/789 emulation (VAX-11/785)? How about 784 (4 processors)? I recommend
> atomic variables for interlocking. Check C++ reference for more information.
> It requires least C+
On 25/05/2017 04:03, Sergey Oboguev wrote:
> Superficially looking at (AS)MP VMS code, it appears that the
> following should (hopefully) suffice for correct operation:
>
> 1. BBSSI and BBCCI should acquire a lock when accessing the memory
> location. A simplistic implementation may use one lock fo
> On May 25, 2017, at 6:51 PM, Matt Burke wrote:
>
> On 25/05/2017 04:03, Sergey Oboguev wrote:
>> Superficially looking at (AS)MP VMS code, it appears that the following
>> should (hopefully) suffice for correct operation:
>>
>> 1. BBSSI and BBCCI should acquire a lock when accessing the memo
Matt Burke wrote:
> I probably should have researched memory barriers a bit more.
> I knew a little bit about them but wasn't sure if they were needed here.
> The problem may also exist for the rest of the shared memory.
For the purposes of running VMS, what really and ultimately matters is no
.
Congratulations!
By the way: Is there any progress with the CI project (HSC)?
Best regards,
Ulli
> -Ursprüngliche Nachricht-
> Von: Matt Burke
> Gesendet: Sa. 20.05.2017 00:15
> An: Simh Trailing-Edge Mailing List ,
> Betreff: [Simh] New simulator - VAX-11/782
>
10 matches
Mail list logo
