Lines Matching refs:be

53 lwarx/stwcx), either *both* SAVINGS_ACCT(r3) and CURRENT_ACCT(r3) will be
54 updated, or neither will be updated.
57 transaction, the transaction will be aborted by the CPU.  Register and memory
59 'tbegin+4'.  The branch to abort_handler will be taken this second time; the
77 Syscalls made from within an active transaction will not be performed and the
78 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
85 effects will be persistent, independent of transaction success or failure.  No
89 Care must be taken when relying on syscalls to abort during active transactions
107 delivered.  For future compatibility the MSR.TS field should be checked to
119 However, basic signal handlers don't need to be aware of transactions
123 from the second ucontext.  This will be necessary for crash handlers to
141    fprintf(stderr, "Transaction to be restarted at 0x%llx, but "
151 When in an active transaction that takes a signal, we need to be careful with
157 stack pointer will be back at the tbegin but our in memory stack won't be valid
162 state.  This ensures that the signal context (written tm suspended) will be
165 signal will be rolled back anyway.
186 These can be checked by the user program's abort handler as TEXASR[0:7].  If
188 a TM_CAUSE_ALIGNMENT will be persistent while a TM_CAUSE_RESCHED will not.
195 presented).  The transaction cannot then be continued and will take the failure
196 handler route.  Furthermore, the transactional 2nd register state will be
197 inaccessible.  GDB can currently be used on programs using TM, but not sensibly