qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: clement.aldebert@univ-tlse3.fr
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "laurent polzin" <laurent.polzin@univ-tlse3.fr>,
	"millian.poquet" <millian.poquet@univ-tlse3.fr>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Raspberry Pi 3B energy consumption
Date: Mon, 24 Mar 2025 17:37:48 +0100 (CET)	[thread overview]
Message-ID: <975738318.22990772.1742834268217.JavaMail.zimbra@univ-tlse3.fr> (raw)
In-Reply-To: <CAFEAcA-aCi8CrHOffPJxFQq9xqnR+-_S6LUFg69PsdSR+g60gw@mail.gmail.com>

Dear Peter Maydell,

Thank you for your detailed response.

We will take a closer look at why, when using WFI, the affected cores still appear to be at 100% utilization in htop. Additionally, we will investigate whether implementing WFE in QEMU would be necessary to achieve proper CPU core shutdown.

Currently, we are not using PSCI, but this does seem like a promising approach that we will explore further.

Regarding the use of the "virt" machine, our supervisor, M. Poquet, requires the Raspberry Pi 3B specifically for his courses due to its hardware specifications. Therefore, switching to "virt" would only be considered as a last resort.

Thank you again for your insights. Any further recommendations would be greatly appreciated.

Best regards,
Clément Aldebert & Laurent Polzin



----- Mail original -----
De: "Peter Maydell" <peter.maydell@linaro.org>
À: "clement aldebert" <clement.aldebert@univ-tlse3.fr>
Cc: "Alex Bennée" <alex.bennee@linaro.org>, "qemu-devel" <qemu-devel@nongnu.org>, "millian.poquet" <millian.poquet@univ-tlse3.fr>, "laurent polzin" <laurent.polzin@univ-tlse3.fr>
Envoyé: Jeudi 20 Mars 2025 21:11:52
Objet: Re: Raspberry Pi 3B energy consumption

On Thu, 20 Mar 2025 at 20:09, Peter Maydell <peter.maydell@linaro.org> wrote:
> If you need WFE to work, that's certainly feasible and something it would
> be nice to see, but potentially quite a bit of work in the guts of QEMU's
> arm emulation. (Basically going to sleep on WFE is easy but then making
> sure that all the events  and situations that need to wake up a WFE is
> tedious. We implement sleep-on-WFI but not sleep-on-WFI because the set

should read "sleep-on-WFI but not sleep-on-WFE", of course. Oops...

> of WFI-wakeup events is rather smaller than the WFE-wakeup events.) It's
> been in the "we really should implement this but since the only downside
> is the host CPUs spinning, we've never got round to it" bucket for years.

-- PMM


      reply	other threads:[~2025-03-24 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABsFrshLGcmBEBXCMrOdDv213c1q6GB6pDs4JDLQGKrTzqvkYQ@mail.gmail.com>
2025-03-19 15:57 ` Raspberry Pi 3B energy consumption Alex Bennée
2025-03-20 17:14   ` clement.aldebert
2025-03-20 20:09     ` Peter Maydell
2025-03-20 20:11       ` Peter Maydell
2025-03-24 16:37         ` clement.aldebert [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=975738318.22990772.1742834268217.JavaMail.zimbra@univ-tlse3.fr \
    --to=clement.aldebert@univ-tlse3.fr \
    --cc=alex.bennee@linaro.org \
    --cc=laurent.polzin@univ-tlse3.fr \
    --cc=millian.poquet@univ-tlse3.fr \
    --cc=peter.maydell@linaro.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).