From e4d4dfffec9ffe603296d51f140763c546ea1366 Mon Sep 17 00:00:00 2001 From: Red Bear OS Date: Mon, 20 Jul 2026 00:44:11 +0900 Subject: [PATCH] xhcid: promote IRQ reactor startup lines to info level MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 'Running IRQ reactor with IRQ file and event queue' and 'in polling mode' were debug! since the file was created, so test-xhci-irq-qemu.sh (which greps for the interrupt-driven line) could never see them at the default info log level — the IRQ-driven path had zero runtime evidence. They are one-time startup lines; promote to info so the interrupt delivery mode is observable and the proof can detect it. --- drivers/usb/xhcid/src/xhci/irq_reactor.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/xhcid/src/xhci/irq_reactor.rs b/drivers/usb/xhcid/src/xhci/irq_reactor.rs index fb249fc1d8..2079caa493 100644 --- a/drivers/usb/xhcid/src/xhci/irq_reactor.rs +++ b/drivers/usb/xhcid/src/xhci/irq_reactor.rs @@ -128,7 +128,7 @@ impl IrqReactor { std::thread::sleep(std::time::Duration::from_millis(2)); } fn run_polling(mut self) -> ! { - debug!("Running IRQ reactor in polling mode."); + log::info!("Running IRQ reactor in polling mode."); let hci_clone = Arc::clone(&self.hci); let mut event_trb_index = { @@ -180,7 +180,7 @@ impl IrqReactor { } fn run_with_irq_file(mut self) -> ! { - debug!("Running IRQ reactor with IRQ file and event queue"); + log::info!("Running IRQ reactor with IRQ file and event queue"); let hci_clone = Arc::clone(&self.hci); let event_queue =