All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Polzini <laurentpolzin@gmail.com>
Cc: qemu-devel@nongnu.org,  qemu-arm@nongnu.org,
	millian.poquet@univ-tlse3.fr,  clement.aldebert@univ-tlse3.fr
Subject: Re: Raspberry Pi 3B energy consumption
Date: Wed, 19 Mar 2025 15:57:41 +0000	[thread overview]
Message-ID: <87ecytm2ru.fsf@draig.linaro.org> (raw)
In-Reply-To: <CABsFrshLGcmBEBXCMrOdDv213c1q6GB6pDs4JDLQGKrTzqvkYQ@mail.gmail.com> (Polzini's message of "Wed, 19 Mar 2025 13:38:57 +0100")

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-19 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 12:38 Raspberry Pi 3B energy consumption Polzini
2025-03-19 15:57 ` Alex Bennée [this message]
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

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=87ecytm2ru.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=clement.aldebert@univ-tlse3.fr \
    --cc=laurentpolzin@gmail.com \
    --cc=millian.poquet@univ-tlse3.fr \
    --cc=qemu-arm@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.