qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug AioContext polling is not implemented on Windows with qemu-system-ppc.exe
Date: Thu, 22 Mar 2018 16:52:50 +0800	[thread overview]
Message-ID: <20180322085250.GH32362@xz-mi> (raw)
In-Reply-To: <CABLmASEOqo3cixnksUNg9kiHrA+NdLkE9+RcYTnK0BM+CjhVig@mail.gmail.com>

On Thu, Mar 22, 2018 at 09:28:34AM +0100, Howard Spoelstra wrote:
> > Hi, Howard,
> >
> > Thanks for reporting the problem.  Could you try applying below patch
> > to your rc0 tree and rebuild QEMU, to see whether it fixes your problem?
> >
> > -----------------------------
> > diff --git a/iothread.c b/iothread.c
> > index 1b3463cb00..9f52270ae1 100644
> > --- a/iothread.c
> > +++ b/iothread.c
> > @@ -31,11 +31,15 @@ typedef ObjectClass IOThreadClass;
> >  #define IOTHREAD_CLASS(klass) \
> >     OBJECT_CLASS_CHECK(IOThreadClass, klass, TYPE_IOTHREAD)
> >
> > +#ifdef CONFIG_LINUX
> >  /* Benchmark results from 2016 on NVMe SSD drives show max polling times around
> >   * 16-32 microseconds yield IOPS improvements for both iodepth=1 and iodepth=32
> >   * workloads.
> >   */
> >  #define IOTHREAD_POLL_MAX_NS_DEFAULT 32768ULL
> > +#else
> > +#define IOTHREAD_POLL_MAX_NS_DEFAULT 0ULL
> > +#endif
> >
> >  static __thread IOThread *my_iothread;
> >
> > diff --git a/util/aio-win32.c b/util/aio-win32.c
> > index d6d5e02f00..a67b00c6ad 100644
> > --- a/util/aio-win32.c
> > +++ b/util/aio-win32.c
> > @@ -410,5 +410,7 @@ void aio_context_setup(AioContext *ctx)
> >  void aio_context_set_poll_params(AioContext *ctx, int64_t max_ns,
> >                                   int64_t grow, int64_t shrink, Error **errp)
> >  {
> > -    error_setg(errp, "AioContext polling is not implemented on Windows");
> > +    if (max_ns) {
> > +        error_setg(errp, "AioContext polling is not implemented on Windows");
> > +    }
> >  }
> > -----------------------------
> >
> > Thanks,
> >
> > --
> > Peter Xu
> 
> Hi Peter,
> 
> Thanks, that patch does indeed fix the problem.

Thank you for testing that.  I'll post a formal patch soon.  Hopefully
it can reach rc1.

> 
> Best,
> Howard

-- 
Peter Xu

  reply	other threads:[~2018-03-22  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 17:11 [Qemu-devel] Bug AioContext polling is not implemented on Windows with qemu-system-ppc.exe Howard Spoelstra
2018-03-21 11:07 ` Paolo Bonzini
2018-03-21 13:13   ` Howard Spoelstra
2018-03-21 13:22     ` Paolo Bonzini
2018-03-21 13:29       ` Howard Spoelstra
2018-03-21 15:27         ` Paolo Bonzini
2018-03-21 16:23           ` Howard Spoelstra
2018-03-21 16:25             ` Paolo Bonzini
2018-03-21 16:31               ` Howard Spoelstra
2018-03-21 16:37                 ` Paolo Bonzini
2018-03-22  5:19                   ` Peter Xu
2018-03-22  8:28                     ` Howard Spoelstra
2018-03-22  8:52                       ` Peter Xu [this message]
2018-03-22  9:14                     ` Paolo Bonzini
2018-03-22 10:06                       ` Peter Xu

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=20180322085250.GH32362@xz-mi \
    --to=peterx@redhat.com \
    --cc=hsp.cat7@gmail.com \
    --cc=pbonzini@redhat.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 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).