All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, tim@xen.org, ian.jackson@eu.citrix.com,
	ian.campbell@citrix.com, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Question to Xen log level in the case of PT
Date: Wed, 9 Sep 2015 14:53:53 +0800	[thread overview]
Message-ID: <55EFD781.5080505@intel.com> (raw)
In-Reply-To: <55EECF9602000078000A0AA9@prv-mh.provo.novell.com>

>> So can Xen change log level dynamically like Linux? If yes, we might
>> change this level temporarily while passing through IGD. If not, any
>> suggestion?
>
> First of all you could boot without lowering the log level (non-debug
> builds) or raising the log level ("loglvl=warning"; debug builds). But

Sorry I don't know how to build "non-debug" here. Could you give me this 
detail? Or where I can get this info?

> that would change the log level for the entire session, which may
> not be what you're after. I too realized that having a way to
> dynamically adjust the log level would be useful occasionally. For
> post-4.6 I have a patch (attached) ready allowing to do so in a
> limited way from the serial console (and hence also via "xl debug-key").
> As you'll see in there I also took note of it probably being desirable
> to have a sysctl (and then a wrapping xl command) to full control the
> log level. I didn't get around to implement that yet.

Good to know this.

>
> Otoh the specific messages you cite are of quite questionable use
> in the first place. I certainly would welcome a patch lowering their
> priority to XENLOG_G_DEBUG (which however would still not

Done.

Thanks
Tiejun

  reply	other threads:[~2015-09-09  6:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  6:53 Question to Xen log level in the case of PT Chen, Tiejun
2015-09-08 10:07 ` Jan Beulich
2015-09-09  6:53   ` Chen, Tiejun [this message]
2015-09-09  7:30     ` Jan Beulich

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=55EFD781.5080505@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.