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
81 not be running in transactional state.  The effect of syscalls will always
83 side-effect, read soon-to-be-aborted transactional data that should not remain
87 Simple syscalls (e.g. sigprocmask()) "could" be OK.  Even things like write()
88 from, say, printf() should be OK as long as the kernel does not access any
106 delivered.  For future compatibility the MSR.TS field should be checked to
118 However, basic signal handlers don't need to be aware of transactions
122 from the second ucontext.  This will be necessary for crash handlers to
140    fprintf(stderr, "Transaction to be restarted at 0x%llx, but "
150 When in an active transaction that takes a signal, we need to be careful with
156 stack pointer will be back at the tbegin but our in memory stack won't be valid
161 state.  This ensures that the signal context (written tm suspended) will be
164 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