qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa).
Date: Sat, 26 Apr 2008 14:36:44 -0500	[thread overview]
Message-ID: <4813844C.7070308@codemonkey.ws> (raw)
In-Reply-To: <200804262026.06396.paul@codesourcery.com>

Paul Brook wrote:
> On Saturday 26 April 2008, Andrzej Zaborowski wrote:
>   
>> Revision: 4261
>>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4261
>> Author:   balrog
>> Date:     2008-04-26 16:04:29 +0000 (Sat, 26 Apr 2008)
>>
>> Log Message:
>> -----------
>> Errors while registering ioports are not fatal (Glauber Costa).
>>     
>
> Why shouldn't they be fatal? How can this be anything other than a serious bug 
> in the device emulation?
>   

I think the idea is that the device should fail to initialize rather the 
VM being destroyed.  Consider the case of PCI hotplug.  It's a 
recoverable error if register ioport fails during hot add.

In general, it's better to avoid exit()'ing deep in the code and instead 
propagate errors.  With that said, I don't think we should just 
eliminate the hw_error() call without going through and updating all the 
callers of register_ioport to handle that function failing.

Regards,

Anthony Liguori

> Paul
>
>
>   

  reply	other threads:[~2008-04-26 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 16:04 [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa) Andrzej Zaborowski
2008-04-26 19:26 ` Paul Brook
2008-04-26 19:36   ` Anthony Liguori [this message]
2008-04-26 19:57     ` Paul Brook
2008-04-26 20:33       ` Anthony Liguori
2008-04-26 20:45       ` Glauber Costa
2008-04-26 19:57   ` andrzej zaborowski
2008-04-26 20:08     ` Paul Brook
2008-04-26 20:38       ` Anthony Liguori
2008-04-26 20:54         ` Paul Brook
2008-04-26 21:09           ` Anthony Liguori
2008-04-26 21:29             ` Paul Brook
2008-04-26 20:39     ` Glauber Costa
2008-04-26 20:43     ` Anthony Liguori
2008-04-26 21:18       ` andrzej zaborowski

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=4813844C.7070308@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).