From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] console: allow log level threshold adjustments from serial console
Date: Tue, 22 Sep 2015 14:35:22 +0100 [thread overview]
Message-ID: <5601591A.1030702@citrix.com> (raw)
In-Reply-To: <560172AB02000078000A4607@prv-mh.provo.novell.com>
On 22/09/15 14:24, Jan Beulich wrote:
>>>> On 22.09.15 at 15:17, <andrew.cooper3@citrix.com> wrote:
>> On 22/09/15 13:45, Jan Beulich wrote:
>>> +static void do_adj_thresh(unsigned char key)
>>> +{
>>> + if ( *upper_thresh_adj < *lower_thresh_adj )
>>> + *upper_thresh_adj = *lower_thresh_adj;
>>> + printk("'%c' pressed -> %s log level: %s (rate limited %s)\n",
>>> + key, thresh_adj, loglvl_str(*lower_thresh_adj),
>>> + loglvl_str(*upper_thresh_adj));
>> It might be useful for this printk() to indicate whether it was the
>> standard or the guest log level which was adjusted.
> It does, by printing the string thresh_adj currently points to.
Ah - so it does. Sorry for the noise.
>
>>> +static struct keyhandler inc_thresh_keyhandler = {
>>> + .irq_callback = 1,
>>> + .u.irq_fn = do_inc_thresh,
>>> + .desc = "increase log level threshold"
>>> +};
>>> +static struct keyhandler dec_thresh_keyhandler = {
>>> + .irq_callback = 1,
>>> + .u.irq_fn = do_dec_thresh,
>>> + .desc = "decrease log level threshold"
>>> +};
>>> +static struct keyhandler toggle_guest_keyhandler = {
>>> + .irq_callback = 1,
>>> + .u.irq_fn = do_toggle_guest,
>>> + .desc = "toggle host/guest log level adjustment"
>>> +};
>>> +
>> I am guessing from the looks of these that I should augment my
>> keyhandler cleanup to also be able to register irq handlers from outside
>> of common/keyhandler.c
> Yeah, I was actually surprised you got away without (i.e. that all of
> them lived in this one file so far).
It surprised me as well, but I didn't fancy adding it simply for the
sake of adding it.
~Andrew
prev parent reply other threads:[~2015-09-22 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 12:45 [PATCH] console: allow log level threshold adjustments from serial console Jan Beulich
2015-09-22 13:17 ` Andrew Cooper
2015-09-22 13:24 ` Jan Beulich
2015-09-22 13:35 ` Andrew Cooper [this message]
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=5601591A.1030702@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.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.