On 2015/12/21 22:01, Will Deacon wrote:
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
[SNIP]
# /perf test -v signal
17: Test breakpoint overflow signal handler :
--- start ---
test child forked, pid 792
count1 11, count2 11, overflow 11
failed: RF
On 2015/12/21 22:01, Will Deacon wrote:
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
[SNIP]
# /perf test -v signal
17: Test breakpoint overflow signal handler :
--- start ---
test child forked, pid 792
count1 11, count2 11, overflow 11
failed: RF
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
> System hung can be reproduced on qemu and real hardware using:
>
> # perf test -v signal
>
> If qemu is started with '-smp 1', system hung. In real hardware and in
> qemu with smp > 1, the result is:
That sounds like a qemu
System hung can be reproduced on qemu and real hardware using:
# perf test -v signal
If qemu is started with '-smp 1', system hung. In real hardware and in
qemu with smp > 1, the result is:
# /perf test -v signal
17: Test breakpoint overflow signal handler :
--- start ---
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
> System hung can be reproduced on qemu and real hardware using:
>
> # perf test -v signal
>
> If qemu is started with '-smp 1', system hung. In real hardware and in
> qemu with smp > 1, the result is:
That sounds like a qemu
System hung can be reproduced on qemu and real hardware using:
# perf test -v signal
If qemu is started with '-smp 1', system hung. In real hardware and in
qemu with smp > 1, the result is:
# /perf test -v signal
17: Test breakpoint overflow signal handler :
--- start ---
6 matches
Mail list logo
