Lines Matching refs:transaction

20 A simple transaction looks like this:
40   /* Retry the transaction if it failed because it conflicted with
49 example, the transaction completes as though it were normal straight-line code
57 transaction, the transaction will be aborted by the CPU.  Register and memory
65 Causes of transaction aborts
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
81 Syscalls made from within a suspended transaction are performed as normal and
82 the transaction is not explicitly doomed by the kernel.  However, what the
83 kernel does to perform the syscall may result in the transaction being doomed
85 effects will be persistent, independent of transaction success or failure.  No
87 transaction success.
91 give the appearance of success) or perform operations that cause transaction
140            /* Yes, we crashed during a transaction.  Oops. */
151 When in an active transaction that takes a signal, we need to be careful with
160 To avoid this, when taking a signal in an active transaction, we need to use
163 written below the stack required for the rollback.  The transaction is aborted
175 kernel aborted a transaction:
180  TM_CAUSE_SYSCALL       Syscall from active transaction.
193 GDB and ptrace are not currently TM-aware.  If one stops during a transaction,
194 it looks like the transaction has just started (the checkpointed state is
195 presented).  The transaction cannot then be continued and will take the failure