All of
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <>
To: Jan Beulich <>
Cc: "Ian Jackson" <>,
	"Andrew Cooper" <>,
	"Frédéric Pierret" <>,
	"Dario Faggioli" <>,,
Subject: Re: [ANNOUNCE] Xen 4.15 release update - still in feature freeze
Date: Tue, 16 Mar 2021 10:43:23 +0100	[thread overview]
Message-ID: <YFB9ux/06pP4hh/Y@Air-de-Roger> (raw)
In-Reply-To: <>

On Mon, Mar 15, 2021 at 02:46:07PM +0100, Jan Beulich wrote:
> On 15.03.2021 13:18, Ian Jackson wrote:
> > ==============================
> > 
> > Fallout from MSR handling behavioral change.
> > 
> > I think there are now no outstanding patches to fix/change MSR
> > behaviour and there is no longer any blocker here ?
> In addition to what Andrew has said, while not a blocker in that
> sense I think the excessive verbosity of the logging is also an
> issue.

I think you meant the logging done for each MSR that's not explicitly

While I agree it might be too verbose, I don't see how we can change
that right now. We could introduce a command line parameter to select
whether to print those messages or not, but I think that's too
specific for a command line option.

We should look into some kind of logging improvements that allow
selecting which messages to print on a per-domain basis IMO.

In any case, those messages will only show up in debug builds, so it's
mostly annoying to developers but transparent to consumers of the
production build.

Thanks, Roger.

  reply	other threads:[~2021-03-16  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 12:18 [ANNOUNCE] Xen 4.15 release update - still in feature freeze Ian Jackson
2021-03-15 13:10 ` Andrew Cooper
2021-03-15 13:46 ` Jan Beulich
2021-03-16  9:43   ` Roger Pau Monné [this message]
2021-03-16 10:12     ` Jan Beulich
2021-03-18 18:11 ` Dario Faggioli
2021-03-29 17:16   ` Dario Faggioli

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:

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

  git send-email \
    --in-reply-to=YFB9ux/06pP4hh/Y@Air-de-Roger \ \ \ \ \ \ \ \ \

* 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.