Torvald Riegel <trie...@redhat.com> writes: > > I'm not sure this is quite true. If a libitm-executed transaction is > started from within some other transactional region (e.g., managed > explicitly by the user), and those two disagree about what is an abort > that should be retried or not, then this can at least have a negative > impact on performance: Either because the outermost HW transaction > handler thinks it shouldn't retry even though it should, or because the > outermost transaction retries continuously even though there's no way it > can succeed.
It shouldn't retry continuously for a nested abort. Also retrying a lot is dangerous anyways, you have to be very careful about that. Short term your biggest problem is profiling the whole thing in any case, and that is what the XABORT with well defined codes make much easier. -Andi -- a...@linux.intel.com -- Speaking for myself only
