From: Juan Quintela <quintela@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Mark Burton" <mburton@qti.qualcomm.com>,
"Bill Mills" <bill.mills@linaro.org>,
"Marco Liebel" <mliebel@qti.qualcomm.com>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Emilio Cota" <cota@braap.org>, kvm-devel <kvm@vger.kernel.org>,
"Wei W. Wang" <wei.w.wang@intel.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: Future of icount discussion for next KVM call?
Date: Thu, 16 Feb 2023 14:56:43 +0100 [thread overview]
Message-ID: <875yc1k92c.fsf@secure.mitica> (raw)
In-Reply-To: <CAHDbmO3QSbpKLWKt9uj+2Yo_fT-dC-E4M1Nb=iWHqMSBw35-3w@mail.gmail.com> ("Alex Bennée"'s message of "Thu, 16 Feb 2023 10:23:58 +0000")
Alex Bennée <alex.bennee@linaro.org> wrote:
> (replying all because qemu-devel rejected my email again)
Just to see what we are having now:
- single qemu binary moved to next slot (moved to next week?)
Phillipe proposal
- TDX migration: we have the slides, but no code
So I guess we can move it to the following slot, when we have a chance
to look at the code, Wei?
- Markus asked to have only one topic per call
(and it is reasonable)
- the future of icount cames with documentation to read before the call.
So I think we can do the icount call this week, and discuss here on list
if we move to a weekly call on the same slot.
What do you think?
Later, Juan.
next prev parent reply other threads:[~2023-02-16 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bklt9alc.fsf@linaro.org>
2023-02-16 10:23 ` Future of icount discussion for next KVM call? Alex Bennée
2023-02-16 10:56 ` Juan Quintela
2023-02-16 12:20 ` Markus Armbruster
2023-02-16 12:45 ` Philippe Mathieu-Daudé
2023-02-16 12:46 ` Alex Bennée
2023-02-16 13:56 ` Juan Quintela [this message]
2023-02-16 14:36 ` Wang, Wei W
2023-02-25 1:46 ` Wang, Wei W
2023-03-03 9:12 ` Wang, Wei W
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=875yc1k92c.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bill.mills@linaro.org \
--cc=cota@braap.org \
--cc=erdnaxe@crans.org \
--cc=f4bug@amsat.org \
--cc=kvm@vger.kernel.org \
--cc=ma.mandourr@gmail.com \
--cc=mburton@qti.qualcomm.com \
--cc=mliebel@qti.qualcomm.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wei.w.wang@intel.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 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).