From: "Alex Bennée" <alex.bennee@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Juan Quintela" <quintela@redhat.com>,
"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>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wei W. Wang" <wei.w.wang@intel.com>
Subject: Re: Future of icount discussion for next KVM call?
Date: Thu, 16 Feb 2023 12:46:46 +0000 [thread overview]
Message-ID: <877cwh93m0.fsf@linaro.org> (raw)
In-Reply-To: <87bkltredr.fsf@pond.sub.org>
Markus Armbruster <armbru@redhat.com> writes:
> Juan Quintela <quintela@redhat.com> writes:
>
>> Alex Bennée <alex.bennee@linaro.org> wrote:
>>> (replying all because qemu-devel rejected my email again)
>>>
>>> On Thu, 16 Feb 2023 at 10:19, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>
>>>> Hi Juan,
>>>>
>>>> Do we have an agenda for next weeks KVM call yet? If there is space I'd
>>>> like to take some time to discuss the future direction of icount.
>>
>> For next week we have:
>> - more single binary qemu (philippe?)
>> - TDX migration from intel.
>> We asked them on the previous call to change their design to transfer
>> stuff through migration channels and not create a new channel. But I
>> haven't heard from intel. (wei?)
>> They agreed to send the slides and post the code before continue
>> discussion.
>>
>> And now I like the title of you topic
>>
>> - Future Direction of icount
>>
>> O:-)
>>
>> So, I will recommend 20 minutes each if Wei shows up, or 30/30 for the
>> rest.
>>
>> What do the rest of the people think.
>
> I think we either need fewer topics per call (ideally one), or strictly
> enforced time limits per topic. I don't fancy meetings where the topic
> that made me attend falls off the end.
I'm happy to push this out to the next KVM meeting if you want. The main
driver for posting this now was to ensure availability for interested
participants and maybe get some pre-discussion on the list.
> The former may necessitate more frequent calls.
Maybe - the number of agenda items tends to ebb and flow and we seem to
be making good use of the slot now to discuss a wide array of topics.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-02-16 12:50 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 [this message]
2023-02-16 13:56 ` Juan Quintela
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=877cwh93m0.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=bill.mills@linaro.org \
--cc=cota@braap.org \
--cc=erdnaxe@crans.org \
--cc=f4bug@amsat.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=quintela@redhat.com \
--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).