From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [RFC PATCH 1/5] drm/xe: Add LRC ctx timestamp support functions
Date: Fri, 07 Jun 2024 10:10:54 +0300 [thread overview]
Message-ID: <87bk4dmdmp.fsf@intel.com> (raw)
In-Reply-To: <20240607065219.2264624-2-matthew.brost@intel.com>
On Thu, 06 Jun 2024, Matthew Brost <matthew.brost@intel.com> wrote:
> +static inline u32 __xe_lrc_ctx_timestamp_job_offset(struct xe_lrc *lrc)
Please don't use the inline keyword in .c files, no matter how simple
the function. Just let the compiler do its job of inlining as
needed. Using inline also silences warnings about unused static
functions.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-06-07 7:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 6:52 [RFC PATCH 0/5] Only timeout jobs if they run longer than timeout period Matthew Brost
2024-06-07 6:52 ` [RFC PATCH 1/5] drm/xe: Add LRC ctx timestamp support functions Matthew Brost
2024-06-07 7:10 ` Jani Nikula [this message]
2024-06-07 15:16 ` Matthew Brost
2024-06-07 6:52 ` [RFC PATCH 2/5] drm/xe: Add MI_COPY_MEM_MEM GPU instruction definitions Matthew Brost
2024-06-07 11:04 ` Michal Wajdeczko
2024-06-07 15:22 ` Matthew Brost
2024-06-07 6:52 ` [RFC PATCH 3/5] drm/xe: Emit ctx timestamp copy in ring ops Matthew Brost
2024-06-07 6:52 ` [RFC PATCH 4/5] drm/xe: Add ctx timestamp to LRC snapshot Matthew Brost
2024-06-07 6:52 ` [RFC PATCH 5/5] drm/xe: Sample ctx timestamp to determine if jobs have timed out Matthew Brost
2024-06-07 6:56 ` ✓ CI.Patch_applied: success for Only timeout jobs if they run longer than timeout period Patchwork
2024-06-07 6:56 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-07 6:57 ` ✓ CI.KUnit: success " Patchwork
2024-06-07 7:09 ` ✓ CI.Build: " Patchwork
2024-06-07 7:11 ` ✓ CI.Hooks: " Patchwork
2024-06-07 7:13 ` ✓ CI.checksparse: " Patchwork
2024-06-07 15:27 ` ✗ CI.FULL: failure " 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=87bk4dmdmp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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