From: Gleb Natapov <gleb@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm: add detail error message when fail to add ioeventfd
Date: Mon, 3 Jun 2013 12:27:57 +0300 [thread overview]
Message-ID: <20130603092757.GE4725@redhat.com> (raw)
In-Reply-To: <1369198655-25156-1-git-send-email-akong@redhat.com>
On Wed, May 22, 2013 at 12:57:35PM +0800, Amos Kong wrote:
> I try to hotplug 28 * 8 multiple-function devices to guest with
> old host kernel, ioeventfds in host kernel will be exhausted, then
> qemu fails to allocate ioeventfds for blk/nic devices.
>
> It's better to add detail error here.
>
Applied, thanks.
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> kvm-all.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/kvm-all.c b/kvm-all.c
> index 8222729..3d5f7b7 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -813,6 +813,8 @@ static void kvm_mem_ioeventfd_add(MemoryListener *listener,
> r = kvm_set_ioeventfd_mmio(fd, section->offset_within_address_space,
> data, true, section->size, match_data);
> if (r < 0) {
> + fprintf(stderr, "%s: error adding ioeventfd: %s\n",
> + __func__, strerror(-r));
> abort();
> }
> }
> @@ -843,6 +845,8 @@ static void kvm_io_ioeventfd_add(MemoryListener *listener,
> r = kvm_set_ioeventfd_pio(fd, section->offset_within_address_space,
> data, true, section->size, match_data);
> if (r < 0) {
> + fprintf(stderr, "%s: error adding ioeventfd: %s\n",
> + __func__, strerror(-r));
> abort();
> }
> }
> --
> 1.7.1
--
Gleb.
prev parent reply other threads:[~2013-06-03 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 4:57 [Qemu-devel] [PATCH] kvm: add detail error message when fail to add ioeventfd Amos Kong
2013-05-22 9:32 ` Stefan Hajnoczi
2013-05-22 13:48 ` Amos Kong
2013-05-23 7:46 ` Stefan Hajnoczi
2013-05-24 9:16 ` Amos Kong
2013-06-03 9:27 ` Gleb Natapov [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=20130603092757.GE4725@redhat.com \
--to=gleb@redhat.com \
--cc=akong@redhat.com \
--cc=kvm@vger.kernel.org \
--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).