Previously Jan posted [0]. The downside of that approach is that we need to rework log level number space to make it suitable for stable API (safe against addition and removal of numbers).
This version changes the interface to use buffers that contain string representation of log level. User space libraries won't care about what is inside. The parsing and interpretation is up to the hypervisor. Wei. [0] <56d9c80702000078000d9...@prv-mh.provo.novell.com> Wei Liu (5): xen/console: consolidate log levels to an array xen/console: allow log level threshold adjustments libxc: wrapper for log level sysctl libxl: introduce APIs to get and set log level xl: new loglvl command docs/man/xl.pod.1.in | 22 +++ tools/flask/policy/modules/dom0.te | 2 +- tools/libxc/include/xenctrl.h | 6 + tools/libxc/xc_misc.c | 143 ++++++++++++++++ tools/libxl/libxl.c | 40 +++++ tools/libxl/libxl.h | 11 ++ tools/libxl/xl.h | 1 + tools/libxl/xl_cmdimpl.c | 49 ++++++ tools/libxl/xl_cmdtable.c | 6 + xen/common/sysctl.c | 5 + xen/drivers/char/console.c | 314 +++++++++++++++++++++++++++++++++++- xen/include/public/sysctl.h | 41 +++++ xen/include/xen/console.h | 2 + xen/xsm/flask/hooks.c | 3 + xen/xsm/flask/policy/access_vectors | 2 + 15 files changed, 639 insertions(+), 8 deletions(-) -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
