All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, qemu-rust@nongnu.org,
	Paul Durrant <paul@xen.org>
Subject: Re: Rust in QEMU roadmap
Date: Thu, 5 Dec 2024 12:00:34 +0000	[thread overview]
Message-ID: <Z1GV4kwvjPoEob6j@redhat.com> (raw)
In-Reply-To: <CABgObfaZkCQMWH9oH5rLdqHB-B8t2n9uWSaYASsBzxiiMK1hRQ@mail.gmail.com>

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é <berrange@redhat.com> 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 :|



  reply	other threads:[~2024-12-05 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 17:46 Rust in QEMU roadmap Paolo Bonzini
2024-11-27  6:46 ` Zhao Liu
2024-11-27  8:21   ` Paolo Bonzini
2024-11-27 10:47 ` Stefan Hajnoczi
2024-11-27 12:18   ` Daniel P. Berrangé
2024-11-27 12:22     ` Paolo Bonzini
2024-12-05 12:00       ` Daniel P. Berrangé [this message]
2024-12-05 12:10         ` Paul Durrant
2024-11-27 12:38 ` Daniel P. Berrangé
     [not found] <ab7626bb-7c77-49c9-8dc8-86d79b095e3a@pbonzini.local>
2024-12-01 12:16 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z1GV4kwvjPoEob6j@redhat.com \
    --to=berrange@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-rust@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.