Lines Matching refs:transaction

21 A simple transaction looks like this::
41     /* Retry the transaction if it failed because it conflicted with
50 example, the transaction completes as though it were normal straight-line code
58 transaction, the transaction will be aborted by the CPU.  Register and memory
66 Causes of transaction aborts
78 Syscalls made from within an active transaction will not be performed and the
79 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
82 Syscalls made from within a suspended transaction are performed as normal and
83 the transaction is not explicitly doomed by the kernel.  However, what the
84 kernel does to perform the syscall may result in the transaction being doomed
86 effects will be persistent, independent of transaction success or failure.  No
88 transaction success.
92 give the appearance of success) or perform operations that cause transaction
141            /* Yes, we crashed during a transaction.  Oops. */
152 When in an active transaction that takes a signal, we need to be careful with
161 To avoid this, when taking a signal in an active transaction, we need to use
164 written below the stack required for the rollback.  The transaction is aborted
171 Any transaction initiated inside a sighandler and suspended on return
178 kernel aborted a transaction:
184  TM_CAUSE_SYSCALL       Syscall from active transaction.
198 GDB and ptrace are not currently TM-aware.  If one stops during a transaction,
199 it looks like the transaction has just started (the checkpointed state is
200 presented).  The transaction cannot then be continued and will take the failure
223 transaction when tm suspend occurs. So tsuspend will cause a
224 transaction to be aborted and rolled back. Kernel exceptions will also
225 cause the transaction to be aborted and rolled back and the exception
256 exception handling. When in a userspace transaction and we enter the
260 have SRR0 TM = 0 and TS = 00 (ie. TM off and non transaction) and the