From: Ramalingam C <ramalingam.c@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, Lohith BS <lohith.bs@intel.com>
Cc: paulo.r.zanoni@intel.com, jari.tahvanainen@intel.com,
daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
ankit.k.nautiyal@intel.com
Subject: Re: [PATCH i-g-t v11] tests/kms_frontbuffer_tracking: Including DRRS test coverage
Date: Thu, 4 Jan 2018 03:44:10 +0530 [thread overview]
Message-ID: <f0bdc00f-c235-67ba-3d16-9715832f5b93@intel.com> (raw)
In-Reply-To: <20180103192106.dho3w5aw7oar4wzd@intel.com>
On Thursday 04 January 2018 12:51 AM, Rodrigo Vivi wrote:
> On Wed, Jan 03, 2018 at 03:02:07PM +0000, Lohith BS wrote:
>> Dynamic Refresh Rate Switch(DRRS) is used to switch the panel's
>> refresh rate to the lowest vrefresh supported by panel, when frame is
>> not flipped for more than a Sec.
>>
>> In kernel, DRRS uses the front buffer tracking infrastructure.
>> Hence DRRS test coverage is added along with other frontbuffer tracking
>> based features such as FBC and PSR tests.
>>
>> Here, we are testing DRRS with other features in all possible
>> combinations, in all required test cases, to capture any possible
>> regression.
>>
>> v2: Addressed the comments and suggestions from Vlad, Marius.
>> The signoff details from the earlier work are also included.
>>
>> v3: Modified vblank rate calculation by using reply-sequence,
>> provided by drmWaitVBlank, as suggested by Chris Wilson.
>>
>> v4: As suggested from Chris Wilson and Daniel Vetter
>> 1) Avoided using pthread for calculating vblank refresh rate,
>> instead used drmWaitVBlank reply sequence.
>> 2) Avoided using kernel-specific info like transitional delays,
>> instead polling mechanism with timeout is used.
>> 3) Included edp-DRRS as a subtest in kms_frontbuffer_tracking.c,
>> instead of having a separate test.
>>
>> v5: This patch adds DRRS as a new feature in the
>> kms_frontbuffer_tracking IGT.
>> DRRS switch to lower vrefresh rate is tested at slow-draw subtest.
>>
>> Note:
>> 1) Currently kernel doesn't have support to enable and disable
>> the DRRS feature dynamically(as in case of PSR). Hence if the
>> panel supports DRRS it will be enabled by default.
>>
>> This is in continuation of last patch
>> "https://patchwork.freedesktop.org/patch/162726/"
>>
>> v6: This patch adds runtime enable and disable feature for testing DRRS
>>
>> v7: This patch adds runtime enable and disable feature for testing DRRS
>> through debugfs entry "i915_drrs_ctl".
>>
>> v8: Commit message is updated to reflect current implementation.
>>
>> v9: Addressed Paulo Zanoni comments.
>> Check for DRRS_LOW at tests with OFFSCREEN + FBS_INDIVIDUAL.
>>
>> v10: Corrected DRRS state expectation in suspend related subtests.
>>
>> v11: Removing the global flag is_psr_drrs_combo [Rodrigo].
>>
>> Signed-off-by: Lohith BS <lohith.bs@intel.com>
>> Signed-off-by: aknautiy <ankit.k.nautiyal@intel.com>
>> ---
>> tests/kms_frontbuffer_tracking.c | 184 +++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 175 insertions(+), 9 deletions(-)
>>
>> diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
>> index 1601cab..7876a12 100644
>> --- a/tests/kms_frontbuffer_tracking.c
>> +++ b/tests/kms_frontbuffer_tracking.c
>> @@ -34,7 +34,7 @@
>>
>>
>> IGT_TEST_DESCRIPTION("Test the Kernel's frontbuffer tracking mechanism and "
>> - "its related features: FBC and PSR");
>> + "its related features: FBC, PSR and DRRS");
>>
>> /*
>> * One of the aspects of this test is that, for every subtest, we try different
>> @@ -105,8 +105,9 @@ struct test_mode {
>> FEATURE_NONE = 0,
>> FEATURE_FBC = 1,
>> FEATURE_PSR = 2,
>> - FEATURE_COUNT = 4,
>> - FEATURE_DEFAULT = 4,
>> + FEATURE_DRRS = 4,
>> + FEATURE_COUNT = 8,
>> + FEATURE_DEFAULT = 8,
>> } feature;
>>
>> /* Possible pixel formats. We just use FORMAT_DEFAULT for most tests and
>> @@ -156,6 +157,7 @@ struct rect {
>> struct {
>> int fd;
>> int debugfs;
>> + int drrs_debugfs_fd;
>> drmModeResPtr res;
>> drmModeConnectorPtr connectors[MAX_CONNECTORS];
>> drmModeEncoderPtr encoders[MAX_ENCODERS];
>> @@ -182,6 +184,13 @@ struct {
>> .can_test = false,
>> };
>>
>> +#define MAX_DRRS_STATUS_BUF_LEN 256
>> +
>> +struct {
>> + bool can_test;
>> +} drrs = {
>> + .can_test = false,
>> +};
>>
>> #define SINK_CRC_SIZE 12
>> typedef struct {
>> @@ -825,6 +834,64 @@ static void psr_print_status(void)
>> igt_info("PSR status:\n%s\n", buf);
>> }
>>
>> +void drrs_set(unsigned int val)
>> +{
>> + char buf[2];
>> +
>> + igt_debug("Manually %sabling DRRS. %llu\n", val ? "en" : "dis", val);
>> + snprintf(buf, sizeof(buf), "%d", val);
>> + igt_assert_eq(write(drm.drrs_debugfs_fd,
>> + buf, strlen(buf)), strlen(buf));
>> +}
>> +
>> +static bool is_drrs_high(void)
>> +{
>> + char buf[MAX_DRRS_STATUS_BUF_LEN];
>> +
>> + debugfs_read("i915_drrs_status", buf);
>> + return strstr(buf, "DRRS_HIGH_RR");
>> +}
>> +
>> +static bool is_drrs_low(void)
>> +{
>> + char buf[MAX_DRRS_STATUS_BUF_LEN];
>> +
>> + debugfs_read("i915_drrs_status", buf);
>> + return strstr(buf, "DRRS_LOW_RR");
>> +}
>> +
>> +static bool is_drrs_supported(void)
>> +{
>> + char buf[MAX_DRRS_STATUS_BUF_LEN];
>> +
>> + debugfs_read("i915_drrs_status", buf);
>> + return strstr(buf, "DRRS Supported: Yes");
>> +}
>> +
>> +static bool is_drrs_inactive(void)
>> +{
>> + char buf[MAX_DRRS_STATUS_BUF_LEN];
>> +
>> + debugfs_read("i915_drrs_status", buf);
>> +
>> + if (strstr(buf, "No active crtc found"))
>> + return true;
>> + if (strstr(buf, "Idleness DRRS: Disabled"))
>> + return true;
>> + if (strstr(buf, "DRRS Supported : No"))
> sorry for not asking on the previous email, but since drrs status
> print this for other connected outputs I believe this will cause a
> false positive in the case you have
>
> CRTC 1: DP-1:
> VBT: DRRS_type: None
>
> DRRS Supported : No
>
> CRTC 2: eDP-1:
> VBT: DRRS_type: whatever
>
> DRRS Supported : Yes
>
>
> won't it?
Thats a good catch. We should not be deciding inactiveness based on
DRRS_Supported state. as that will be populated for all active crtcs
with yes and nos. our tests didn't catch as they were having single edp
display.
so how about alternatively detecting the drrs_inactive state by negating
the active state of the DRRS. DRRS active state is possible only on one
crtc which has eDP connector.
so func should look like
static bool is_drrs_inactive(void)
{
char buf[MAX_DRRS_STATUS_BUF_LEN];
debugfs_read("i915_drrs_status", buf);
if (strstr(buf, "DRRS_State: "))
return false;
return true;
}
>> + return true;
>> +
>> + return false;
>> +}
>> +
>> +static void drrs_print_status(void)
>> +{
>> + char buf[MAX_DRRS_STATUS_BUF_LEN];
>> +
>> + debugfs_read("i915_drrs_status", buf);
>> + igt_info("DRRS STATUS :\n%s\n", buf);
>> +}
>> +
>> static struct timespec fbc_get_last_action(void)
>> {
>> struct timespec ret = { 0, 0 };
>> @@ -935,10 +1002,17 @@ static bool psr_wait_until_enabled(void)
>> return igt_wait(psr_is_enabled(), 5000, 1);
>> }
>>
>> +static bool drrs_wait_until_rr_switch_to_low(void)
>> +{
>> + return igt_wait(is_drrs_low(), 5000, 1);
>> +}
>> +
>> #define fbc_enable() igt_set_module_param_int("enable_fbc", 1)
>> #define fbc_disable() igt_set_module_param_int("enable_fbc", 0)
>> #define psr_enable() igt_set_module_param_int("enable_psr", 1)
>> #define psr_disable() igt_set_module_param_int("enable_psr", 0)
>> +#define drrs_enable() drrs_set(1)
>> +#define drrs_disable() drrs_set(0)
>>
>> static void get_sink_crc(sink_crc_t *crc, bool mandatory)
>> {
>> @@ -1184,6 +1258,7 @@ static void disable_features(const struct test_mode *t)
>>
>> fbc_disable();
>> psr_disable();
>> + drrs_disable();
>> }
>>
>> static void *busy_thread_func(void *data)
>> @@ -1508,6 +1583,12 @@ static void teardown_crcs(void)
>> igt_pipe_crc_free(pipe_crc);
>> }
>>
>> +static void teardown_drrs(void)
>> +{
>> + if (drm.drrs_debugfs_fd != -1)
>> + close(drm.drrs_debugfs_fd);
>> +}
>> +
>> static bool fbc_supported_on_chipset(void)
>> {
>> char buf[128];
>> @@ -1577,6 +1658,29 @@ static void teardown_psr(void)
>> {
>> }
>>
>> +static void setup_drrs(void)
>> +{
>> + if (get_connector(prim_mode_params.connector_id)->connector_type !=
>> + DRM_MODE_CONNECTOR_eDP) {
>> + igt_info("Can't test DRRS: no usable eDP screen.\n");
>> + return;
>> + }
>> +
>> + if (!is_drrs_supported()) {
>> + igt_info("Can't test DRRS: Not supported.\n");
>> + return;
>> + }
>> +
>> + drm.drrs_debugfs_fd = openat(drm.debugfs, "i915_drrs_ctl", O_WRONLY);
>> +
>> + if (drm.drrs_debugfs_fd > 0) {
>> + drrs.can_test = true;
>> + } else {
>> + igt_info("Can't test DRRS: Debugfs entry i915_drrs_ctl not found.\n");
>> + drrs.can_test = false;
>> + }
>> +}
>> +
>> static void setup_environment(void)
>> {
>> setup_drm();
>> @@ -1584,6 +1688,7 @@ static void setup_environment(void)
>>
>> setup_fbc();
>> setup_psr();
>> + setup_drrs();
>>
>> setup_crcs();
>> }
>> @@ -1596,6 +1701,7 @@ static void teardown_environment(void)
>> teardown_psr();
>> teardown_fbc();
>> teardown_modeset();
>> + teardown_drrs();
>> teardown_drm();
>> }
>>
>> @@ -1662,6 +1768,11 @@ static void do_flush(const struct test_mode *t)
>> #define ASSERT_PSR_ENABLED (1 << 6)
>> #define ASSERT_PSR_DISABLED (1 << 7)
>>
>> +#define DRRS_ASSERT_FLAGS (7 << 8)
>> +#define ASSERT_DRRS_HIGH (1 << 8)
>> +#define ASSERT_DRRS_LOW (1 << 9)
>> +#define ASSERT_DRRS_INACTIVE (1 << 10)
>> +
>> static int adjust_assertion_flags(const struct test_mode *t, int flags)
>> {
>> if (!(flags & DONT_ASSERT_FEATURE_STATUS)) {
>> @@ -1669,12 +1780,17 @@ static int adjust_assertion_flags(const struct test_mode *t, int flags)
>> flags |= ASSERT_FBC_ENABLED;
>> if (!(flags & ASSERT_PSR_DISABLED))
>> flags |= ASSERT_PSR_ENABLED;
>> + if (!((flags & ASSERT_DRRS_LOW) ||
>> + (flags & ASSERT_DRRS_INACTIVE)))
>> + flags |= ASSERT_DRRS_HIGH;
>> }
>>
>> if ((t->feature & FEATURE_FBC) == 0)
>> flags &= ~FBC_ASSERT_FLAGS;
>> if ((t->feature & FEATURE_PSR) == 0)
>> flags &= ~PSR_ASSERT_FLAGS;
>> + if ((t->feature & FEATURE_DRRS) == 0)
>> + flags &= ~DRRS_ASSERT_FLAGS;
>>
>> return flags;
>> }
>> @@ -1706,6 +1822,23 @@ static void do_status_assertions(int flags)
>> return;
>> }
>>
>> + if (flags & ASSERT_DRRS_HIGH) {
>> + if (!is_drrs_high()) {
>> + drrs_print_status();
>> + igt_assert_f(false, "DRRS HIGH\n");
>> + }
>> + } else if (flags & ASSERT_DRRS_LOW) {
>> + if (!drrs_wait_until_rr_switch_to_low()) {
>> + drrs_print_status();
>> + igt_assert_f(false, "DRRS LOW\n");
>> + }
>> + } else if (flags & ASSERT_DRRS_INACTIVE) {
>> + if (!is_drrs_inactive()) {
>> + drrs_print_status();
>> + igt_assert_f(false, "DRRS INACTIVE\n");
>> + }
>> + }
>> +
>> if (flags & ASSERT_FBC_ENABLED) {
>> igt_require(!fbc_not_enough_stolen());
>> igt_require(!fbc_stride_not_supported());
>> @@ -1833,6 +1966,8 @@ static void enable_features_for_test(const struct test_mode *t)
>> fbc_enable();
>> if (t->feature & FEATURE_PSR)
>> psr_enable();
>> + if (t->feature & FEATURE_DRRS)
>> + drrs_enable();
>> }
>>
>> static void check_test_requirements(const struct test_mode *t)
>> @@ -1852,6 +1987,18 @@ static void check_test_requirements(const struct test_mode *t)
>> "Can't test PSR without sink CRCs\n");
>> }
>>
>> + if (t->feature & FEATURE_DRRS)
>> + igt_require_f(drrs.can_test,
>> + "Can't test DRRS with the current outputs\n");
>> +
>> + /*
>> + * In kernel, When PSR is enabled, DRRS will be disabled. So If a test
>> + * case needs DRRS + PSR enabled, that will be skipped.
>> + */
>> + igt_require_f(!((t->feature & FEATURE_PSR) &&
>> + (t->feature & FEATURE_DRRS)),
>> + "Can't test PSR and DRRS together\n");
>> +
>> if (opt.only_pipes != PIPE_COUNT)
>> igt_require(t->pipes == opt.only_pipes);
>> }
>> @@ -1973,7 +2120,7 @@ static void rte_subtest(const struct test_mode *t)
>>
>> unset_all_crtcs();
>> do_assertions(ASSERT_FBC_DISABLED | ASSERT_PSR_DISABLED |
>> - DONT_ASSERT_CRC);
>> + DONT_ASSERT_CRC | ASSERT_DRRS_INACTIVE);
>>
>> enable_prim_screen_and_wait(t);
>> set_cursor_for_test(t, &prim_mode_params);
>> @@ -2065,6 +2212,13 @@ static void draw_subtest(const struct test_mode *t)
>> if (op_disables_psr(t, t->method))
>> assertions |= ASSERT_PSR_DISABLED;
>>
>> + /*
>> + * On FBS_INDIVIDUAL, write to offscreen plane will not touch the
>> + * current frambuffer. Hence assert for DRRS_LOW.
>> + */
>> + if ((t->fbs == FBS_INDIVIDUAL) && (t->screen == SCREEN_OFFSCREEN))
>> + assertions |= ASSERT_DRRS_LOW;
>> +
>> prepare_subtest(t, pattern);
>> target = pick_target(t, params);
>>
>> @@ -2273,7 +2427,11 @@ static void slow_draw_subtest(const struct test_mode *t)
>> sleep(2);
>>
>> update_wanted_crc(t, &pattern->crcs[t->format][r]);
>> - do_assertions(0);
>> +
>> + if (t->feature & FEATURE_DRRS)
>> + do_assertions(ASSERT_DRRS_LOW);
>> + else
>> + do_assertions(0);
>> }
>> }
>>
>> @@ -2882,17 +3040,17 @@ static void suspend_subtest(const struct test_mode *t)
>> sleep(5);
>> igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);
>> sleep(5);
>> - do_assertions(0);
>> + do_assertions(ASSERT_DRRS_LOW);
>>
>> unset_all_crtcs();
>> sleep(5);
>> igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);
>> sleep(5);
>> do_assertions(ASSERT_FBC_DISABLED | ASSERT_PSR_DISABLED |
>> - DONT_ASSERT_CRC);
>> + DONT_ASSERT_CRC | ASSERT_DRRS_INACTIVE);
>>
>> set_mode_for_params(params);
>> - do_assertions(0);
>> + do_assertions(ASSERT_DRRS_HIGH);
> I don't understand why we had this do_assertions(0) here,
> but how sure you are that this is high and previous is low?
Actually passing 0 or ASSERT_DRRS_HIGH to do_assertion is same. if DRRS
is enabled and assert flag doesn't have DRRS_LOW || DRRS_INACTIVE,
adjust_assertion_flags() will set ASSERT_DRRS_HIGH in the flag.
i.e If a feature is enabled but no assert flag is passed for that
feature adjust_assertion_flags() sets the default state of the features
as assert flag.
so yes do_assertions(0) shouldn't be touched at its last occurrence.
regarding high and low state expectation: at earlier stage we have the
delay of 5Sec after resume with all crtcs on. so if DRRS is enabled, its
state will be DRRS_LOW.
In middle stage, since no active crtc, DRRS will be inactive. And in
later stage after mode set there is not enough delay to enter into
DRRS_LOW so DRRS_HIGH should be expected.
Above DRRS state expectation theory is tested to be correct on GLK and
other platforms.
-Ram
>
>> }
>>
>> /**
>> @@ -3371,6 +3529,14 @@ static const char *feature_str(int feature)
>> return "psr";
>> case FEATURE_FBC | FEATURE_PSR:
>> return "fbcpsr";
>> + case FEATURE_DRRS:
>> + return "drrs";
>> + case FEATURE_FBC | FEATURE_DRRS:
>> + return "fbcdrrs";
>> + case FEATURE_PSR | FEATURE_DRRS:
>> + return "psrdrrs";
>> + case FEATURE_FBC | FEATURE_PSR | FEATURE_DRRS:
>> + return "fbcpsrdrrs";
>> default:
>> igt_assert(false);
>> }
>> @@ -3635,7 +3801,7 @@ int main(int argc, char *argv[])
>> tilingchange_subtest(&t);
>> }
>>
>> - if (t.feature & FEATURE_PSR)
>> + if ((t.feature & FEATURE_PSR) || (t.feature & FEATURE_DRRS))
>> igt_subtest_f("%s-slowdraw", feature_str(t.feature))
>> slow_draw_subtest(&t);
>>
>> --
>> 1.9.1
>>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-03 22:18 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1505724732-17529-1-git-send-email-lohith.bs@intel.com>
2017-09-18 19:54 ` [PATCH] Idleness DRRS: Rodrigo Vivi
2017-09-19 10:46 ` Ramalingam C
2017-09-19 18:12 ` Rodrigo Vivi
2017-10-31 9:20 ` [PATCH 0/2] DRRS coverage in frontbuffer tracking IGT Ramalingam C
2017-10-31 9:20 ` [PATCH 1/2] drm/i915: Runtime disable for eDP DRRS Ramalingam C
2017-10-31 18:57 ` Rodrigo Vivi
2017-11-01 16:44 ` C, Ramalingam
2017-11-07 18:38 ` [PATCH v2 " Ramalingam C
2017-11-17 18:53 ` Rodrigo Vivi
2017-11-19 14:55 ` C, Ramalingam
2017-11-21 20:59 ` Rodrigo Vivi
2017-10-31 9:20 ` [PATCH 2/2] i915/drrs/debugfs: module param and psr status Ramalingam C
2017-11-07 18:40 ` [PATCH v2 2/2] i915/drrs/debugfs: crtc id " Ramalingam C
2017-11-17 18:56 ` Rodrigo Vivi
2017-11-20 3:39 ` C, Ramalingam
2017-11-20 4:23 ` [PATCH v3] i915/drrs/debugfs: psr status info addition Ramalingam C
2017-11-21 20:56 ` Rodrigo Vivi
2017-10-31 9:20 ` [PATCH i-g-t] tests/kms_frontbuffer_tracking: Idleness DRRS coverage Ramalingam C
2017-11-10 16:22 ` [PATCH i-g-t] Idleness DRRS: Lohith BS
2017-12-06 15:13 ` [PATCH i-g-t v8] tests/kms_frontbuffer_tracking: Including DRRS test coverage Lohith BS
2017-12-06 18:30 ` Paulo Zanoni
2017-12-11 13:12 ` [PATCH i-g-t v9] " Lohith BS
2018-01-01 13:45 ` [PATCH i-g-t v10] " Lohith BS
2018-01-02 20:34 ` Rodrigo Vivi
2018-01-03 16:02 ` Bs, Lohith
2018-01-03 15:02 ` [PATCH i-g-t v11] " Lohith BS
2018-01-03 19:21 ` Rodrigo Vivi
2018-01-03 22:14 ` Ramalingam C [this message]
2018-01-05 11:40 ` [PATCH i-g-t v12] " Lohith BS
2018-01-05 17:55 ` Rodrigo Vivi
2018-01-06 10:48 ` Ramalingam C
2018-01-06 13:37 ` Ramalingam C
2018-01-10 14:47 ` [PATCH i-g-t v13] " Lohith BS
2018-01-10 18:15 ` Rodrigo Vivi
2018-01-11 5:27 ` Ramalingam C
2018-01-11 20:22 ` Rodrigo Vivi
2018-01-11 8:40 ` Daniel Vetter
2018-01-17 5:05 ` Ramalingam C
2017-10-31 9:28 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Runtime disable for eDP DRRS Patchwork
2017-10-31 9:48 ` ✓ Fi.CI.BAT: success " Patchwork
2017-10-31 10:33 ` ✗ Fi.CI.BAT: warning for tests/kms_frontbuffer_tracking: Idleness DRRS coverage Patchwork
2017-11-08 7:26 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915: Runtime disable for eDP DRRS (rev3) Patchwork
2017-11-08 8:11 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-10 16:49 ` ✗ Fi.CI.BAT: warning for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev2) Patchwork
2017-11-20 4:46 ` ✗ Fi.CI.BAT: warning for series starting with [v2,1/2] drm/i915: Runtime disable for eDP DRRS (rev4) Patchwork
2017-12-06 16:32 ` ✗ Fi.CI.BAT: warning for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev3) Patchwork
2017-12-11 15:56 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev4) Patchwork
2017-12-11 17:11 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-12-28 15:59 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915: Runtime disable for eDP DRRS (rev4) Patchwork
2017-12-28 16:45 ` ✓ Fi.CI.IGT: " Patchwork
2018-01-02 10:37 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev5) Patchwork
2018-01-02 13:26 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-03 15:30 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev6) Patchwork
2018-01-03 18:49 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-05 12:04 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev7) Patchwork
2018-01-05 13:25 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-10 15:11 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: Idleness DRRS coverage (rev8) Patchwork
2018-01-10 16:14 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-19 10:14 ` [PATCH] Idleness DRRS: Ramalingam C
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=f0bdc00f-c235-67ba-3d16-9715832f5b93@intel.com \
--to=ramalingam.c@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=lohith.bs@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox