From: Markus Armbruster <armbru@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: imammedo@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v1 0/5] Add error_abort and associated cleanups
Date: Tue, 03 Dec 2013 10:44:57 +0100 [thread overview]
Message-ID: <87a9ginu92.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <cover.1386049636.git.peter.crosthwaite@xilinx.com> (Peter Crosthwaite's message of "Mon, 2 Dec 2013 21:49:20 -0800")
Peter Crosthwaite <peter.crosthwaite@xilinx.com> writes:
> Following our discussion RE self asserting API calls, here is a spin of
> my proposal. This series obsoletes the need for _nofail variants for
> Error ** accepting APIs. Is also greately reduces the verbosity of calls
> sites that are currently asserting against errors.
>
> Patch 1 is the main event - addition of error_abort. The following
> patches then cleanup uses of _nofail and assert_no_error().
>
> To give it a smoke test, I introduce a (critical) bug into QOM:
[...]
> 32 files changed, 100 insertions(+), 143 deletions(-)
I like it. Nice diffstat, too.
There are some _nofail functions left, but none of them can use
error_abort.
If anything assigns to error_abort, we're probably screwed. No bright
idea how to prevent that at compile-time.
next prev parent reply other threads:[~2013-12-03 9:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 5:49 [Qemu-devel] [RFC PATCH v1 0/5] Add error_abort and associated cleanups Peter Crosthwaite
2013-12-03 5:49 ` [Qemu-devel] [RFC PATCH v1 1/5] error: Add error_abort Peter Crosthwaite
2013-12-03 5:50 ` [Qemu-devel] [RFC PATCH v1 2/5] hw: Remove assert_no_error usages Peter Crosthwaite
2013-12-03 9:35 ` Markus Armbruster
2013-12-03 10:04 ` Peter Crosthwaite
2013-12-03 5:51 ` [Qemu-devel] [RFC PATCH v1 3/5] target-i386: Remove assert_no_error usage Peter Crosthwaite
2013-12-03 5:51 ` [Qemu-devel] [RFC PATCH v1 4/5] qemu-option: Remove qemu_opts_create_nofail Peter Crosthwaite
2013-12-03 9:42 ` Markus Armbruster
2013-12-03 10:17 ` Peter Crosthwaite
2013-12-03 10:44 ` Markus Armbruster
2013-12-04 6:45 ` Peter Crosthwaite
2013-12-03 5:52 ` [Qemu-devel] [RFC PATCH v1 5/5] qerror: Remove assert_no_error() Peter Crosthwaite
2013-12-03 9:44 ` Markus Armbruster [this message]
2013-12-03 11:49 ` [Qemu-devel] [RFC PATCH v1 0/5] Add error_abort and associated cleanups Igor Mammedov
2013-12-03 11:57 ` Paolo Bonzini
2013-12-03 12:03 ` Peter Crosthwaite
2013-12-03 12:58 ` Eric Blake
2013-12-03 13:53 ` Markus Armbruster
2013-12-03 20:33 ` Igor Mammedov
2013-12-03 20:43 ` Eric Blake
2013-12-04 9:11 ` Markus Armbruster
2013-12-04 14:46 ` Eric Blake
2013-12-05 10:37 ` Paolo Bonzini
2013-12-05 15:32 ` Igor Mammedov
2013-12-05 15:59 ` Paolo Bonzini
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=87a9ginu92.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.