From: Markus Armbruster <armbru@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 02/10] qdev: add creation function that may fail
Date: Sat, 12 Feb 2011 18:10:37 +0100 [thread overview]
Message-ID: <m31v3dnppu.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <AANLkTinyVKrC9pa83RK6AKvo-nQqk7pkkC+BkFravoam@mail.gmail.com> (Blue Swirl's message of "Thu, 3 Feb 2011 20:59:21 +0000")
Blue Swirl <blauwirbel@gmail.com> writes:
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> ---
> hw/qdev.c | 14 +++++++++++++-
> hw/qdev.h | 1 +
> 2 files changed, 14 insertions(+), 1 deletions(-)
>
> diff --git a/hw/qdev.c b/hw/qdev.c
> index c7fec44..1aa1ea0 100644
> --- a/hw/qdev.c
> +++ b/hw/qdev.c
> @@ -106,6 +106,18 @@ static DeviceState
> *qdev_create_from_info(BusState *bus, DeviceInfo *info)
> initialize the actual device emulation. */
> DeviceState *qdev_create(BusState *bus, const char *name)
> {
> + DeviceState *dev;
> +
> + dev = qdev_try_create(bus, name);
> + if (!dev) {
> + hw_error("Unknown device '%s' for bus '%s'\n", name, bus->info->name);
Aside: I never liked the use hw_error() for this purpose. Dumping CPU
state isn't helpful when the problem is a bad device name in board setup
code.
> + }
> +
> + return dev;
> +}
> +
> +DeviceState *qdev_try_create(BusState *bus, const char *name)
> +{
> DeviceInfo *info;
>
> if (!bus) {
> @@ -114,7 +126,7 @@ DeviceState *qdev_create(BusState *bus, const char *name)
>
> info = qdev_find_info(bus->info, name);
> if (!info) {
> - hw_error("Unknown device '%s' for bus '%s'\n", name, bus->info->name);
> + return NULL;
> }
>
> return qdev_create_from_info(bus, info);
> diff --git a/hw/qdev.h b/hw/qdev.h
> index 9808f85..8a13ec9 100644
> --- a/hw/qdev.h
> +++ b/hw/qdev.h
> @@ -122,6 +122,7 @@ typedef struct GlobalProperty {
> /*** Board API. This should go away once we have a machine config file. ***/
>
> DeviceState *qdev_create(BusState *bus, const char *name);
> +DeviceState *qdev_try_create(BusState *bus, const char *name);
> int qdev_device_help(QemuOpts *opts);
> DeviceState *qdev_device_add(QemuOpts *opts);
> int qdev_init(DeviceState *dev) QEMU_WARN_UNUSED_RESULT;
I'd prefer these to follow qdev_init() / qdev_init_nofail() precedence,
for consistency, i.e. rename existing qdev_create() to
qdev_create_nofail(), call your new function qdev_create().
next prev parent reply other threads:[~2011-02-12 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 20:59 [Qemu-devel] [PATCH 02/10] qdev: add creation function that may fail Blue Swirl
2011-02-12 17:10 ` Markus Armbruster [this message]
2011-02-12 17:30 ` Blue Swirl
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=m31v3dnppu.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=blauwirbel@gmail.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.