On 2016-10-18, at 13:45, Tony Harminc wrote: > > There is also the long-known performance problem with TRT (and TR) > that its definition requires that "Access exceptions are recognized > only for those bytes in the second operand which are actually > required. Access exceptions are not recognized for those bytes in the > first operand which are to the right of the first byte for which a > nonzero function byte is obtained." > Isn't the purpose of the "trial execution" to avoid page faults, at least on the destination operand? But woe be unto you if channel activity or other unserialized updates occur concurrently. (Or is that detected causing the trial execution to restart?)
-- gil
