qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vl.c:main_loop() non-blocking TCG optimization still useful?
Date: Mon, 8 Feb 2016 16:41:49 +0000	[thread overview]
Message-ID: <20160208164149.GH31586@stefanha-x1.localdomain> (raw)
In-Reply-To: <56B0B189.1000306@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

On Tue, Feb 02, 2016 at 02:39:21PM +0100, Jan Kiszka wrote:
> On 2016-02-02 14:29, Stefan Hajnoczi wrote:
> > Hi Jan,
> > In 2011 the following patch was merged to optimize I/O vs vcpu scheduling:
> > 
> > commit c9f711a5d31e22dac932c1c01e9c0f97caff0988
> > Author: Jan Kiszka <jan.kiszka@siemens.com>
> > Date:   Mon Aug 22 17:46:02 2011 +0200
> > 
> >     Poll main loop after I/O events were received
> > 
> > This was back in the days of CONFIG_IOTHREAD.  Things have changed
> > quite a bit since then.
> > 
> > Do you think the last_io/non-blocking trick is still needed today in TCG?
> 
> The problem back then was the lock-step between io-thread and vcpus
> thread: if the iothread polled with the option to block, the vcpus
> thread got kicked again because the common lock was released to it. But
> if the iothread did not block because of further pending io, it would
> have to kick the vcpus thread immediately out of its emulation loop
> again. This meant no progress for the vcpus, only sync ping-pong.
> 
> If this changed now (I lost a bit track), the need for this trick might
> be gone. Maybe try the setup I described and measure the boot time of an
> SMP guest with and without this trick.

Okay, thanks.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2016-02-08 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 13:29 [Qemu-devel] vl.c:main_loop() non-blocking TCG optimization still useful? Stefan Hajnoczi
2016-02-02 13:39 ` Jan Kiszka
2016-02-08 16:41   ` Stefan Hajnoczi [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=20160208164149.GH31586@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=jan.kiszka@siemens.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).