Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Tomasz Lis <tomasz.lis@intel.com>, intel-xe@lists.freedesktop.org
Cc: "Michał Winiarski" <michal.winiarski@intel.com>
Subject: Re: [PATCH v6 0/5] drm/xe/vf: Post-migration recovery worker basis
Date: Wed, 6 Nov 2024 15:33:33 +0100	[thread overview]
Message-ID: <b7ba81a8-bdc8-4ede-b32f-20b30336602f@intel.com> (raw)
In-Reply-To: <464fa43f-c1eb-4a04-a0c2-07d614c6915a@intel.com>



On 06.11.2024 14:09, Michal Wajdeczko wrote:
> 
> 
> On 04.11.2024 22:34, Tomasz Lis wrote:
>> To support VF Migration, it is necessary to do fixups to any
>> non-virtualized resources. These fixups need to be applied within
>> VM, on the KMD working with VF.
>>
>> This series introduces a post-migration recovery worker, executed
>> after migration to perform fixups.
>>
>> Specific fixups will be added later in further series.
>>
>> v2: renamed and moved functions, updated logged messages, removed
>>   unused includes, used anon struct, keeping pm ref during whole
>>   recovery, skip handshake, style fixes (Michal)
>> v3: ordering, kerneldoc, asserts, debug messages, on_all_tiles ->
>>   on_all_gts, switched 'err' and 'ret'  (Michal)
>> v4: fixed missing header include in one patch
>> v5: Explained what fixups are, explained which IRQ is used, style
>>   fixes, assert to separate patch, debug message per GuC instead
>>   of one, comments changes (Michal)
>> v6: Improved documentation patch, updated one debug message
>>
> 
> series LGTM,
> 
> Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> 
> 
>> Tomasz Lis (5):
>>   drm/xe/vf: React to MIGRATED interrupt
>>   drm/xe/vf: Document SRIOV VF restore flow

used v3 with DOC in .c

>>   drm/xe/vf: Send RESFIX_DONE message at end of VF restore
>>   drm/xe/vf: Start post-migration fixups with provisinoning query

fixed typo

>>   drm/xe/vf: Defer fixups if migrated twice fast

and applied to drm-xe-next



      reply	other threads:[~2024-11-06 14:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 21:34 [PATCH v6 0/5] drm/xe/vf: Post-migration recovery worker basis Tomasz Lis
2024-11-04 21:34 ` [PATCH v6 1/5] drm/xe/vf: React to MIGRATED interrupt Tomasz Lis
2024-11-04 21:34 ` [PATCH v6 2/5] drm/xe/vf: Document SRIOV VF restore flow Tomasz Lis
2024-11-06 14:15   ` [PATCH v3 " Michal Wajdeczko
2024-11-04 21:34 ` [PATCH v6 3/5] drm/xe/vf: Send RESFIX_DONE message at end of VF restore Tomasz Lis
2024-11-04 21:34 ` [PATCH v6 4/5] drm/xe/vf: Start post-migration fixups with provisinoning query Tomasz Lis
2024-11-04 21:34 ` [PATCH v6 5/5] drm/xe/vf: Defer fixups if migrated twice fast Tomasz Lis
2024-11-05  0:35 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery worker basis (rev6) Patchwork
2024-11-05  0:35 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-05  0:36 ` ✓ CI.KUnit: success " Patchwork
2024-11-05  0:48 ` ✓ CI.Build: " Patchwork
2024-11-05  0:50 ` ✓ CI.Hooks: " Patchwork
2024-11-05  0:51 ` ✓ CI.checksparse: " Patchwork
2024-11-05  1:13 ` ✓ CI.BAT: " Patchwork
2024-11-06  1:10 ` ✗ CI.FULL: failure " Patchwork
2024-11-06 13:09 ` [PATCH v6 0/5] drm/xe/vf: Post-migration recovery worker basis Michal Wajdeczko
2024-11-06 14:33   ` Michal Wajdeczko [this message]

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=b7ba81a8-bdc8-4ede-b32f-20b30336602f@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.winiarski@intel.com \
    --cc=tomasz.lis@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