qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [Qemu-devel] PATCH: dont call exit() from pci_nic_init(),	let caller handle
Date: Thu, 20 Mar 2008 14:18:19 +0200	[thread overview]
Message-ID: <47E2560B.8020902@qumranet.com> (raw)
In-Reply-To: <20080320001951.GI14060@us.ibm.com>

Ryan Harper wrote:
> While exploring the PCI hotplug code recently posted, I encountered a
> situation where I don't believe the current behavior is ideal.  With
> hotplug, we can add additional pci-based nic devices like e1000 and
> rtl8139 from the qemu monitor.  If one mistakenly specifies model=ne2000
> (the ISA version), qemu just exits.  If a command is run from the
> monitor and specifies bogus values, I don't believe the right behavior
> is to exit out of the guest entirely.  The attached patch (which doesn't
> apply directly against qemu-cvs since hotplug hasn't been merged)
> changes pci_nic_init() to return NULL on error instead of exiting
> and then I've replaced all callers to check the return value and exit(),
> preserving the existing behavior, but allowing flexibility so
> hotplug can do the right thing and just report the error rather than
> exiting the guest.
>
>   

Applied, thanks.

[this didn't make it to kvm-devel for some reason?]

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2008-03-20 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  0:19 [Qemu-devel] PATCH: dont call exit() from pci_nic_init(), let caller handle Ryan Harper
2008-03-20 12:01 ` [Qemu-devel] Re: [kvm-devel] " Marcelo Tosatti
2008-03-20 12:18 ` Avi Kivity [this message]
2008-03-20 13:10   ` [kvm-devel] [Qemu-devel] " Ryan Harper

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=47E2560B.8020902@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).