qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, "Aurelien Jarno" <aurelien@aurel32.net>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 11/13] isa: Clean up inappropriate hw_error()
Date: Thu, 17 Dec 2015 16:37:04 +0200	[thread overview]
Message-ID: <20151217163521-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <877fkdjgkn.fsf@blackfin.pond.sub.org>

On Thu, Dec 17, 2015 at 03:27:36PM +0100, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> > On Thu, Dec 17, 2015 at 01:19:53PM +0100, Markus Armbruster wrote:
> >> isa_bus_irqs(), isa_create() and isa_try_create() call hw_error() when
> >> passed a null bus.  Use of hw_error() has always been questionable,
> >> because these are used only during machine initialization, and
> >> printing CPU registers isn't useful there.
> >> 
> >> Since the previous commit, passing a null bus is a programming error.
> >> Drop the hw_error() and simply let it crash.
> >> 
> >> Cc: Richard Henderson <rth@twiddle.net>
> >> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> >> Cc: "Hervé Poussineau" <hpoussin@reactos.org>
> >> Cc: Aurelien Jarno <aurelien@aurel32.net>
> >> Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> >> Signed-off-by: Markus Armbruster <armbru@pond.sub.org>
> >> Reviewed-by: Hervé Poussineau <hpoussin@reactos.org>
> >
> > I'd prefer an assert just in case.
> 
> I understand "prefer", I don't understand "just in case" :)

To make debugging a bit less painful in case we missed something.

> Adding an assertion here merely converts one kind of crash into another.
> 
> Doesn't make anything safer, not even just in case something happens we
> thought was impossible.
> 
> Does print a message before crashing that some developers may find
> useful.
> 
> Might make our belief that null can't happen a bit more explicit.
> 
> My own preference is not to assert the blatantly obvious.  However, I'm
> certainly willing to defer to a maintainer's or reviewer's preference,
> within reason.  For what it's worth:
> 
>     $ scripts/get_maintainer.pl -f hw/isa/isa-bus.c 
>     get_maintainer.pl: No maintainers found, printing recent contributors.
>     get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.
> 
>     "Hervé Poussineau" <hpoussin@reactos.org> (commit_signer:4/6=67%)
>     Markus Armbruster <armbru@pond.sub.org> (commit_signer:3/6=50%)
>     Leon Alrae <leon.alrae@imgtec.com> (commit_signer:2/6=33%)
>     Paolo Bonzini <pbonzini@redhat.com> (commit_signer:2/6=33%)
>     Dave Airlie <airlied@redhat.com> (commit_signer:1/6=17%)
> 
> Considering all of the above, do you want me to add the assertions?

Only in case you want my Reviewed-by.

-- 
MST

  reply	other threads:[~2015-12-17 14:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:19 [Qemu-devel] [PATCH v2 00/13] Clean up some hw_error() misuse Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 01/13] hw: Don't use hw_error() for machine initialization errors Markus Armbruster
2015-12-17 14:39   ` Thomas Huth
2015-12-17 16:34   ` Richard Henderson
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 02/13] omap: Don't use hw_error() in device init() methods Markus Armbruster
2015-12-17 14:30   ` Thomas Huth
2015-12-17 14:50     ` Peter Maydell
2015-12-17 15:45     ` Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 03/13] arm_mptimer: Don't use hw_error() in realize() method Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 04/13] etraxfs_eth: Don't use hw_error() in init() method Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 05/13] raven: Mark use of hw_error() in realize() FIXME Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 06/13] error: Don't append a newline when printing the error hint Markus Armbruster
2015-12-17 15:50   ` Eric Blake
2015-12-17 16:19     ` Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 07/13] hw/arm/virt: Fix property "gic-version" error handling Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 08/13] sysbus: Don't use hw_error() in machine_init_done_notifiers Markus Armbruster
2015-12-17 14:33   ` Thomas Huth
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 09/13] isa: Trivially convert remaining PCI-ISA bridges to realize() Markus Armbruster
2015-12-17 13:37   ` Michael S. Tsirkin
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 10/13] isa: Clean up error handling around isa_bus_new() Markus Armbruster
2015-12-17 13:41   ` Michael S. Tsirkin
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 11/13] isa: Clean up inappropriate hw_error() Markus Armbruster
2015-12-17 13:39   ` Michael S. Tsirkin
2015-12-17 14:27     ` Markus Armbruster
2015-12-17 14:37       ` Michael S. Tsirkin [this message]
2015-12-17 16:38       ` Richard Henderson
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 12/13] audio: Clean up inappropriate and unreachable use of hw_error() Markus Armbruster
2015-12-17 12:19 ` [Qemu-devel] [PATCH v2 13/13] xen-hvm: Mark inappropriate error handling FIXME 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=20151217163521-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=armbru@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=hpoussin@reactos.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).