[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH] x86/HVM: limit upcall vector related verbosity
On Thu, Nov 23, 2023 at 11:25:34AM +0100, Jan Beulich wrote: > Avoid logging all-identical messages for every vCPU, but make sure to > log unusual events like the vector differing from vCPU 0's (note that > the respective condition also makes sure vCPU 0 itself will have the > vector setting logged), or it changing after it was once set. (Arguably > a downside is that some vCPU not having its vector set would no longer > be recognizable from the logs. But I think that's tolerable as > sufficiently unlikely outside of people actively fiddling with related > code.) Maybe we could consider printing unconditionally for debug builds? Thanks, Roger.
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |