It is supported by 'nightly' makefile target. It creates
snapshot from the GIT HEAD, makes mockbuild,
creates repo and uploads result on the fedorapeople.
Also fixed makefile to support parallel builds, added
couple of hopefully useful targets, implemented local
RPM build target 'rpm'.
Other targets (e.g. 'srpm') can be also used to work
with snapshots. It is controlled by BUILD makefile
varible. If set to 'release' normal release is done.
If set to anything else (e.g. 'snapshot') snapshot
is done.
There is also support for GIT snapshots in the upstream
provided SPEC file. Snapshot build is done if
built with '--with snapshot', normal (release) build
is done otherwise.
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
By default build as development release with build date and git suffix
added to the release number. Build without this suffix if built
--with release
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
Accomplished by switch from GRUB_CMDLINE_LINUX to GRUB_CMDLINE_LINUX_DEFAULT
in /etc/default/grub
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
The plugin_bootloader is automatically disabled if the grub2 is not found.
Resolves: rhbz#1150047
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
Currently it is substitution for the rtctl tool,
but there are small differences in the syntax.
Format for the rules is:
group.GROUPNAME=RULE_PRIO:SCHED:PRIO:AFFINITY:REGEX
where RULE_PRIO defines tuned priority of the
rule. Rules are sorted according to priority.
This is needed for inheritence to be able
to reorder previously defined rule. For same
RULE_PRIO, rules should be processed in the order
there were defined (but this is Python interpreter
dependant). To disable inherited rule for GROUPNAME
use:
group.GROUPNAME=
SCHED must be one of:
'f' for FIFO,
'b' for batch,
'r' for round robin,
'o' for other,
'*' means not to change.
AFFINITY is a hex number, see taskset(1) for details
about number of CPUs. The '*' means not to change.
REGEX is Python regex. It must match against output of
ps -eo cmd
Any given process name may match more than one group.
Default priority and scheduling policy are taken from
the last matching rege.
You need to write 'group.' prefix before your
group name. This is because there may be added
other parameters to the plugin later.
Example of usage:
[scheduler]
group.kthreads=0:*:1:*:\[.*\]$
group.watchdog=0:f:99:*:\[watchdog.*\]
Resolves: rhbz#1100826
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
This plugin can be used to add parameters to kernel (boot/dracut)
command line. Currently only grub2 bootloader is used and reboot
is required to apply the tunings. The tuning can be only unloaded
by profile change followed by reboot.
It patches grub.cfg at runtime and installs /etc/grub.d/00_tuned
grub2 template. So it's possible to regenerate grub.cfg by
grub2-mkconfig and the tuning persists.
It also patches /etc/default/grub and adds tuned_params grub2 variable
to GRUB_CMDLINE_LINUX. This is probably the only way how to get
variables into kernel command line in grub.cfg. Nothing else is added to
/etc/default and it's patched if the plugin is used for the first
time. It's re-patched on plugin initialization only if the tuned_params
variable is missing.
On subsequent invocation only the tuned_params grub2 variable and
grub.cfg are changed.
Example of use:
[bootloader]
cmdline=quiet
This adds "quiet" parameter to the kernel boot command line (reboot
is required).
EFI is also supported. By default it autodetects redhat and fedora
directories (in this order). Nothing else is touched. If you have
different EFI system and your grub.cfg location is not auto-detected
or your grub.cfg is located on different place you can specify
the grub.cfg location manually:
[bootloader]
grub2_cfg_file=CUSTOM_PATH/grub.cfg
cmdline=quiet
This has precedence over auto-detection. This is used for runtime
patching. In case it is not set correctly, the grub.cfg patching
will not work, but you can still regenerate the config by hand by
grub2-mkconfig.
Resolves: rhbz#1044111
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
In this way only the installed profiles are described in the installed
manual pages. I.e. base profiles are now described in the tuned-profiles.7
manual page and profiles for the Project Atomic are now described
in the tuned-profiles-atomic.7 manual page. Simalarly for the SAP and
compat profiles.
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
These profiles are performance optimized for SAP HANA loads.
There are available in tuned-profiles-sap-hana subpackage.
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
The file system image containing tuned can be prepared offline, thus we
need to check the configuration on the first run. This is also more
clean solution than the previous post install hack.
Resolves: rhbz#1144067
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
This profile is performance optimized for running SAP NetWeaver
based applications on bare metal.
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
It's optional and there may be more SAP profiles in the future,
hus it's better to have special subpackage for it.
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
Added initial global config (/etc/tuned/tuned-main.conf) and
possibility to globally enable / disable dynamic tunings.
resolves: rhbz#1006427
Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
