From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1tJAXY-0002FV-2t for mharc-qemu-rust@gnu.org; Thu, 05 Dec 2024 07:01:04 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJAXT-0002Eo-9r for qemu-rust@nongnu.org; Thu, 05 Dec 2024 07:01:01 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJAXN-0002sq-DY for qemu-rust@nongnu.org; Thu, 05 Dec 2024 07:00:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1733400050; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=kz+lWolidNLM4/3Lr+R4ibPfY0z6uplz27VVbpMn9HI=; b=PF8hm7tWVm77nbblpPWMWH32H1AdMCjP1sQ7Fk1n+Kqs0RwRVreDCIfAV9QsutccYkvA8N 3FMXcsb4fB4UgG4N0T0DxNO8i4XKnTR9TF5xR2McjqnNcVQfjX50oP/gGwFHrVsxEJH9Ks j+czzNDdEzs9XP1Me1PI9Cgmv+w5mpc= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-510-SAPjHdJhP0-Qp4woHkl1Zg-1; Thu, 05 Dec 2024 07:00:47 -0500 X-MC-Unique: SAPjHdJhP0-Qp4woHkl1Zg-1 X-Mimecast-MFC-AGG-ID: SAPjHdJhP0-Qp4woHkl1Zg Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id F01F01956046; Thu, 5 Dec 2024 12:00:43 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.137]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 3BE101955F3D; Thu, 5 Dec 2024 12:00:39 +0000 (UTC) Date: Thu, 5 Dec 2024 12:00:34 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Paolo Bonzini Cc: Stefan Hajnoczi , qemu-devel@nongnu.org, qemu-rust@nongnu.org, Paul Durrant Subject: Re: Rust in QEMU roadmap Message-ID: Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.13 (2024-03-09) X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -50 X-Spam_score: -5.1 X-Spam_bar: ----- X-Spam_report: (-5.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-2.996, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-rust@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: QEMU Rust-related patches and discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2024 12:01:01 -0000 On Wed, Nov 27, 2024 at 01:22:00PM +0100, Paolo Bonzini wrote: > On Wed, Nov 27, 2024 at 1:18 PM Daniel P. Berrangé wrote: > > I question the usefulness of the 'syslog' trace target. I can't see > > it being desirable as a option for 'production' builds, and it seems > > uneccessarily indirect for developers. What's its compelling USP ? > > > > WRT 'ftrace', IIUC, the Linux 'perf' command has built-in support > > for using USDT probes now: > > > > https://www.brendangregg.com/perf.html#StaticUserTracing > > I also wonder if 'ftrace' is duplicating 'log' these days. Anyhow, if > we can deprecate 'syslog' and 'ftrace' that would be good to know > independent of Rust. I looked back at the history of syslog and re-discovered that I raised the same question when it was first proposed. It was said that syslog was to be used by XenServer for some kind of logging they wanted: https://lists.nongnu.org/archive/html/qemu-devel/2016-08/msg00336.html I've CC'd Paul as it'd be useful to know if Xen did end up using this feature or not, as we don't want to rip the rug from under them. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|