All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmkhn@proton.me
To: Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Jan Beulich <jbeulich@suse.com>,
	andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	michal.orzel@amd.com, roger.pau@citrix.com, dmukhin@ford.com,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/2] xen/console: unify printout behavior for UART emulators
Date: Tue, 08 Jul 2025 23:30:03 +0000	[thread overview]
Message-ID: <aG2p+MmXdAJObhR8@kraken> (raw)
In-Reply-To: <ab1d2b35-2760-436c-8e9d-57f094712012@xen.org>

On Sat, Jun 28, 2025 at 06:26:12PM +0100, Julien Grall wrote:
> Hi Stefano,
> 
> On 21/06/2025 01:52, Stefano Stabellini wrote:
> >> Widely used or not - _I_ use it all the time in debug configs where serial
> >> is available.
> >
> > Fair enough and your usage is really important for the project. At the
> > same time you know exactly what's going on so you wouldn't be confused
> > by the presence or absence of a (d0) prefix.
> >
> > The main issue is when less familiar users try Xen, or less familiar
> > developers go through the Xen source code to learn from it.
> >
> > I would optimize this choice to make it simpler for users and to make
> > the code simpler. Your use-case is really important as well, but I would
> > trust you to understand what's going on either way, with or without the
> > (d0) prefix.
> 
> Thanks for the clarification. I gave a try with and without the series
> to understand a bit more the difference. I think there are some
> imbalance in that setup because when the focus is on Xen, the logs are
> still prefixed with "(XEN)". So naturally the log with no prefix are the
> one for Dom0. So I have to agree with Jan here.
> 
> I haven't tried the behavior with dom0less. So I am not sure what would
> happen if the focus switch to Xen.
> 
> Also, when switching focus, I have noticed a very odd behavior with this
> patch. "(d0)" is printed multiple time per line:

Thanks for catching this, will fix.

> 
> "
> (d0) [    1.344020] v(d0) gaarb: loaded
> (d0) [    1.352808] c(d0) locksource: Swit(d0) ched to clocksou(d0) rce
> arch_sys_cou(d0) nter
> (d0) [    1.367604] V(d0) FS: Disk quotas (d0) dquot_6.6.0
> (d0) [    1.369369] V(d0) FS: Dquot-cache (d0) hash table entri(d0) es:
> 512 (order 0(d0) , 4096 bytes)
> (d0) [    1.376766] p(d0) np: PnP ACPI: di(d0) sabled
> (d0) [    1.619730] N(d0) ET: Registered P(d0) F_INET protocol (d0) family
> (d0) [    1.623635] I(d0) P idents hash ta(d0) ble entries: 163(d0) 84
> (order: 5, 13(d0) 1072 bytes, line(d0) ar)
> (d0) [    1.636915] t(d0) cp_listen_portad(d0) dr_hash hash tab(d0) le
> entries: 512 (d0) (order: 3, 36864(d0)  bytes, linear)
> (d0) [    1.638331] T(d0) able-perturb has(d0) h table entries:(d0)
> 65536 (order: 6(d0) , 262144 bytes, (d0) linear)
> (d0) [    1.639267] T(d0) CP established h(d0) ash table entrie(d0) s:
> 8192 (order: (d0) 4, 65536 bytes, (d0) linear)
> (d0) [    1.643457] T(d0) CP bind hash tab(d0) le entries: 8192(d0)
> (order: 8, 1179(d0) 648 bytes, linea(d0) r)
> (d0) [    1.652078] T(d0) CP: Hash tables (d0) configured (esta(d0)
> blished 8192 bin(d0) d 8192)
> (d0) [    1.655824] U(d0) DP hash table en(d0) tries: 512 (orde(d0) r:
> 4, 81920 byte(d0) s, linear)
> (d0) [    1.657807] U(d0) DP-Lite hash tab(d0) le entries: 512 (d0)
> (order: 4, 81920(d0)  bytes, linear)
> (d0) [    1.661993] N(d0) ET: Registered P(d0) F_UNIX/PF_LOCAL (d0)
> protocol family
> (d0) [    1.674980] R(d0) PC: Registered n(d0) amed UNIX socket(d0)
> transport modul(d0) e.
> (d0) [    1.676034] R(d0) PC: Registered u(d0) dp transport mod(d0) ule.
> (d0) [    1.677241] R(d0) PC: Registered t(d0) cp transport mod(d0) ule.
> (d0) [    1.677964] R(d0) PC: Registered t(d0) cp-with-tls tran(d0)
> sport module.
> (d0) [    1.678615] R(d0) PC: Registered t(d0) cp NFSv4.1 backc(d0)
> hannel transport(d0)  module.
> "
> 
> Cheers,
> 
> --
> Julien Grall
> 
> 



  parent reply	other threads:[~2025-07-08 23:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 20:11 [PATCH v3 0/2] xen/console: updates to diagnostic messages prefixes dmkhn
2025-06-06 20:11 ` [PATCH v3 1/2] xen/console: introduce CONSOLE_PREFIX dmkhn
2025-07-25  1:02   ` Stefano Stabellini
2025-06-06 20:11 ` [PATCH v3 2/2] xen/console: unify printout behavior for UART emulators dmkhn
2025-06-10  8:21   ` Jan Beulich
2025-06-11  0:07     ` dmkhn
2025-06-11  5:39       ` Jan Beulich
2025-06-11 19:07         ` Stefano Stabellini
2025-06-12  6:51           ` Jan Beulich
2025-06-18  0:39             ` Stefano Stabellini
2025-06-18  6:27               ` Jan Beulich
2025-06-19  0:45                 ` Stefano Stabellini
2025-06-20  6:07                   ` Jan Beulich
2025-06-21  0:52                     ` Stefano Stabellini
2025-06-28 17:26                       ` Julien Grall
2025-06-28 17:28                         ` Julien Grall
2025-07-08 23:30                         ` dmkhn [this message]
2025-06-27 16:54                   ` Julien Grall
2025-06-27 21:58                     ` Stefano Stabellini
2025-06-29 13:47                       ` Jan Beulich
2025-06-30 22:22                         ` Stefano Stabellini
2025-06-30 22:27                           ` Stefano Stabellini
2025-07-08 23:33                             ` dmkhn
2025-07-08 23:32                         ` dmkhn
2025-06-25 10:50   ` Roger Pau Monné
2025-07-08 23:27     ` dmkhn

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=aG2p+MmXdAJObhR8@kraken \
    --to=dmkhn@proton.me \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=dmukhin@ford.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.