From patchwork Fri Jan 21 09:26:39 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: docs: Document simple trace backend thread-safety limitation Date: Thu, 20 Jan 2011 23:26:39 -0000 From: Stefan Hajnoczi X-Patchwork-Id: 79818 Message-Id: <1295601999-14280-1-git-send-email-stefanha@linux.vnet.ibm.com> To: Cc: Stefan Hajnoczi , Prerna Saxena Signed-off-by: Stefan Hajnoczi --- docs/tracing.txt | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/docs/tracing.txt b/docs/tracing.txt index 963c504..d2499d9 100644 --- a/docs/tracing.txt +++ b/docs/tracing.txt @@ -133,6 +133,11 @@ source tree. It may not be as powerful as platform-specific or third-party trace backends but it is portable. This is the recommended trace backend unless you have specific needs for more advanced backends. +This trace backend is not thread-safe. In many cases this is not an issue +since the QEMU global mutex covers much of the codebase. Consider this +limitation when tracing utility functions that may be called from worker +threads with no synchronization. + ==== Monitor commands ==== * info trace