Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for mm/hmm, mm/migrate_device: Allow p2p access and p2p migration (rev2)
Date: Wed, 16 Oct 2024 06:20:46 -0000	[thread overview]
Message-ID: <172905964643.1272209.500341486061228131@2413ebb6fbb6> (raw)
In-Reply-To: <20241015111322.97514-1-thomas.hellstrom@linux.intel.com>

== Series Details ==

Series: mm/hmm, mm/migrate_device: Allow p2p access and p2p migration (rev2)
URL   : https://patchwork.freedesktop.org/series/139995/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit b74058545e0dabebe267c77fc4b618db9da461f4
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Date:   Tue Oct 15 13:13:22 2024 +0200

    mm/hmm, mm/migrate_device: Allow p2p access and p2p migration
    
    Introduce a way for hmm_range_fault() and migrate_vma_setup() to identify
    foreign devices with fast interconnect and thereby allow
    both direct access over the interconnect and p2p migration.
    
    The need for a callback arises because without it, the p2p ability would
    need to be static and determined at dev_pagemap creation time. With
    a callback it can be determined dynamically, and in the migrate case
    the callback could separate out local device pages.
    
    The hmm_range_fault() change has been tested internally, the
    migrate_vma_setup() change hasn't yet.
    
    Seeking early feedback. Any suggestions appreciated.
    
    Cc: Matthew Brost <matthew.brost@intel.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Simona Vetter <simona.vetter@ffwll.ch>
    Cc: DRI-devel <dri-devel@lists.freedesktop.org>
    Cc: Linux Memory Management List <linux-mm@kvack.org>
    Cc: LKML <linux-kernel@vger.kernel.org>
    
    Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
+ /mt/dim checkpatch 01c7b2c084e5c84313f382734c10945b9aa49823 drm-intel
b74058545e0d mm/hmm, mm/migrate_device: Allow p2p access and p2p migration



  parent reply	other threads:[~2024-10-16  6:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:13 [RFC PATCH] mm/hmm, mm/migrate_device: Allow p2p access and p2p migration Thomas Hellström
2024-10-15 11:21 ` Thomas Hellström
2024-10-15 12:17 ` Jason Gunthorpe
2024-10-15 12:41   ` Thomas Hellström
2024-10-15 13:02     ` Jason Gunthorpe
2024-10-15 13:17       ` Thomas Hellström
2024-10-16  4:46         ` Alistair Popple
2024-10-15 13:34 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-15 13:35 ` ✓ CI.checkpatch: " Patchwork
2024-10-15 13:36 ` ✓ CI.KUnit: " Patchwork
2024-10-15 13:47 ` ✓ CI.Build: " Patchwork
2024-10-15 13:50 ` ✓ CI.Hooks: " Patchwork
2024-10-15 13:51 ` ✓ CI.checksparse: " Patchwork
2024-10-15 22:06 ` ✗ CI.FULL: failure " Patchwork
2024-10-16  6:20 ` ✓ CI.Patch_applied: success for mm/hmm, mm/migrate_device: Allow p2p access and p2p migration (rev2) Patchwork
2024-10-16  6:20 ` Patchwork [this message]
2024-10-16  6:21 ` ✓ CI.KUnit: " Patchwork
2024-10-16  6:33 ` ✓ CI.Build: " Patchwork
2024-10-16  6:35 ` ✓ CI.Hooks: " Patchwork
2024-10-16  6:37 ` ✓ CI.checksparse: " Patchwork
2024-10-16  7:00 ` ✓ CI.BAT: " Patchwork
2024-10-16 14:48 ` ✗ 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=172905964643.1272209.500341486061228131@2413ebb6fbb6 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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