* [PATCH v2] x86/HVM: limit upcall vector related verbosity
@ 2023-12-18 7:26 Jan Beulich
2024-02-26 13:37 ` Andrew Cooper
0 siblings, 1 reply; 2+ messages in thread
From: Jan Beulich @ 2023-12-18 7:26 UTC (permalink / raw)
To: xen-devel; +Cc: Andrew Cooper, Wei Liu, Roger Pau Monné
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.)
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
v2: Add comment.
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -4129,7 +4129,15 @@ static int hvmop_set_evtchn_upcall_vecto
if ( (v = domain_vcpu(d, op.vcpu)) == NULL )
return -ENOENT;
- printk(XENLOG_G_INFO "%pv: upcall vector %02x\n", v, op.vector);
+ /*
+ * Avoid logging all-identical messages for every vCPU, but make sure to
+ * log unusual events like the vector differing from vCPU 0's, or it
+ * changing after it was once set
+ */
+ if ( op.vector != d->vcpu[0]->arch.hvm.evtchn_upcall_vector ||
+ (v->arch.hvm.evtchn_upcall_vector &&
+ op.vector != v->arch.hvm.evtchn_upcall_vector) )
+ printk(XENLOG_G_INFO "%pv: upcall vector %02x\n", v, op.vector);
v->arch.hvm.evtchn_upcall_vector = op.vector;
hvm_assert_evtchn_irq(v);
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v2] x86/HVM: limit upcall vector related verbosity
2023-12-18 7:26 [PATCH v2] x86/HVM: limit upcall vector related verbosity Jan Beulich
@ 2024-02-26 13:37 ` Andrew Cooper
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Cooper @ 2024-02-26 13:37 UTC (permalink / raw)
To: Jan Beulich, xen-devel; +Cc: Wei Liu, Roger Pau Monné
On 18/12/2023 7:26 am, 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.)
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-02-26 13:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-18 7:26 [PATCH v2] x86/HVM: limit upcall vector related verbosity Jan Beulich
2024-02-26 13:37 ` Andrew Cooper
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.