From: Matthew Brost <matthew.brost@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v5 2/3] drm/xe/migrate: Make emit_pte() header write atomic
Date: Wed, 8 Oct 2025 16:27:17 -0700 [thread overview]
Message-ID: <aObzVYIXjS+bNjXl@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20251008101145.11506-7-satyanarayana.k.v.p@intel.com>
On Wed, Oct 08, 2025 at 03:41:48PM +0530, Satyanarayana K V P wrote:
> The MI_STORE_DATA_IMM instruction header is quad dword in size. If the
> vCPU halts during save/restore while this sequence is being programmed,
> partial writes may trigger page faults when saving IGPU CCS metadata.
> Update instruction header atomically.
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
>
> ---
> V4 -> V5:
> - Fixed review comments (Matt B).
>
> V3 -> V4:
> - New commit added.
>
> V2 -> V3:
> - None
>
> V1 -> V2:
> - None
> ---
> drivers/gpu/drm/xe/xe_migrate.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_migrate.c b/drivers/gpu/drm/xe/xe_migrate.c
> index b629072956ee..7097da1555ca 100644
> --- a/drivers/gpu/drm/xe/xe_migrate.c
> +++ b/drivers/gpu/drm/xe/xe_migrate.c
> @@ -607,9 +607,14 @@ static void emit_pte(struct xe_migrate *m,
>
> while (ptes) {
> u32 chunk = min(MAX_PTE_PER_SDI, ptes);
> + u32 dw[SZ_2], i = 0;
> +
> + dw[i++] = MI_STORE_DATA_IMM | MI_SDI_NUM_QW(chunk);
> + dw[i++] = ofs;
> +
> + WRITE_ONCE(*(u64 *)&bb->cs[bb->len], *(u64 *)dw);
> + bb->len += i;
>
> - bb->cs[bb->len++] = MI_STORE_DATA_IMM | MI_SDI_NUM_QW(chunk);
> - bb->cs[bb->len++] = ofs;
> bb->cs[bb->len++] = 0;
I think you actually need an emit_atomic here. I just read the bsepc and
the last dw enforces some msb restrictions so the 3 dw must be written
atomically. I believe it is safe to write out 4 dw in the atomic
instruction but only increment bb->len by 3.
Matt
>
> cur_ofs = ofs;
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-10-08 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 10:11 [PATCH v5 0/3] drm/xe/migrate: Atomicize CCS copy command setup Satyanarayana K V P
2025-10-08 10:11 ` [PATCH v5 1/3] " Satyanarayana K V P
2025-10-08 22:58 ` Matthew Brost
2025-10-09 13:00 ` Rodrigo Vivi
2025-10-09 16:11 ` Matthew Brost
2025-10-09 18:35 ` Rodrigo Vivi
2025-10-09 18:49 ` Matthew Brost
2025-10-09 19:49 ` Rodrigo Vivi
2025-10-09 20:34 ` Michal Wajdeczko
2025-10-09 23:06 ` Matt Roper
2025-10-10 8:41 ` K V P, Satyanarayana
2025-10-10 19:13 ` Rodrigo Vivi
2025-10-13 4:42 ` K V P, Satyanarayana
2025-10-08 10:11 ` [PATCH v5 2/3] drm/xe/migrate: Make emit_pte() header write atomic Satyanarayana K V P
2025-10-08 23:27 ` Matthew Brost [this message]
2025-10-08 10:11 ` [PATCH v5 3/3] drm/xe/vf: Clear CCS read/write buffers in atomic way Satyanarayana K V P
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=aObzVYIXjS+bNjXl@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=satyanarayana.k.v.p@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