public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] log: Send identifier string in log messages, openlog() won't work for us
Date: Fri, 24 Feb 2023 11:44:32 -0800	[thread overview]
Message-ID: <CABJz62Mk_MpCRQYYQ=YU3hJnfWTxckRaOiX2pQqtiiPU0BqKdQ@mail.gmail.com> (raw)
In-Reply-To: <20230224075937.01b6345d@elisabeth>

On Fri, Feb 24, 2023 at 07:59:37AM +0100, Stefano Brivio wrote:
> On Thu, 23 Feb 2023 10:15:15 -0800 Andrea Bolognani <abologna@redhat.com> wrote:
> > Note the change from passt.avx2 to passt. Looking at the process
> > listing, plain passt was used in both cases, so I assume that the
> > passt.avx2 mention is journald trying to fill in the blanks and
> > getting it wrong?
>
> Yes, it's your system logger filling in the blanks, but it didn't
> really get it wrong, as the process name is actually "passt.avx2" if
> the AVX2-enabled build starts. Look at this, cough cough, beauty in
> arch.c:
>
>   https://passt.top/passt/tree/arch.c#n21
>
> "passt.avx2" wasn't intended in any case.

Oh, I see now that I actually have passt.avx2 running, despite the
output of ps hiding this fact:

  $ ps aux | grep bin/passt
  qemu   173991   [...]   /usr/bin/passt [...]
  $ sudo ls -l /proc/173991/exe
  [...]   /proc/173991/exe -> /usr/bin/passt.avx2

So it looks like everything is indeed working as intended :)

-- 
Andrea Bolognani / Red Hat / Virtualization


  reply	other threads:[~2023-02-24 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 17:35 [PATCH] log: Send identifier string in log messages, openlog() won't work for us Stefano Brivio
2023-02-23 18:15 ` Andrea Bolognani
2023-02-24  6:59   ` Stefano Brivio
2023-02-24 19:44     ` Andrea Bolognani [this message]
2023-02-23 23:31 ` David Gibson

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='CABJz62Mk_MpCRQYYQ=YU3hJnfWTxckRaOiX2pQqtiiPU0BqKdQ@mail.gmail.com' \
    --to=abologna@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).