From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Arjun Melkaveri <arjun.melkaveri@intel.com>
Cc: zbigniew.kempczynski@intel.com, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/gem_ctx_persistence: modified test_saturated_hostile subtest
Date: Thu, 02 Sep 2021 16:33:23 -0700 [thread overview]
Message-ID: <87ilzilfi4.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20210902153800.14831-1-arjun.melkaveri@intel.com>
On Thu, 02 Sep 2021 08:38:00 -0700, Arjun Melkaveri wrote:
>
> Applying saturated_hostile to support for twiddling the
> scheduling parameters via sysfs to tune timeouts.
Can you explain the motivation for this? Why this was not done previously
and why we want to do this now?
next prev parent reply other threads:[~2021-09-02 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 15:38 [igt-dev] [PATCH i-g-t] tests/i915/gem_ctx_persistence: modified test_saturated_hostile subtest Arjun Melkaveri
2021-09-02 16:43 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-09-02 20:49 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-02 23:33 ` Dixit, Ashutosh [this message]
2021-09-03 19:35 ` [igt-dev] [PATCH i-g-t] " Dixit, Ashutosh
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=87ilzilfi4.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=arjun.melkaveri@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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