From: Cornelia Huck <cohuck@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Xu <peterx@redhat.com>, Halil Pasic <pasic@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Cornelia Huck <cohuck@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] qemu-error: advanced report_once handling
Date: Thu, 30 Aug 2018 16:59:00 +0200 [thread overview]
Message-ID: <20180830145902.27376-1-cohuck@redhat.com> (raw)
[Markus: I've decided to not include your R-b, as I did too many changes
to feel comfortable with that.]
[Also note that I'm about to disappear on vacation, so don't expect
quick responses. I just want to get it out before I forget about it.]
Based on previous discussions, I wanted to enhance the recently
merged report_once infrastucture with a way to print a message
once based on a variable instead of globally-once, similar to
what vfio-ccw uses today.
Not really tested, mainly wanted to get this out before my vacation
to get the ball rolling.
v1->v2:
- merged patch 3 (use the new function in vfio-ccw) into patch 1
- require a non-NULL 'printed' parameter
- have the functions return whether something was printed and slightly
simplify the existing macros
- adapt macro formatting to suit my aesthetic sensibilities
Cornelia Huck (2):
qemu-error: add {error,warn}_report_once_cond
qemu-error: make use of {error,warn}_report_once_cond
hw/vfio/ccw.c | 18 +++--------------
include/qemu/error-report.h | 39 ++++++++++++++++++------------------
util/qemu-error.c | 48 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 70 insertions(+), 35 deletions(-)
--
2.14.4
next reply other threads:[~2018-08-30 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 14:59 Cornelia Huck [this message]
2018-08-30 14:59 ` [Qemu-devel] [PATCH v2 1/2] qemu-error: add {error, warn}_report_once_cond Cornelia Huck
2018-08-31 5:57 ` Markus Armbruster
2018-08-30 14:59 ` [Qemu-devel] [PATCH v2 2/2] qemu-error: make use of " Cornelia Huck
2018-08-31 6:01 ` Markus Armbruster
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=20180830145902.27376-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=armbru@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).