[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 1/6] argo: lower level of noisy connection-refused log
- To: dmukhin@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx
- From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 8 Jun 2026 15:54:51 -0400
- Arc-authentication-results: i=1; mx.zohomail.com; dkim=pass header.i=apertussolutions.com; spf=pass smtp.mailfrom=dpsmith@xxxxxxxxxxxxxxxxxxxx; dmarc=pass header.from=<dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1780948496; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=agwjieH2C8BqxPI7qbVmt/rqTrmPxOTB+kkEdNu7f3o=; b=RV+eATuNWtGEMKV0JMX7PlWr8yck1NQp2wbyfyhVAZfKpWpbu63Z5O7kFL6mlAe4SLTWIEnLukUYg20QPxqc1XqWKMRO3t4YcjQ7c5DBV2RvPypIJNQwz9Dmdia3xOaLBIOLI4lWmgI8Ot40jQ4oADgBPMlik5gAC9nhM1ClT7Y=
- Arc-seal: i=1; a=rsa-sha256; t=1780948496; cv=none; d=zohomail.com; s=zohoarc; b=mZxL+FYw2x95QmgxagjIlBkA1w6ENc66rKxnqzurwuiYYzVHlbhfBi5x7SjgXULDH/xw19GoCJdI2Uxo3gbg+oevOoJGcDGYHM1zVkwtOdL2i0sPVg1Jbd6a68BERIOjO6LmwGXDXyDbRj2vISyoPPMITHjQSpamHbdkxrlzfGQ=
- Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=zoho header.d=apertussolutions.com header.i="dpsmith@xxxxxxxxxxxxxxxxxxxx" header.h="Message-ID:Date:MIME-Version:Subject:To:Cc:References:From:In-Reply-To:Content-Type:Content-Transfer-Encoding"
- Cc: andrew.cooper3@xxxxxxxxxx, anthony.perard@xxxxxxxxxx, jbeulich@xxxxxxxx, julien@xxxxxxx, michal.orzel@xxxxxxx, roger.pau@xxxxxxxxxx, sstabellini@xxxxxxxxxx, christopher.w.clark@xxxxxxxxx, Mykola Kvach <mykola_kvach@xxxxxxxx>
- Delivery-date: Mon, 08 Jun 2026 19:55:16 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 5/26/26 5:58 PM, dmukhin@xxxxxxxx wrote:
From: Denis Mukhin <dmukhin@xxxxxxxx>
Switch the log line to argo_dprintk() so it is enabled only in debug
environments, as it can spam the logs when a dom0 service using the Argo
hypercall tries to communicate with a domain that is still starting up.
Note that this also lowers the log level to debug when the argo_dprintk()
facility is enabled.
Signed-off-by: Denis Mukhin <dmukhin@xxxxxxxx>
Reviewed-by: Mykola Kvach <mykola_kvach@xxxxxxxx>
---
Changes since v2:
- updated commit message
---
xen/common/argo.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/xen/common/argo.c b/xen/common/argo.c
index 28626e00a8cb..98a3db7fd070 100644
--- a/xen/common/argo.c
+++ b/xen/common/argo.c
@@ -2034,10 +2034,9 @@ sendv(struct domain *src_d, xen_argo_addr_t *src_addr,
src_id.domain_id);
if ( !ring_info )
{
- gprintk(XENLOG_ERR,
- "argo: vm%u connection refused, src (vm%u:%x) dst (vm%u:%x)\n",
- current->domain->domain_id, src_id.domain_id, src_id.aport,
- dst_addr->domain_id, dst_addr->aport);
+ argo_dprintk("vm%u connection refused, src (vm%u:%x) dst (vm%u:%x)\n",
+ current->domain->domain_id, src_id.domain_id,
src_id.aport,
+ dst_addr->domain_id, dst_addr->aport);
ret = -ECONNREFUSED;
}
My apologies but this is not the wisest approach, hitting this is a real
error and shouldn't be getting silenced. If you are seeing a lot of
these messages, I would suggest asking yourself why. Without further
context on how you are using it, one suggesting is perhaps your
connection model might need to be revisited.
V/r,
Daniel P. Smith
|