From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: Stafford Horne <shorne@gmail.com>, Jia Liu <proljc@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] target/openrisc: Call cpu_openrisc_clock_init() in cpu_realize()
Date: Thu, 6 Mar 2025 15:05:25 +0100 [thread overview]
Message-ID: <a5ca8711-64ed-400e-9eff-e8b4cd19bd72@linaro.org> (raw)
In-Reply-To: <20250114231304.77150-1-philmd@linaro.org>
On 15/1/25 00:13, Philippe Mathieu-Daudé wrote:
> OpenRISC timer is architecturally tied to the CPU.
>
> It doesn't belong to the machine init() code to
> instanciate it: move its creation when a vCPU is
> realized (after being created).
>
> Reported-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> hw/openrisc/openrisc_sim.c | 2 --
> hw/openrisc/virt.c | 2 --
> target/openrisc/cpu.c | 2 ++
> 3 files changed, 2 insertions(+), 4 deletions(-)
Patch queued, thanks.
prev parent reply other threads:[~2025-03-06 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 23:13 [RFC PATCH] target/openrisc: Call cpu_openrisc_clock_init() in cpu_realize() Philippe Mathieu-Daudé
2025-01-15 18:38 ` Richard Henderson
2025-03-06 14:05 ` Philippe Mathieu-Daudé [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=a5ca8711-64ed-400e-9eff-e8b4cd19bd72@linaro.org \
--to=philmd@linaro.org \
--cc=pbonzini@redhat.com \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=shorne@gmail.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).