Displaying 6 results from an estimated 6 matches for "configon".
Did you mean:
config
2012 Feb 23
1
[PATCH v2] Add a flag to make some functions called only at CONFIG state(RHBZ796520)
Add a flag "ConfigOnly" to make sure that some non-daemon-functions
should be called only at CONFIG state(RHBZ796520).
Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com>
---
generator/generator_actions.ml | 44 ++++++++++++++++++++--------------------
generator/generator_c.ml | 8 ++++++-...
2012 Feb 22
1
[PATCH] set-smp: only set smp value at config time
We only set smp number at config time, other than
it has no effect.
Also limit the number value below 255, since qemu
can't support that.
Below is the reproduce from https://bugzilla.redhat.com/show_bug.cgi?id=795322
> # guestfish -a /dev/null
> [...]
> ><fs> run
> ><fs> get-smp
> 1
> ><fs> set-smp 4
> ><fs> get-smp
> 4
>
2016 Sep 02
6
[PATCH 0/4] generator: Some work to split large C files
By splitting up large C files we can make parallel compiles
a bit faster.
Rich.
2017 Oct 04
0
[PATCH 2/9] ocaml: Replace pattern matching { field = field } with { field }.
.... *)
List.iter (
- fun { name = name; camel_name = camel_name } ->
+ fun { name; camel_name } ->
if not (contains_uppercase camel_name) then
failwithf "%s: camel case name must contain uppercase characters"
name;
@@ -265,7 +265,7 @@ let () =
(* ConfigOnly should only be specified on non_daemon_functions. *)
List.iter (
function
- | { name = name; config_only = true } ->
+ | { name; config_only = true } ->
failwithf "%s cannot have ConfigOnly flag" name
| { config_only = false } -> ()
) ((actions |>...
2017 Oct 04
11
[PATCH 0/9] build: Require OCaml >= 4.02.
Per my previous email:
https://www.redhat.com/archives/libguestfs/2017-September/msg00203.html
I'd like to talk about requiring a more modern version of the OCaml
compiler.
These commits show some of the code changes which would be possible
with OCaml >= 3.12 [which it turns out we already require by accident]
and also with OCaml >= 4.02. The latter is my favoured option.
Rich.
2012 Jul 03
8
[PATCH 0/7 v2] Fix and workaround for qcow2 issues in qemu causing data corruption.
https://bugzilla.redhat.com/show_bug.cgi?id=836710
https://bugzilla.redhat.com/show_bug.cgi?id=836913
There are at least two related bugs going on:
(1) Linux sync(2) system call doesn't send a write barrier to the
disk, so in effect it doesn't force the hard disk to flush its cache.
libguestfs used sync(2) to force changes to disk. We didn't expect
that qemu was caching anything