From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH] fixup! drm/xe: Add CONFIG_DRM_XE_PREEMPT_TIMEOUT
Date: Wed, 16 Aug 2023 22:19:25 +0530 [thread overview]
Message-ID: <450eb430-dcf0-4ed1-958e-11880f5aefea@intel.com> (raw)
In-Reply-To: <20230816164431.6680-1-niranjana.vishwanathapura@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On 16-08-2023 22:14, Niranjana Vishwanathapura wrote:
> Remove unwanted documentation
>
> Signed-off-by: Niranjana Vishwanathapura<niranjana.vishwanathapura@intel.com>
LGTM.
Reviewed-by:Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> ---
> drivers/gpu/drm/xe/Kconfig.profile | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/Kconfig.profile b/drivers/gpu/drm/xe/Kconfig.profile
> index a3655ee6978e..4bc080547d5f 100644
> --- a/drivers/gpu/drm/xe/Kconfig.profile
> +++ b/drivers/gpu/drm/xe/Kconfig.profile
> @@ -30,9 +30,6 @@ config DRM_XE_PREEMPT_TIMEOUT
> when submitting a new context. If the current context does not hit
> an arbitration point and yield to HW before the timer expires, the
> HW will be reset to allow the more important context to execute.
> -
> - Value should be within the DRM_XE_PREEMPT_TIMEOUT_MIN/MAX limits.
> - This is adjustable via XE_ENGINE_SET_PROPERTY_PREEMPTION_TIMEOUT.
> config DRM_XE_PREEMPT_TIMEOUT_MAX
> int "Default max preempt timeout (us)"
> default 10000000 # microseconds
[-- Attachment #2: Type: text/html, Size: 37977 bytes --]
next prev parent reply other threads:[~2023-08-16 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 16:44 [Intel-xe] [PATCH] fixup! drm/xe: Add CONFIG_DRM_XE_PREEMPT_TIMEOUT Niranjana Vishwanathapura
2023-08-16 16:49 ` Ghimiray, Himal Prasad [this message]
2023-08-16 17:19 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-08-16 17:19 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-16 17:20 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-16 17:24 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-16 17:24 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-16 17:25 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-16 17:50 ` [Intel-xe] ✓ CI.BAT: 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=450eb430-dcf0-4ed1-958e-11880f5aefea@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@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