From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Lukáš Doktor" <ldoktor@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] scripts: Remove 'debug' parameter from QEMUMachine & QEMUMonitorProtocol
Date: Thu, 5 Oct 2017 14:20:10 -0300 [thread overview]
Message-ID: <20171005172013.3098-1-ehabkost@redhat.com> (raw)
Changes v1 -> v2:
* Rebased to python-next (some patches from v1 are already queued
there)S
* guestperf: Inline init_logging() method on all callers because
not all classes derive from BaseShell (reported by Lukáš
Doktor)
This series removes the 'debug' parameter from QEMUMachine and
QEMUMonitorProtocol and lets scripts use the logging module to
enable debugging messages.
Eduardo Habkost (3):
guestperf: Configure logging on all shell frontends
scripts: Remove debug parameter from QEMUMonitorProtocol
scripts: Remove debug parameter from QEMUMachine
scripts/qemu.py | 9 +++------
scripts/qmp/qmp.py | 16 +++++++---------
tests/migration/guestperf/engine.py | 6 ++----
tests/migration/guestperf/shell.py | 13 +++++++++++++
tests/qemu-iotests/iotests.py | 2 --
5 files changed, 25 insertions(+), 21 deletions(-)
--
2.13.6
next reply other threads:[~2017-10-05 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 17:20 Eduardo Habkost [this message]
2017-10-05 17:20 ` [Qemu-devel] [PATCH v2 1/3] guestperf: Configure logging on all shell frontends Eduardo Habkost
2017-10-07 6:53 ` Lukáš Doktor
2017-10-05 17:20 ` [Qemu-devel] [PATCH v2 2/3] scripts: Remove debug parameter from QEMUMonitorProtocol Eduardo Habkost
2017-10-07 8:26 ` Lukáš Doktor
2017-10-10 2:49 ` Eduardo Habkost
2017-10-10 16:03 ` Lukáš Doktor
2017-10-05 17:20 ` [Qemu-devel] [PATCH v2 3/3] scripts: Remove debug parameter from QEMUMachine Eduardo Habkost
2017-10-07 8:34 ` Lukáš Doktor
2017-10-10 2:50 ` Eduardo Habkost
2017-10-10 16:01 ` Lukáš Doktor
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=20171005172013.3098-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ldoktor@redhat.com \
--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).