From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>, Fam Zheng <famz@redhat.com>,
Eliezer Tamir <eliezer.tamir@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Jens Axboe <axboe@fb.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Davide Libenzi <davidel@xmailserver.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Linux kernel polling for QEMU
Date: Mon, 05 Dec 2016 11:20:31 +0000 [thread overview]
Message-ID: <871sxm1v28.fsf@linaro.org> (raw)
In-Reply-To: <3677a5ef-a01c-b867-178b-8287017176d3@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 30/11/2016 10:46, Peter Maydell wrote:
>>> > The problem is indeed with the scheduling. The way it currently works
>>> > is to depend on the iothread to kick a reschedule once in a while, or
>>> > a cpu to issue an instruction that does so (wfe/wfi). However if
>>> > there's no io and a cpu never issues a scheduling instruction, then it
>>> > won't happen. We either need a sched tick or to never have an infinite
>>> > iothread ppoll timeout (basically using the ppoll timeout as a tick).
>> Ah yes, that one. I thought Alex had a patch which added
>> a timer to ensure that we don't allow a single guest
>> TCG vCPU to hog the execution thread, but maybe I'm
>> misremembering.
>
> Yes, it's part of MTTCG.
The patch itself is:
tcg: add kick timer for single-threaded vCPU emulation
It's not really part of MTTCG as it can be applied without reference to
the MTTCG work. However it is a pre-requisite to the iothread mutex
rework that MTTCG requires which would otherwise break the single
threaded case which currently relies on the side-effect to trigger
scheduling.
>
> Paolo
--
Alex Bennée
next prev parent reply other threads:[~2016-12-05 11:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 15:12 [Qemu-devel] Linux kernel polling for QEMU Stefan Hajnoczi
2016-11-28 9:31 ` Eliezer Tamir
2016-11-28 15:29 ` Stefan Hajnoczi
2016-11-28 15:41 ` Paolo Bonzini
2016-11-29 10:45 ` Stefan Hajnoczi
2016-11-30 17:41 ` Avi Kivity
2016-12-01 11:45 ` Stefan Hajnoczi
2016-12-01 11:59 ` Avi Kivity
2016-12-01 14:35 ` Paolo Bonzini
2016-12-02 10:12 ` Stefan Hajnoczi
2016-12-07 10:38 ` Avi Kivity
2016-12-07 10:32 ` Avi Kivity
2016-11-28 20:41 ` Willem de Bruijn
2016-11-29 8:19 ` Christian Borntraeger
2016-11-29 11:00 ` Stefan Hajnoczi
2016-11-29 11:58 ` Christian Borntraeger
2016-11-29 10:32 ` Fam Zheng
2016-11-29 11:17 ` Paolo Bonzini
2016-11-29 13:24 ` Fam Zheng
2016-11-29 13:27 ` Paolo Bonzini
2016-11-29 14:17 ` Fam Zheng
2016-11-29 15:24 ` Andrew Jones
2016-11-29 15:39 ` Fam Zheng
2016-11-29 16:01 ` Andrew Jones
2016-11-29 16:13 ` Paolo Bonzini
2016-11-29 19:38 ` Andrew Jones
2016-11-30 7:19 ` Peter Maydell
2016-11-30 9:05 ` Andrew Jones
2016-11-30 9:46 ` Peter Maydell
2016-11-30 14:18 ` Paolo Bonzini
2016-12-05 11:20 ` Alex Bennée [this message]
2016-11-29 15:45 ` Paolo Bonzini
2016-11-29 20:43 ` Stefan Hajnoczi
2016-11-30 5:42 ` Fam Zheng
2016-11-30 9:38 ` Stefan Hajnoczi
2016-11-30 10:50 ` Fam Zheng
2016-11-30 15:10 ` Stefan Hajnoczi
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=871sxm1v28.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=axboe@fb.com \
--cc=borntraeger@de.ibm.com \
--cc=davidel@xmailserver.org \
--cc=drjones@redhat.com \
--cc=eliezer.tamir@linux.intel.com \
--cc=famz@redhat.com \
--cc=hch@lst.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.