The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.
re: http://www.garlic.com/~lynn/2010e.htmL#32 Need tool to zap core http://www.garlic.com/~lynn/2010e.htmL#34 Need tool to zap core http://www.garlic.com/~lynn/2010e.htmL#38 Need tool to zap core old email menioning SIE in vm/811 (811 was a code name for 370/xa because architecture documents dated nov78) ... aka vmtool which was (originally) only for internal mvs/xa development and was never going to be released to customers. Also some discussion of difference between SIE in 3081 and Trout (trout was codename for 3090) http://www.garlic.com/~lynn/2006j.html#email810630 in this post http://www.garlic.com/~lynn/2006j.html#27 virtual memory above also mentions part of SIE poor performance on 3081 was that it had to be "paged in" (from the 3310/piccolo by the service processor). another old email mentioning SIE in 3090 http://www.garlic.com/~lynn/2003j.html#email831118 in this post http://www.garlic.com/~lynn/200ej.html#42 Flash 10208 another reference to SIE on 3090 still being expensive instruction http://www.garlic.com/~lynn/2007c.html#email860121 in this post http://www.garlic.com/~lynn/2007c.html#49 SVC the above discusses potentially disabling for i/o interrupts. as it mentions .... I had done something similar a decade earlier ... would dynamically change based on I/O interrupt rate crossing some threshhold. -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
