From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org,
Zhao Liu <zhao1.liu@intel.com>
Subject: [PATCH] i386: Fix the missing Rust HPET configuration option
Date: Mon, 17 Feb 2025 23:44:16 +0800 [thread overview]
Message-ID: <20250217154416.3144571-1-zhao1.liu@intel.com> (raw)
The configuration option of Rust HPET is missing, so that PC machine
can't boot with "hpet=on" when QEMU Rust support is enabled.
Add the Rust HPET configuration option.
Fixes: d128c341a744 ("i386: enable rust hpet for pc when rust is enabled")
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
---
hw/timer/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/hw/timer/Kconfig b/hw/timer/Kconfig
index 9ac008453408..c051597180f4 100644
--- a/hw/timer/Kconfig
+++ b/hw/timer/Kconfig
@@ -13,6 +13,10 @@ config HPET
bool
default y if PC && !HAVE_RUST
+config X_HPET_RUST
+ bool
+ default y if PC && HAVE_RUST
+
config I8254
bool
depends on ISA_BUS
--
2.34.1
next reply other threads:[~2025-02-17 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:44 Zhao Liu [this message]
2025-02-18 8:09 ` [PATCH] i386: Fix the missing Rust HPET configuration option Paolo Bonzini
2025-02-18 8:40 ` Zhao Liu
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=20250217154416.3144571-1-zhao1.liu@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@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).