From: David Hildenbrand <david@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: fam@euphon.net, peter.maydell@linaro.org, mst@redhat.com,
codyprime@gmail.com, mark.cave-ayland@ilande.co.uk,
mdroth@linux.vnet.ibm.com, kraxel@redhat.com, mreitz@redhat.com,
qemu-block@nongnu.org, quintela@redhat.com, armbru@redhat.com,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
marcandre.lureau@redhat.com, rth@twiddle.net,
farman@linux.ibm.com, groug@kaod.org, dgilbert@redhat.com,
alex.williamson@redhat.com, qemu-arm@nongnu.org,
stefanha@redhat.com, jsnow@redhat.com,
david@gibson.dropbear.id.au, kwolf@redhat.com,
berrange@redhat.com, cohuck@redhat.com, qemu-s390x@nongnu.org,
sundeep.lkml@gmail.com, qemu-ppc@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC] error: auto propagated local_err
Date: Thu, 19 Sep 2019 09:32:34 +0200 [thread overview]
Message-ID: <c4a95138-3c08-0563-d567-aa1828de7e39@redhat.com> (raw)
In-Reply-To: <20190918130244.24257-1-vsementsov@virtuozzo.com>
On 18.09.19 15:02, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Here is a proposal (three of them, actually) of auto propagation for
> local_err, to not call error_propagate on every exit point, when we
> deal with local_err.
>
> It also may help make Greg's series[1] about error_append_hint smaller.
>
> See definitions and examples below.
>
> I'm cc-ing to this RFC everyone from series[1] CC list, as if we like
> it, the idea will touch same code (and may be more).
>
> [1]: https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03449.html
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> include/qapi/error.h | 102 +++++++++++++++++++++++++++++++++++++++++++
> block.c | 63 ++++++++++++--------------
> block/backup.c | 8 +++-
> block/gluster.c | 7 +++
> 4 files changed, 144 insertions(+), 36 deletions(-)
>
> diff --git a/include/qapi/error.h b/include/qapi/error.h
> index 3f95141a01..083e061014 100644
> --- a/include/qapi/error.h
> +++ b/include/qapi/error.h
> @@ -322,6 +322,108 @@ void error_set_internal(Error **errp,
> ErrorClass err_class, const char *fmt, ...)
> GCC_FMT_ATTR(6, 7);
>
> +typedef struct ErrorPropagator {
> + Error **errp;
> + Error *local_err;
> +} ErrorPropagator;
> +
> +static inline void error_propagator_cleanup(ErrorPropagator *prop)
> +{
> + if (prop->local_err) {
> + error_propagate(prop->errp, prop->local_err);
> + }
> +}
> +
> +G_DEFINE_AUTO_CLEANUP_CLEAR_FUNC(ErrorPropagator, error_propagator_cleanup);
> +
> +/*
> + * ErrorPropagationPair
> + *
> + * [Error *local_err, Error **errp]
> + *
> + * First element is local_err, second is original errp, which is propagation
> + * target. Yes, errp has a bit another type, so it should be converted.
> + *
> + * ErrorPropagationPair may be used as errp, which points to local_err,
> + * as it's type is compatible.
> + */
> +typedef Error *ErrorPropagationPair[2];
> +
> +static inline void error_propagation_pair_cleanup(ErrorPropagationPair *arr)
> +{
> + Error *local_err = (*arr)[0];
> + Error **errp = (Error **)(*arr)[1];
> +
> + if (local_err) {
> + error_propagate(errp, local_err);
> + }
> +}
> +
> +G_DEFINE_AUTO_CLEANUP_CLEAR_FUNC(ErrorPropagationPair,
> + error_propagation_pair_cleanup);
> +
> +/*
> + * DEF_AUTO_ERRP
> + *
> + * Define auto_errp variable, which may be used instead of errp, and
> + * *auto_errp may be safely checked to be zero or not, and may be safely
> + * used for error_append_hint(). auto_errp is automatically propagated
> + * to errp at function exit.
> + */
> +#define DEF_AUTO_ERRP(auto_errp, errp) \
> + g_auto(ErrorPropagationPair) (auto_errp) = {NULL, (Error *)(errp)}
> +
> +
> +/*
> + * Another variant:
> + * Pros:
> + * - normal structure instead of cheating with array
> + * - we can directly use errp, if it's not NULL and don't point to
> + * error_abort or error_fatal
> + * Cons:
> + * - we need to define two variables instead of one
> + */
> +typedef struct ErrorPropagationStruct {
> + Error *local_err;
> + Error **errp;
> +} ErrorPropagationStruct;
> +
> +static inline void error_propagation_struct_cleanup(ErrorPropagationStruct *prop)
> +{
> + if (prop->local_err) {
> + error_propagate(prop->errp, prop->local_err);
> + }
> +}
> +
> +G_DEFINE_AUTO_CLEANUP_CLEAR_FUNC(ErrorPropagationStruct,
> + error_propagation_struct_cleanup);
> +
> +#define DEF_AUTO_ERRP_V2(auto_errp, errp) \
> + g_auto(ErrorPropagationStruct) (__auto_errp_prop) = {.errp = (errp)}; \
> + Error **auto_errp = \
> + ((errp) == NULL || *(errp) == error_abort || *(errp) == error_fatal) ? \
> + &__auto_errp_prop.local_err : \
> + (errp);
> +
> +/*
> + * Third variant:
> + * Pros:
> + * - simpler movement for functions which don't have local_err yet
> + * the only thing to do is to call one macro at function start.
> + * This extremely simplifies Greg's series
> + * Cons:
> + * - looks like errp shadowing.. Still seems safe.
> + * - must be after all definitions of local variables and before any
> + * code.
> + * - like v2, several statements in one open macro
> + */
> +#define MAKE_ERRP_SAFE(errp) \
> +g_auto(ErrorPropagationStruct) (__auto_errp_prop) = {.errp = (errp)}; \
> +if ((errp) == NULL || *(errp) == error_abort || *(errp) == error_fatal) { \
> + (errp) = &__auto_errp_prop.local_err; \
> +}
Using that idea, what about something like this:
diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
index 8bfb6684cb..043ad69f8b 100644
--- a/hw/s390x/s390-virtio-ccw.c
+++ b/hw/s390x/s390-virtio-ccw.c
@@ -58,22 +58,42 @@ S390CPU *s390_cpu_addr2state(uint16_t cpu_addr)
return S390_CPU(ms->possible_cpus->cpus[cpu_addr].cpu);
}
+typedef struct ErrorPropagator {
+ Error **errp;
+ Error *local_err;
+} ErrorPropagator;
+
+static inline void error_propagator_cleanup(ErrorPropagator *prop)
+{
+ if (prop->local_err) {
+ error_propagate(prop->errp, prop->local_err);
+ }
+}
+
+G_DEFINE_AUTO_CLEANUP_CLEAR_FUNC(ErrorPropagator, error_propagator_cleanup);
+
+#define DEFINE_LOCAL_ERRP(_errp) \
+g_auto(ErrorPropagator) (__auto_errp_prop) = {.errp = (_errp)}; \
+Error **local_errp = &__auto_errp_prop.local_err
+
static S390CPU *s390x_new_cpu(const char *typename, uint32_t core_id,
Error **errp)
{
+ DEFINE_LOCAL_ERRP(errp);
S390CPU *cpu = S390_CPU(object_new(typename));
- Error *err = NULL;
- object_property_set_int(OBJECT(cpu), core_id, "core-id", &err);
- if (err != NULL) {
+ object_property_set_int(OBJECT(cpu), core_id, "core-id", local_errp);
+ if (*local_errp != NULL) {
goto out;
}
- object_property_set_bool(OBJECT(cpu), true, "realized", &err);
+ object_property_set_bool(OBJECT(cpu), true, "realized", local_errp);
out:
object_unref(OBJECT(cpu));
- if (err) {
- error_propagate(errp, err);
+ if (*local_errp) {
cpu = NULL;
}
return cpu;
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-09-19 7:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:02 [Qemu-devel] [RFC] error: auto propagated local_err Vladimir Sementsov-Ogievskiy
2019-09-18 17:10 ` Eric Blake
2019-09-18 17:46 ` Vladimir Sementsov-Ogievskiy
2019-09-18 18:05 ` Eric Blake
2019-09-18 18:32 ` Eric Blake
2019-09-19 6:47 ` Vladimir Sementsov-Ogievskiy
2019-09-19 13:29 ` Eric Blake
2019-09-19 9:17 ` Kevin Wolf
2019-09-19 9:47 ` Vladimir Sementsov-Ogievskiy
2019-09-19 10:09 ` Daniel P. Berrangé
2019-09-19 10:21 ` Vladimir Sementsov-Ogievskiy
2019-09-19 11:55 ` Daniel P. Berrangé
2019-09-19 12:00 ` Vladimir Sementsov-Ogievskiy
2019-09-19 13:03 ` Kevin Wolf
2019-09-19 13:17 ` Vladimir Sementsov-Ogievskiy
2019-09-19 13:44 ` Eric Blake
2019-09-19 13:40 ` Eric Blake
2019-09-19 14:13 ` Vladimir Sementsov-Ogievskiy
2019-09-19 14:26 ` Eric Blake
2019-09-19 14:30 ` Vladimir Sementsov-Ogievskiy
2019-09-19 14:44 ` Eric Blake
2019-09-19 14:49 ` Daniel P. Berrangé
2019-09-19 15:24 ` Eric Blake
2019-09-19 15:37 ` Vladimir Sementsov-Ogievskiy
2019-09-19 15:50 ` Daniel P. Berrangé
2019-09-19 16:16 ` Vladimir Sementsov-Ogievskiy
2019-09-19 16:51 ` Daniel P. Berrangé
2019-09-20 12:58 ` Eric Blake
2019-09-19 15:12 ` Vladimir Sementsov-Ogievskiy
2019-09-19 14:34 ` Kevin Wolf
2019-09-19 1:54 ` [Qemu-devel] " no-reply
2019-09-19 7:32 ` David Hildenbrand [this message]
2019-09-19 7:41 ` Vladimir Sementsov-Ogievskiy
2019-09-19 7:53 ` David Hildenbrand
2019-09-19 8:20 ` Vladimir Sementsov-Ogievskiy
2019-09-19 8:23 ` David Hildenbrand
2019-09-19 8:59 ` Greg Kurz
2019-09-19 9:28 ` Vladimir Sementsov-Ogievskiy
2019-09-19 10:08 ` Greg Kurz
2019-09-19 8:59 ` Max Reitz
2019-09-19 9:14 ` Vladimir Sementsov-Ogievskiy
2019-09-19 9:33 ` Max Reitz
2019-09-19 10:03 ` Vladimir Sementsov-Ogievskiy
2019-09-19 11:52 ` Max Reitz
2019-09-20 11:46 ` Vladimir Sementsov-Ogievskiy
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=c4a95138-3c08-0563-d567-aa1828de7e39@redhat.com \
--to=david@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=codyprime@gmail.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=fam@euphon.net \
--cc=farman@linux.ibm.com \
--cc=groug@kaod.org \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=sundeep.lkml@gmail.com \
--cc=vsementsov@virtuozzo.com \
/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).