Tuesday, July 4, 2017

VRQ 0.96c release

VRQ 0.96c is released with the following changes

1. Sync up mainline scheduler changes in 4.12
2. Clean up herder files.

This is just a sync-up release to bring VRQ to 4.12 kernel. Not new feature code is added in VRQ itself.

Enjoy VRQ 0.96c for v4.12 kernel, and unlock your SMT cpu ability with VRQ, :)

code are available at
and also

All-in-one patch is available too.

BR Alfred 


  1. Merged into v4.12-pf1. Builds and boots OK.


  2. Builds and boot ok on Ryzen machine. One kernel build without problems. Seems stable so far. Alfred, thanks for quick sync up.

    BR, Dzon.

    1. I'm running this on i7 machine and no stability issues either.
      @Alfred, regarding my problem with efficiency on full load I might have stumbled on a symptom. With the y-cruncher benchmark I noticed that the results are almost identical to cfs, but there is a huge difference in time it took to "Reserving Working Memory... ". Maybe its not scheduling, but memory allocation problem. I will try to look into on how to test this theory.

      BR, Dzon.

  3. I got this while compiling (ubuntu 16.04, gcc-6.3):

    kernel/livepatch/transition.c:288:18: error: storage size of ‘flags’ isn’t known
    struct rq_flags flags;
    kernel/livepatch/transition.c:311:7: error: implicit declaration of function ‘task_rq_lock’ [-Werror=implicit-function-declaration]
    rq = task_rq_lock(task, &flags);
    kernel/livepatch/transition.c:313:6: error: implicit declaration of function ‘task_running’ [-Werror=implicit-function-declaration]
    if (task_running(rq, task) && task != current) {
    kernel/livepatch/transition.c:330:2: error: implicit declaration of function ‘task_rq_unlock’ [-Werror=implicit-function-declaration]
    task_rq_unlock(rq, task, &flags);
    kernel/livepatch/transition.c:288:18: warning: unused variable ‘flags’ [-Wunused-variable]
    struct rq_flags flags;

    I dunno why, meanwhile will compile a version for 4.11.

    Br, Eduardo

    1. @Eduardo
      I'd take care those compilation issue in 4.12 in next release. Those APIs are used to only be used in scheduler code.

      And BTW, your another post seems to be eaten by the lovly system, :)