From: Steven Seeger <steven.seeger@flightsystems.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ppc icount questions
Date: Fri, 12 Jan 2018 13:35:47 -0500 [thread overview]
Message-ID: <2270319.IXj8bBQWhi@wirbelwind> (raw)
In-Reply-To: <c2e77a8e-077d-1d7e-b19c-e6f9c683d6aa@redhat.com>
> I think this is the issue:
>
> I/O thread vCPU thread
> -----------------------------------------------------------------------
> executes 1,000,000,000-th instruction
> wakes up I/O thread
> finds 1st timer
> runs 1st timer
> executes 1,000 instructions
> ----------- QEMU_CLOCK_VIRTUAL now is 1,000,001,000 --------------------
> 1st timer finishes
> executes 10,000 instructions
> ----------- QEMU_CLOCK_VIRTUAL now is 1,000,011,000 --------------------
> runs 2nd timer
I would agree this is the issue. I was thinking that the timer ran in the same
thread as the CPU (thus preventing the two from running at the same time) but
I guess this is not true. There must be some sync point, because taking too
long to finish the timer makes things stall (or that may just be due to
causing a delay in delivery of the next interrupt.)
So I guess what I am looking for is a way to ensure the two run mutually
exclusive of each other. I know from other systems that we can run all this in
a single thread (hardware models and guest CPU) so it should be possible to do
in QEMU as well.
Steven
prev parent reply other threads:[~2018-01-12 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:19 [Qemu-devel] ppc icount questions Steven Seeger
2018-01-12 16:52 ` Paolo Bonzini
2018-01-12 17:12 ` Steven Seeger
2018-01-12 17:19 ` Paolo Bonzini
2018-01-12 18:03 ` Steven Seeger
2018-01-12 18:11 ` Paolo Bonzini
2018-01-12 18:35 ` Steven Seeger [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=2270319.IXj8bBQWhi@wirbelwind \
--to=steven.seeger@flightsystems.net \
--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 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.