Invalid channel program checks

Sam Golob noted some incompatibilities wrt channel program checks in 
a recent conversation.  I have investigated this, and it appears 
that this is a general problem.  We have had the same issue with
the NOP ccw, but there are several others that have the same problem.
The issue is that the hercules channel code checks data address 
validity and access type before any data transfer takes place.  
I am not sure exactly how yet, but I want to add a (control unit 
based) table, with an entry for every ccw indicating if that ccw
causes data transfer.  This table can be indexed into in channel.c, 
before data address validity checks occur.
Does this seem reasonable?

jj


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/JjlUgA/vN2EAA/kG8FAA/dpFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
hercules-advocacy-unsubscribe-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/