From: Chrysostomos Nanakos <cnanakos@grnet.gr>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pingfank@linux.vnet.ibm.com, famz@redhat.com,
benoit@irqsave.net, jan.kiszka@siemens.com, stefanha@redhat.com,
mjt@tls.msk.ru, kroosec@gmail.com, sw@weilnetz.de,
pbonzini@redhat.com, afaerber@suse.de, aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCH v3] async: aio_context_new(): Handle event_notifier_init failure
Date: Wed, 17 Sep 2014 16:18:34 +0300 [thread overview]
Message-ID: <54198A2A.9090907@grnet.gr> (raw)
In-Reply-To: <54198640.4050209@redhat.com>
On 09/17/2014 04:01 PM, Eric Blake wrote:
> On 09/17/2014 03:16 AM, Chrysostomos Nanakos wrote:
>> On 09/16/2014 10:40 PM, Eric Blake wrote:
>>> On 09/16/2014 12:04 PM, Chrysostomos Nanakos wrote:
>>>> If event_notifier_init fails QEMU exits without printing
>>>> any error information to the user. This commit adds an error
>>>> message on failure:
>>>>
>>>> # qemu [...]
>>> Showing the actual command line you used would be helpful.
>> The problem raised after having a system with a low limit of open files
>> and QEMU with 8 iothread objects. Do you believe that we should add such
>> a command line in the commit description? The problem can be easily
>> reproduced with any combination of low limit of open files and iothread
>> objects or even a low limit of open files without the creation of
>> iothreads.
> It is ALWAYS valuable to make your commit message give a good recipe for
> how to reproduce the problem your commit is fixing. It's not a
> prerequisite (a patch can be accepted on inspection alone), but giving
> full details of how to reproduce it makes life easier when revisiting
> the patch a year from now or when writing a test case to ensure no
> regressions.
>
No problem Eric, thanks for the advice. I will make the appropriates
changes to the commit log
and resend the patch.
Regards,
Chrysostomos.
prev parent reply other threads:[~2014-09-17 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 18:04 [Qemu-devel] [PATCH v3] async: aio_context_new(): Handle event_notifier_init failure Chrysostomos Nanakos
2014-09-16 18:04 ` Chrysostomos Nanakos
2014-09-16 19:40 ` Eric Blake
2014-09-16 19:48 ` Benoît Canet
2014-09-17 9:16 ` Chrysostomos Nanakos
2014-09-17 13:01 ` Eric Blake
2014-09-17 13:18 ` Chrysostomos Nanakos [this message]
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=54198A2A.9090907@grnet.gr \
--to=cnanakos@grnet.gr \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=benoit@irqsave.net \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kroosec@gmail.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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.