Displaying 4 results from an estimated 4 matches for "0.839687".
2015 Feb 25
7
virtio balloon: do not call blocking ops when !TASK_RUNNING
Hi all,
with the recent kernel 3.19, I get a kernel warning when I start my
KVM guest on s390 with virtio balloon enabled:
[ 0.839687] do not call blocking ops when !TASK_RUNNING; state=1 set at
[<0000000000174a1e>] prepare_to_wait_event+0x7e/0x108
[ 0.839694] ------------[ cut here ]------------
[ 0.839697] WARNING: at kernel/sched/core.c:7326
[ 0.839698]
2015 Feb 25
7
virtio balloon: do not call blocking ops when !TASK_RUNNING
Hi all,
with the recent kernel 3.19, I get a kernel warning when I start my
KVM guest on s390 with virtio balloon enabled:
[ 0.839687] do not call blocking ops when !TASK_RUNNING; state=1 set at
[<0000000000174a1e>] prepare_to_wait_event+0x7e/0x108
[ 0.839694] ------------[ cut here ]------------
[ 0.839697] WARNING: at kernel/sched/core.c:7326
[ 0.839698]
2015 Feb 26
0
virtio balloon: do not call blocking ops when !TASK_RUNNING
Thomas Huth <thuth at linux.vnet.ibm.com> writes:
> Hi all,
>
> with the recent kernel 3.19, I get a kernel warning when I start my
> KVM guest on s390 with virtio balloon enabled:
The deeper problem is that virtio_ccw_get_config just silently fails on
OOM.
Neither get_config nor set_config are expected to fail.
Cornelia, I think ccw and config_area should be allocated inside
2015 Feb 26
0
virtio balloon: do not call blocking ops when !TASK_RUNNING
Thomas Huth <thuth at linux.vnet.ibm.com> writes:
> Hi all,
>
> with the recent kernel 3.19, I get a kernel warning when I start my
> KVM guest on s390 with virtio balloon enabled:
The deeper problem is that virtio_ccw_get_config just silently fails on
OOM.
Neither get_config nor set_config are expected to fail.
Cornelia, I think ccw and config_area should be allocated inside