From: Juergen Gross <jgross@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Runtime adjustment of hypervisor parameters
Date: Fri, 4 Aug 2017 15:20:09 +0200 [thread overview]
Message-ID: <69f044c3-a987-12bd-eec3-d4c19f075e58@suse.com> (raw)
Last year Jan posted a patch series to change hypervisor log level
thresholds via xl command [1]. This approach was later modified by Wei
resulting in patch series [2].
I'd like to follow up with another approach being able to do the same,
but being much more flexible:
Instead of controlling only loglvl I suggest to add a xl command
xl xen-param <parameters>
which will take a <parameters> string being parsed by the hypervisor
the same way it is parsing boot parameters. Allowed parameters are
specified in the hypervisor the same way as boot parameters, but with
another set of macros (e.g. custom_runtime_param(), ...). Often enough
(e.g. in the loglvl case) the definitions could be just the same, while
in other cases they might differ a little bit (example: conring_size
would require a different handling as at boot time due to race
condition handling).
Parsing functions could be reused in most cases, they'd just need to
lose the __init modifier.
What do you think: is this approach sensible, or can I just put it into
/dev/null instead of starting with the patches?
Juergen
[1]
https://lists.xenproject.org/archives/html/xen-devel/2016-03/msg00694.html
[2]
https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg00228.html
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-08-04 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 13:20 Juergen Gross [this message]
2017-08-04 13:23 ` Runtime adjustment of hypervisor parameters Andrew Cooper
2017-08-04 13:36 ` Juergen Gross
2017-08-04 13:57 ` Andrew Cooper
2017-08-04 14:57 ` Juergen Gross
2017-08-21 10:02 ` George Dunlap
2017-08-04 13:47 ` Wei Liu
2017-08-04 14:51 ` Juergen Gross
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=69f044c3-a987-12bd-eec3-d4c19f075e58@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.