https://bugzilla.redhat.com/show_bug.cgi?id=1064929
Eryu Guan <eguan(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |VERIFIED
--- Comment #29 from Eryu Guan <eguan(a)redhat.com> ---
Reproduced with kernel-3.10.0-106.el7, following steps in comment 5
Samples: 931K of event 'cycles', Event count (approx.): 39097077164
37.59% [kernel] [k] pcpu_alloc_area
17.67% [kernel] [k] pcpu_free_area
7.97% [kernel] [k] lg_global_lock
6.90% [kernel] [k] seq_list_start
3.57% [kernel] [k] memset
3.52% [kernel] [k] find_next_bit
3.02% [kernel] [k] lg_global_unlock
1.69% libc-2.17.so [.] _IO_vfscanf
Verified with kernel-3.10.0-121.el7
Samples: 253K of event 'cycles', Event count (approx.): 70681567890
13.92% libc-2.17.so [.] _IO_vfscanf
6.75% systemd [.] 0x0000000000080922
5.26% libc-2.17.so [.] malloc_consolidate
5.14% libc-2.17.so [.] _int_malloc
4.77% [kernel] [k] strchr
2.72% libc-2.17.so [.] _int_free
2.50% [kernel] [k] memcpy
2.25% [kernel] [k] format_decode
2.05% libmount.so.1.1.0 [.] 0x00000000000149b1
1.87% [kernel] [k] seq_escape
1.80% [kernel] [k] vsnprintf
1.74% libc-2.17.so [.] __strcmp_sse42
Also autofs regression/nfs regression tests passed without hitting new issues.
(Actually there's one regression in autofs tests, see bug 1083815, but that's
probably caused by bug 1031475)
QE also have done three rounds testings since Snapshot 12 (on snapshot 13, RC-1
and RC-2), no other severe issues found.
So set to VERIFIED.
--
You are receiving this mail because:
You are on the CC list for the bug.