qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: clement.aldebert@univ-tlse3.fr
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,
	"millian.poquet" <millian.poquet@univ-tlse3.fr>,
	 laurent polzin <laurent.polzin@univ-tlse3.fr>
Subject: Re: Raspberry Pi 3B energy consumption
Date: Thu, 20 Mar 2025 18:14:23 +0100 (CET)	[thread overview]
Message-ID: <4545005.21021813.1742490863752.JavaMail.zimbra@univ-tlse3.fr> (raw)
In-Reply-To: <87ecytm2ru.fsf@draig.linaro.org>

Dear Alex Bennée,

Thank you for your response and for the provided documentation link.

To clarify, when we refer to energy consumption, we are specifically looking at CPU core utilization. Our goal is to ensure that when we turn off CPU cores on the emulated Raspberry Pi 3B, the host machine does not keep its corresponding cores running at 100% utilization.

This is particularly relevant for our use case, as our supervisor, M. Poquet, intends to use this project for teaching operating system development. Students using QEMU to emulate a Raspberry Pi 3B may have different host machines, so our objective is to implement a general approach that ensures CPU core deactivation works properly regardless of the host system.

So far, our measurements indicate that even after turning off cores in the emulated system, all CPU cores on the host remain at 100% utilization. We are exploring ways to improve this behavior.

We have looked into using -icount, but we would like to find a more viable solution, particularly for the Cortex-A53 CPU used in the Raspberry Pi 3B. Ideally, we would like to be able to use -smp 1 without being constrained by QEMU’s limitations and to implement proper CPU core shutdown, similar to what is available on x86-64 architectures.

Would you have any recommendations or insights on achieving better power management in this scenario?

Best regards,
Clément Aldebert & Laurent Polzin

----- Mail original -----
De: "Alex Bennée" <alex.bennee@linaro.org>
À: "Polzini" <laurentpolzin@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org, "millian poquet" <millian.poquet@univ-tlse3.fr>, "clement aldebert" <clement.aldebert@univ-tlse3.fr>
Envoyé: Mercredi 19 Mars 2025 16:57:41
Objet: Re: Raspberry Pi 3B energy consumption

Polzini <laurentpolzin@gmail.com> writes:

> Dear Sir/Madam, My name is Clément Aldebert, and I am a third-year computer science student at Paul Sabatier University.
> Together with my teammate Laurent Polzin, we are working on a project supervised by Millian Poquet. Our project focuses on
> reducing the energy consumption of QEMU’s Raspberry Pi 3B emulation, as we have observed that power usage is quite high
> even when the system is idle.

Can you qualify that a bit more? What are you running the emulation on?
What power usage do you see?

Power consumption of the emulation is really just down to computational
efficiency of the emulation and if we ever get to a point that QEMU can
go idle giving the host system a chance to reach a lower power state.

> Ultimately, we also aim to enable emulation on a single CPU core.

If you want to run all emulation on a single core you could use -icount
to do that. It is less efficient though.

> We are reaching out to
> inquire if you have any advice, resources, or suggestions for implementing power management in QEMU, particularly for the
> Raspberry Pi 3B model. Additionally, we would like to understand any constraints or best practices regarding adding new
> code or features to QEMU.

What documentation that exists can be found in the developers section of
the manual:

  https://qemu.readthedocs.io/en/master/devel/index.html

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-03-20 19:30 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 [this message]
2025-03-20 20:09     ` Peter Maydell
2025-03-20 20:11       ` Peter Maydell
2025-03-24 16:37         ` clement.aldebert

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=4545005.21021813.1742490863752.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=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).