[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 02/24] arm/vuart: move vpl011-related code to vpl011 emulator
On 2025-01-22 02:26, Jan Beulich wrote: On 21.01.2025 23:56, Jason Andryuk wrote:On 2025-01-03 20:58, Denis Mukhin via B4 Relay wrote:--- a/xen/drivers/char/console.c +++ b/xen/drivers/char/console.c@@ -579,6 +571,9 @@ static void __serial_rx(char c) if ( pv_shim && pv_console ) consoled_guest_tx(c); #endif + + if ( rc ) + printk(KERN_ERR "d%pd: failed to process console input: %d\n", d, rc); }static void cf_check serial_rx(char c)This will print the ENOSPC that was formerly silent. Since this is input from the console, that seems more informative to the user and okay to me.I don't view this as okay. For one it needs to be a guest log level, such that rate limiting can suitably suppress too many of these messages in a short time (which in particular might happen if the ENOSPC reason isn't dealt with by the receiving domain). And then I wonder whether this wouldn't better be even more strongly limited, perhaps to just once per domain. I was thinking of a user typing into the console. Silently dropping characters is frustrating when you don't know it is happening. On the other hand, if the domU is echoing characters, then the user receives feedback on their typing. So maybe silently ignoring ENOSPC is okay? ENODEV could be okay just once. It could also be helpful to get the message if you come back a week later and try to type into the same console. But these the user should rate limit themselves when they just keep getting errors :) I'm also unconvinced of KERN_ERR - from Xen's perspective nothing error- like has happened, once again most notably for the ENOSPC case. I'd view this as a warning at best. Finally: Why d%pd? It ought to be just %pd. Yes, thanks. Regards, Jason
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |