From: David Gibson <dgibson@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Fei Li <fli@suse.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v8 6/7] qemu_thread_create: propagate the error to callers to handle
Date: Wed, 2 Jan 2019 13:29:41 +1100 [thread overview]
Message-ID: <20190102132941.0b887a22@umbus.fritz.box> (raw)
In-Reply-To: <87k1k5lv96.fsf@dusky.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Wed, 19 Dec 2018 10:29:41 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> David Gibson <dgibson@redhat.com> writes:
>
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
>
> Double-checking: is it okay to report some failures of this function
> (one of two H_RESOURCE failures, to be precise), but not others?
Yes. The distinction is whether the failure is likely to be of
relevance to the *host* administrator, or just to the guest.
Although.. come to think of it possibly that reported failure should be
H_HARDWARE to the guest, rather than H_RESOURCE.
--
David Gibson <dgibson@redhat.com>
Principal Software Engineer, Virtualization, Red Hat
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-02 2:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:50 [Qemu-devel] [PATCH for-4.0 v8 0/7] qemu_thread_create: propagate errors to callers to check Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 1/7] Fix segmentation fault when qemu_signal_init fails Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 2/7] qemu_init_vcpu: add a new Error parameter to propagate Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 3/7] migration: fix the multifd code when receiving less channels Fei Li
2018-12-13 6:17 ` Markus Armbruster
2018-12-17 11:45 ` Fei Li
2018-12-19 14:11 ` Markus Armbruster
2018-12-20 3:27 ` Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 4/7] migration: remove unused &local_err parameter in multifd_save_cleanup Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 5/7] migration: add more error handling for postcopy_ram_enable_notify Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 6/7] qemu_thread_create: propagate the error to callers to handle Fei Li
2018-12-13 7:26 ` Markus Armbruster
2018-12-14 0:24 ` David Gibson
2018-12-19 9:29 ` Markus Armbruster
2019-01-02 2:29 ` David Gibson [this message]
2018-12-17 7:29 ` Fei Li
2018-12-18 12:40 ` Fei Li
2018-12-19 10:11 ` Markus Armbruster
2018-12-19 10:10 ` Markus Armbruster
2018-12-19 12:14 ` Fei Li
2018-12-19 17:29 ` Eric Blake
2018-12-20 3:20 ` Fei Li
2018-12-21 9:36 ` Fei Li
2018-12-24 3:34 ` Peter Xu
2018-12-24 6:53 ` Fei Li
2018-12-25 12:18 ` Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 7/7] qemu_thread_join: fix segmentation fault Fei Li
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=20190102132941.0b887a22@umbus.fritz.box \
--to=dgibson@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=fli@suse.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.