From: Anthony PERARD <anthony.perard@citrix.com>
To: <paul@xen.org>
Cc: Jason Andryuk <jandryuk@gmail.com>, QEMU <qemu-devel@nongnu.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen-hvm: Allow disabling buffer_io_timer
Date: Wed, 26 Jan 2022 16:43:03 +0000 [thread overview]
Message-ID: <YfF6F6jG1mDbAMAj@perard> (raw)
In-Reply-To: <2ebaf0d6-a84a-e929-5ac2-597c81d40230@gmail.com>
On Wed, Jan 26, 2022 at 01:47:20PM +0000, Durrant, Paul wrote:
> On 26/01/2022 13:43, Jason Andryuk wrote:
> > On Tue, Dec 14, 2021 at 8:40 AM Durrant, Paul <xadimgnik@gmail.com> wrote:
> > >
> > > On 10/12/2021 11:34, Jason Andryuk wrote:
> > > > commit f37f29d31488 "xen: slightly simplify bufioreq handling" hard
> > > > coded setting req.count = 1 during initial field setup before the main
> > > > loop. This missed a subtlety that an early exit from the loop when
> > > > there are no ioreqs to process, would have req.count == 0 for the return
> > > > value. handle_buffered_io() would then remove state->buffered_io_timer.
> > > > Instead handle_buffered_iopage() is basically always returning true and
> > > > handle_buffered_io() always re-setting the timer.
> > > >
> > > > Restore the disabling of the timer by introducing a new handled_ioreq
> > > > boolean and use as the return value. The named variable will more
> > > > clearly show the intent of the code.
> > > >
> > > > Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
> > >
> > > Reviewed-by: Paul Durrant <paul@xen.org>
> >
> > Thanks, Paul.
> >
> > What is the next step for getting this into QEMU?
> >
>
> Anthony, can you queue this?
Yes, I'll send a pull request soon.
Sorry I tend to wait a while before preparing pull requests, especially
when there's only one patch. But there's another one now.
Cheers,
--
Anthony PERARD
WARNING: multiple messages have this Message-ID (diff)
From: Anthony PERARD via <qemu-devel@nongnu.org>
To: <paul@xen.org>
Cc: Jason Andryuk <jandryuk@gmail.com>, QEMU <qemu-devel@nongnu.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen-hvm: Allow disabling buffer_io_timer
Date: Wed, 26 Jan 2022 16:43:03 +0000 [thread overview]
Message-ID: <YfF6F6jG1mDbAMAj@perard> (raw)
In-Reply-To: <2ebaf0d6-a84a-e929-5ac2-597c81d40230@gmail.com>
On Wed, Jan 26, 2022 at 01:47:20PM +0000, Durrant, Paul wrote:
> On 26/01/2022 13:43, Jason Andryuk wrote:
> > On Tue, Dec 14, 2021 at 8:40 AM Durrant, Paul <xadimgnik@gmail.com> wrote:
> > >
> > > On 10/12/2021 11:34, Jason Andryuk wrote:
> > > > commit f37f29d31488 "xen: slightly simplify bufioreq handling" hard
> > > > coded setting req.count = 1 during initial field setup before the main
> > > > loop. This missed a subtlety that an early exit from the loop when
> > > > there are no ioreqs to process, would have req.count == 0 for the return
> > > > value. handle_buffered_io() would then remove state->buffered_io_timer.
> > > > Instead handle_buffered_iopage() is basically always returning true and
> > > > handle_buffered_io() always re-setting the timer.
> > > >
> > > > Restore the disabling of the timer by introducing a new handled_ioreq
> > > > boolean and use as the return value. The named variable will more
> > > > clearly show the intent of the code.
> > > >
> > > > Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
> > >
> > > Reviewed-by: Paul Durrant <paul@xen.org>
> >
> > Thanks, Paul.
> >
> > What is the next step for getting this into QEMU?
> >
>
> Anthony, can you queue this?
Yes, I'll send a pull request soon.
Sorry I tend to wait a while before preparing pull requests, especially
when there's only one patch. But there's another one now.
Cheers,
--
Anthony PERARD
next prev parent reply other threads:[~2022-01-26 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 19:34 [PATCH] xen-hvm: Allow disabling buffer_io_timer Jason Andryuk
2021-12-10 19:34 ` Jason Andryuk
2021-12-14 13:40 ` Durrant, Paul
2021-12-14 13:40 ` Durrant, Paul
2022-01-26 13:43 ` Jason Andryuk
2022-01-26 13:43 ` Jason Andryuk
2022-01-26 13:47 ` Durrant, Paul
2022-01-26 13:47 ` Durrant, Paul
2022-01-26 16:43 ` Anthony PERARD [this message]
2022-01-26 16:43 ` Anthony PERARD via
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=YfF6F6jG1mDbAMAj@perard \
--to=anthony.perard@citrix.com \
--cc=eduardo@habkost.net \
--cc=jandryuk@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.