From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Mads Ynddal <mads@ynddal.dk>, John Snow <jsnow@redhat.com>,
Cleber Rosa <crosa@redhat.com>,
Mads Ynddal <m.ynddal@samsung.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PULL 12/14] simpletrace: added simplified Analyzer2 class
Date: Thu, 28 Sep 2023 09:44:05 -0400 [thread overview]
Message-ID: <20230928134407.568453-13-stefanha@redhat.com> (raw)
In-Reply-To: <20230928134407.568453-1-stefanha@redhat.com>
From: Mads Ynddal <m.ynddal@samsung.com>
By moving the dynamic argument construction to keyword-arguments,
we can remove all of the specialized handling, and streamline it.
If a tracing method wants to access these, they can define the
kwargs, or ignore it be placing `**kwargs` at the end of the
function's arguments list.
Added deprecation warning to Analyzer class to make users aware
of the Analyzer2 class. No removal date is planned.
Signed-off-by: Mads Ynddal <m.ynddal@samsung.com>
Message-id: 20230926103436.25700-13-mads@ynddal.dk
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
scripts/simpletrace.py | 94 ++++++++++++++++++++++++++++++++----------
1 file changed, 73 insertions(+), 21 deletions(-)
diff --git a/scripts/simpletrace.py b/scripts/simpletrace.py
index 4136d00600..cef81b0707 100755
--- a/scripts/simpletrace.py
+++ b/scripts/simpletrace.py
@@ -12,10 +12,11 @@
import sys
import struct
import inspect
+import warnings
from tracetool import read_events, Event
from tracetool.backend.simple import is_string
-__all__ = ['Analyzer', 'process', 'run']
+__all__ = ['Analyzer', 'Analyzer2', 'process', 'run']
# This is the binary format that the QEMU "simple" trace backend
# emits. There is no specification documentation because the format is
@@ -130,7 +131,9 @@ def read_trace_records(events, fobj, read_header):
yield (event_mapping[event_name], event_name, timestamp_ns, pid) + tuple(args)
class Analyzer:
- """A trace file analyzer which processes trace records.
+ """[Deprecated. Refer to Analyzer2 instead.]
+
+ A trace file analyzer which processes trace records.
An analyzer can be passed to run() or process(). The begin() method is
invoked, then each trace record is processed, and finally the end() method
@@ -188,6 +191,11 @@ def _build_fn(self, event):
return lambda _, rec: fn(*rec[3:3 + event_argcount])
def _process_event(self, rec_args, *, event, event_id, timestamp_ns, pid, **kwargs):
+ warnings.warn(
+ "Use of deprecated Analyzer class. Refer to Analyzer2 instead.",
+ DeprecationWarning,
+ )
+
if not hasattr(self, '_fn_cache'):
# NOTE: Cannot depend on downstream subclasses to have
# super().__init__() because of legacy.
@@ -211,6 +219,56 @@ def __exit__(self, exc_type, exc_val, exc_tb):
self.end()
return False
+class Analyzer2(Analyzer):
+ """A trace file analyzer which processes trace records.
+
+ An analyzer can be passed to run() or process(). The begin() method is
+ invoked, then each trace record is processed, and finally the end() method
+ is invoked. When Analyzer is used as a context-manager (using the `with`
+ statement), begin() and end() are called automatically.
+
+ If a method matching a trace event name exists, it is invoked to process
+ that trace record. Otherwise the catchall() method is invoked.
+
+ The methods are called with a set of keyword-arguments. These can be ignored
+ using `**kwargs` or defined like any keyword-argument.
+
+ The following keyword-arguments are available, but make sure to have an
+ **kwargs to allow for unmatched arguments in the future:
+ event: Event object of current trace
+ event_id: The id of the event in the current trace file
+ timestamp_ns: The timestamp in nanoseconds of the trace
+ pid: The process id recorded for the given trace
+
+ Example:
+ The following method handles the runstate_set(int new_state) trace event::
+
+ def runstate_set(self, new_state, **kwargs):
+ ...
+
+ The method can also explicitly take a timestamp keyword-argument with the
+ trace event arguments::
+
+ def runstate_set(self, new_state, *, timestamp_ns, **kwargs):
+ ...
+
+ Timestamps have the uint64_t type and are in nanoseconds.
+
+ The pid can be included in addition to the timestamp and is useful when
+ dealing with traces from multiple processes:
+
+ def runstate_set(self, new_state, *, timestamp_ns, pid, **kwargs):
+ ...
+ """
+
+ def catchall(self, *rec_args, event, timestamp_ns, pid, event_id, **kwargs):
+ """Called if no specific method for processing a trace event has been found."""
+ pass
+
+ def _process_event(self, rec_args, *, event, **kwargs):
+ fn = getattr(self, event.name, self.catchall)
+ fn(*rec_args, event=event, **kwargs)
+
def process(events, log, analyzer, read_header=True):
"""Invoke an analyzer on each event in a log.
Args:
@@ -278,30 +336,24 @@ def run(analyzer):
process(events_fobj, log_fobj, analyzer, read_header=not no_header)
if __name__ == '__main__':
- class Formatter(Analyzer):
+ class Formatter2(Analyzer2):
def __init__(self):
- self.last_timestamp = None
+ self.last_timestamp_ns = None
- def catchall(self, event, rec):
- timestamp = rec[1]
- if self.last_timestamp is None:
- self.last_timestamp = timestamp
- delta_ns = timestamp - self.last_timestamp
- self.last_timestamp = timestamp
+ def catchall(self, *rec_args, event, timestamp_ns, pid, event_id):
+ if self.last_timestamp_ns is None:
+ self.last_timestamp_ns = timestamp_ns
+ delta_ns = timestamp_ns - self.last_timestamp_ns
+ self.last_timestamp_ns = timestamp_ns
- fields = [event.name, '%0.3f' % (delta_ns / 1000.0),
- 'pid=%d' % rec[2]]
- i = 3
- for type, name in event.args:
- if is_string(type):
- fields.append('%s=%s' % (name, rec[i]))
- else:
- fields.append('%s=0x%x' % (name, rec[i]))
- i += 1
- print(' '.join(fields))
+ fields = [
+ f'{name}={r}' if is_string(type) else f'{name}=0x{r:x}'
+ for r, (type, name) in zip(rec_args, event.args)
+ ]
+ print(f'{event.name} {delta_ns / 1000:0.3f} {pid=} ' + ' '.join(fields))
try:
- run(Formatter())
+ run(Formatter2())
except SimpleException as e:
sys.stderr.write(str(e) + "\n")
sys.exit(1)
--
2.41.0
next prev parent reply other threads:[~2023-09-28 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 13:43 [PULL 00/14] Tracing patches Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 01/14] simpletrace: add __all__ to define public interface Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 02/14] simpletrace: annotate magic constants from QEMU code Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 03/14] simpletrace: improve parsing of sys.argv; fix files never closed Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 04/14] simpletrace: changed naming of edict and idtoname to improve readability Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 05/14] simpletrace: update code for Python 3.11 Stefan Hajnoczi
2023-09-28 13:43 ` [PULL 06/14] simpletrace: improved error handling on struct unpack Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 07/14] simpletrace: define exception and add handling Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 08/14] simpletrace: made Analyzer into context-manager Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 09/14] simpletrace: refactor to separate responsibilities Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 10/14] simpletrace: move logic of process into internal function Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 11/14] simpletrace: move event processing to Analyzer class Stefan Hajnoczi
2023-09-28 13:44 ` Stefan Hajnoczi [this message]
2023-09-28 13:44 ` [PULL 13/14] MAINTAINERS: add maintainer of simpletrace.py Stefan Hajnoczi
2023-09-28 13:44 ` [PULL 14/14] scripts/analyse-locks-simpletrace.py: changed iteritems() to items() Stefan Hajnoczi
2023-10-02 21:56 ` [PULL 00/14] Tracing patches Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230928134407.568453-13-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=m.ynddal@samsung.com \
--cc=mads@ynddal.dk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).