From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Alexey Budankov" <alexey.budankov@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for Introduce CAP_PERFMON to secure system performance monitoring and observability
Date: Tue, 21 Jan 2020 00:15:36 -0000 [thread overview]
Message-ID: <157956573629.11481.7449588890541133927@emeril.freedesktop.org> (raw)
In-Reply-To: <0548c832-7f4b-dc4c-8883-3f2b6d351a08@linux.intel.com>
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and observability
URL : https://patchwork.freedesktop.org/series/72273/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7781 -> Patchwork_16173
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/index.html
Known issues
------------
Here are the changes found in Patchwork_16173 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_blt:
- fi-ivb-3770: [PASS][1] -> [DMESG-FAIL][2] ([i915#725])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-ivb-3770/igt@i915_selftest@live_blt.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-ivb-3770/igt@i915_selftest@live_blt.html
* igt@kms_addfb_basic@too-high:
- fi-icl-dsi: [PASS][3] -> [DMESG-WARN][4] ([i915#109])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-icl-dsi/igt@kms_addfb_basic@too-high.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-icl-dsi/igt@kms_addfb_basic@too-high.html
#### Possible fixes ####
* igt@i915_selftest@live_blt:
- fi-hsw-4770r: [DMESG-FAIL][5] ([i915#553] / [i915#725]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-hsw-4770r/igt@i915_selftest@live_blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-hsw-4770r/igt@i915_selftest@live_blt.html
- fi-hsw-4770: [DMESG-FAIL][7] ([i915#725]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-hsw-4770/igt@i915_selftest@live_blt.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-hsw-4770/igt@i915_selftest@live_blt.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][9] ([fdo#111407]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@gem_exec_parallel@contexts:
- fi-byt-n2820: [TIMEOUT][11] ([fdo#112271]) -> [INCOMPLETE][12] ([i915#45])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-byt-n2820/igt@gem_exec_parallel@contexts.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/fi-byt-n2820/igt@gem_exec_parallel@contexts.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
[i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
[i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
[i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
[i915#937]: https://gitlab.freedesktop.org/drm/intel/issues/937
Participating hosts (50 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-bwr-2160 fi-ctg-p8600 fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7781 -> Patchwork_16173
CI-20190529: 20190529
CI_DRM_7781: 3f2b341ae1fde67f823aeb715c6f489affdef8b1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5374: 83c32e859202e43ff6a8cca162c76fcd90ad6e3b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16173: c7304fe7a4108ae62e23c1b6786a813e0cfb66db @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
c7304fe7a410 drivers/oprofile: open access for CAP_PERFMON privileged process
0515549093ae drivers/perf: open access for CAP_PERFMON privileged process
035c1d9fc22b parisc/perf: open access for CAP_PERFMON privileged process
d3168511835d powerpc/perf: open access for CAP_PERFMON privileged process
dc5f0cb73803 trace/bpf_trace: open access for CAP_PERFMON privileged process
0df0e7d3bc27 drm/i915/perf: open access for CAP_PERFMON privileged process
eca88405d138 perf tool: extend Perf tool with CAP_PERFMON capability support
c74fee681ffe perf/core: open access to anon probes for CAP_PERFMON privileged process
b04501d7d623 perf/core: open access to the core for CAP_PERFMON privileged process
08ee25620fef capabilities: introduce CAP_PERFMON to kernel and user space
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16173/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-21 0:15 UTC|newest]
Thread overview: 163+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 11:18 [PATCH v5 0/10] Introduce CAP_PERFMON to secure system performance monitoring and observability Alexey Budankov
2020-01-20 11:18 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:18 ` Alexey Budankov
2020-01-20 11:18 ` Alexey Budankov
2020-01-20 11:18 ` Alexey Budankov
2020-01-20 11:23 ` [PATCH v5 01/10] capabilities: introduce CAP_PERFMON to kernel and user space Alexey Budankov
2020-01-20 11:23 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:23 ` Alexey Budankov
2020-01-20 11:23 ` Alexey Budankov
2020-01-20 11:23 ` Alexey Budankov
2020-01-21 14:43 ` Stephen Smalley
2020-01-21 14:43 ` [Intel-gfx] " Stephen Smalley
2020-01-21 14:43 ` Stephen Smalley
2020-01-21 14:43 ` Stephen Smalley
2020-01-21 14:43 ` Stephen Smalley
2020-01-21 17:30 ` Alexey Budankov
2020-01-21 17:30 ` [Intel-gfx] " Alexey Budankov
2020-01-21 17:30 ` Alexey Budankov
2020-01-21 17:30 ` Alexey Budankov
2020-01-21 17:30 ` Alexey Budankov
2020-01-21 17:55 ` Alexei Starovoitov
2020-01-21 17:55 ` [Intel-gfx] " Alexei Starovoitov
2020-01-21 17:55 ` Alexei Starovoitov
2020-01-21 17:55 ` Alexei Starovoitov
2020-01-21 17:55 ` Alexei Starovoitov
2020-01-21 18:27 ` Alexey Budankov
2020-01-21 18:27 ` [Intel-gfx] " Alexey Budankov
2020-01-21 18:27 ` Alexey Budankov
2020-01-21 18:27 ` Alexey Budankov
2020-01-21 18:27 ` Alexey Budankov
2020-01-22 10:45 ` Alexey Budankov
2020-01-22 10:45 ` [Intel-gfx] " Alexey Budankov
2020-01-22 10:45 ` Alexey Budankov
2020-01-22 10:45 ` Alexey Budankov
2020-01-22 10:45 ` Alexey Budankov
2020-01-22 14:07 ` Stephen Smalley
2020-01-22 14:07 ` [Intel-gfx] " Stephen Smalley
2020-01-22 14:07 ` Stephen Smalley
2020-01-22 14:07 ` Stephen Smalley
2020-01-22 14:07 ` Stephen Smalley
2020-01-22 14:25 ` Alexey Budankov
2020-01-22 14:25 ` [Intel-gfx] " Alexey Budankov
2020-01-22 14:25 ` Alexey Budankov
2020-01-22 14:25 ` Alexey Budankov
2020-01-22 14:25 ` Alexey Budankov
2020-02-06 18:03 ` Alexey Budankov
2020-02-06 18:03 ` [Intel-gfx] " Alexey Budankov
2020-02-06 18:03 ` Alexey Budankov
2020-02-06 18:03 ` Alexey Budankov
2020-02-06 18:03 ` Alexey Budankov
2020-02-07 11:38 ` Thomas Gleixner
2020-02-07 11:38 ` [Intel-gfx] " Thomas Gleixner
2020-02-07 11:38 ` Thomas Gleixner
2020-02-07 11:38 ` Thomas Gleixner
2020-02-07 11:38 ` Thomas Gleixner
2020-02-07 13:39 ` Alexey Budankov
2020-02-07 13:39 ` [Intel-gfx] " Alexey Budankov
2020-02-07 13:39 ` Alexey Budankov
2020-02-07 13:39 ` Alexey Budankov
2020-02-07 13:39 ` Alexey Budankov
2020-02-20 13:05 ` Alexey Budankov
2020-02-20 13:05 ` [Intel-gfx] " Alexey Budankov
2020-02-20 13:05 ` Alexey Budankov
2020-02-20 13:05 ` Alexey Budankov
2020-02-20 13:05 ` Alexey Budankov
2020-02-12 8:53 ` Alexey Budankov
2020-02-12 8:53 ` [Intel-gfx] " Alexey Budankov
2020-02-12 8:53 ` Alexey Budankov
2020-02-12 8:53 ` Alexey Budankov
2020-02-12 8:53 ` Alexey Budankov
2020-02-12 13:32 ` Stephen Smalley
2020-02-12 13:32 ` [Intel-gfx] " Stephen Smalley
2020-02-12 13:32 ` Stephen Smalley
2020-02-12 13:32 ` Stephen Smalley
2020-02-12 13:32 ` Stephen Smalley
2020-02-12 13:53 ` Alexey Budankov
2020-02-12 13:53 ` [Intel-gfx] " Alexey Budankov
2020-02-12 13:53 ` Alexey Budankov
2020-02-12 13:53 ` Alexey Budankov
2020-02-12 13:53 ` Alexey Budankov
2020-02-12 15:21 ` Stephen Smalley
2020-02-12 15:21 ` [Intel-gfx] " Stephen Smalley
2020-02-12 15:21 ` Stephen Smalley
2020-02-12 15:21 ` Stephen Smalley
2020-02-12 15:21 ` Stephen Smalley
2020-02-12 15:45 ` Stephen Smalley
2020-02-12 15:45 ` [Intel-gfx] " Stephen Smalley
2020-02-12 15:45 ` Stephen Smalley
2020-02-12 15:45 ` Stephen Smalley
2020-02-12 15:45 ` Stephen Smalley
2020-02-12 16:56 ` Alexey Budankov
2020-02-12 16:56 ` [Intel-gfx] " Alexey Budankov
2020-02-12 16:56 ` Alexey Budankov
2020-02-12 16:56 ` Alexey Budankov
2020-02-12 16:56 ` Alexey Budankov
2020-02-12 17:09 ` Stephen Smalley
2020-02-12 17:09 ` [Intel-gfx] " Stephen Smalley
2020-02-12 17:09 ` Stephen Smalley
2020-02-12 17:09 ` Stephen Smalley
2020-02-12 17:09 ` Stephen Smalley
2020-02-13 9:05 ` Alexey Budankov
2020-02-13 9:05 ` [Intel-gfx] " Alexey Budankov
2020-02-13 9:05 ` Alexey Budankov
2020-02-13 9:05 ` Alexey Budankov
2020-02-13 9:05 ` Alexey Budankov
2020-02-12 16:16 ` Alexey Budankov
2020-02-12 16:16 ` [Intel-gfx] " Alexey Budankov
2020-02-12 16:16 ` Alexey Budankov
2020-02-12 16:16 ` Alexey Budankov
2020-02-12 16:16 ` Alexey Budankov
2020-01-20 11:24 ` [PATCH v5 02/10] perf/core: open access to the core for CAP_PERFMON privileged process Alexey Budankov
2020-01-20 11:24 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:24 ` Alexey Budankov
2020-01-20 11:24 ` Alexey Budankov
2020-01-20 11:24 ` Alexey Budankov
2020-01-20 11:26 ` [PATCH v5 03/10] perf/core: open access to anon probes " Alexey Budankov
2020-01-20 11:26 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:26 ` Alexey Budankov
2020-01-20 11:26 ` Alexey Budankov
2020-01-20 11:26 ` Alexey Budankov
2020-01-20 11:27 ` [PATCH v5 04/10] perf tool: extend Perf tool with CAP_PERFMON capability support Alexey Budankov
2020-01-20 11:27 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:27 ` Alexey Budankov
2020-01-20 11:27 ` Alexey Budankov
2020-01-20 11:27 ` Alexey Budankov
2020-01-20 11:28 ` [PATCH v5 05/10] drm/i915/perf: open access for CAP_PERFMON privileged process Alexey Budankov
2020-01-20 11:28 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:28 ` Alexey Budankov
2020-01-20 11:28 ` Alexey Budankov
2020-01-20 11:28 ` Alexey Budankov
2020-01-20 11:29 ` [PATCH v5 06/10] trace/bpf_trace: " Alexey Budankov
2020-01-20 11:29 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:29 ` Alexey Budankov
2020-01-20 11:29 ` Alexey Budankov
2020-01-20 11:29 ` Alexey Budankov
2020-01-20 11:30 ` [PATCH v5 07/10] powerpc/perf: " Alexey Budankov
2020-01-20 11:30 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:30 ` Alexey Budankov
2020-01-20 11:30 ` Alexey Budankov
2020-01-20 11:30 ` Alexey Budankov
2020-01-22 11:02 ` Anju T Sudhakar
2020-01-22 11:02 ` [Intel-gfx] " Anju T Sudhakar
2020-01-22 11:02 ` Anju T Sudhakar
2020-01-22 11:02 ` Anju T Sudhakar
2020-01-22 11:02 ` Anju T Sudhakar
2020-01-20 11:31 ` [PATCH v5 08/10] parisc/perf: " Alexey Budankov
2020-01-20 11:31 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:31 ` Alexey Budankov
2020-01-20 11:31 ` Alexey Budankov
2020-01-20 11:31 ` Alexey Budankov
2020-01-20 11:32 ` [PATCH v5 09/10] drivers/perf: " Alexey Budankov
2020-01-20 11:32 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:32 ` Alexey Budankov
2020-01-20 11:32 ` Alexey Budankov
2020-01-20 11:32 ` Alexey Budankov
2020-01-20 11:33 ` [PATCH v5 10/10] drivers/oprofile: " Alexey Budankov
2020-01-20 11:33 ` [Intel-gfx] " Alexey Budankov
2020-01-20 11:33 ` Alexey Budankov
2020-01-20 11:33 ` Alexey Budankov
2020-01-20 11:33 ` Alexey Budankov
2020-01-20 16:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability Patchwork
2020-01-21 0:15 ` Patchwork [this message]
2020-01-21 11:00 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=157956573629.11481.7449588890541133927@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=alexey.budankov@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.