From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call minutes for 2023-04-18
Date: Wed, 19 Apr 2023 09:55:53 +0200 [thread overview]
Message-ID: <87mt341f1y.fsf@secure.mitica> (raw)
Hi
We started testing with recording the call, will
Update on icount
Enable icount to be "enabled" independently of tcg.
icount + ttcg breaks, so there needs to be done some changes here.
The plugin allows to plug into the timer subsystem, so all the times are available.
Having multithread ttcg makes things complicated.
We don't want three versions of icount:
- deterministic
- multithread
- ....
The plugin only allows some primitives to handle the times, not the
full power of TCG.
We will try to break out the icount generation without disturbing
determinism.
The plugin will be able to calculate the time, and everything else
will read it from there.
The current code will continue to be as it is, and will not work with
multithread ttcg.
We got a recording of the call here:
https://fileserver.linaro.org/s/nJTSCLyQBfo6GLJ
Thanks to Alex for storing it.
Later, Juan.
reply other threads:[~2023-04-19 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mt341f1y.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--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).