dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Matthew Brost" <matthew.brost@intel.com>,
	oak.zeng@intel.com, "Dave Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Christian König" <christian.koenig@amd.com>
Subject: Cross-device and cross-driver HMM support
Date: Wed, 27 Mar 2024 10:52:35 +0100	[thread overview]
Message-ID: <bc4c7b5f19e6479a002ef69949918a45ca89ce69.camel@linux.intel.com> (raw)

Hi!

With our SVM mirror work we'll soon start looking at HMM cross-device
support. The identified needs are

1) Instead of migrating foreign device memory to system when the
current device is faulting, leave it in place...
1a) for access using internal interconnect,
1b) for access using PCIE p2p (probably mostly as a reference)

2) Request a foreign device to migrate memory range a..b of a CPU
mm_struct to local shareable device memory on that foreign device.

and we plan to add an infrastructure for this. Probably this can be
done initially without too much (or any) changes to the hmm code
itself.

So the question is basically whether anybody is interested in a 
drm-wide solution for this and in that case also whether anybody sees
the need for cross-driver support?

Otherwise any objections against us starting out with an xe driver
helper implementation that could be lifted to drm-level when needed?

Finally any suggestions or pointers to existing solutions for this?

Any comments / suggestions greatly appreciated.

Thanks,
Thomas


             reply	other threads:[~2024-03-27  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  9:52 Thomas Hellström [this message]
2024-04-02 22:57 ` Cross-device and cross-driver HMM support Dave Airlie
2024-04-03  9:16   ` Christian König
2024-04-03 12:57     ` Jason Gunthorpe
2024-04-03 14:06       ` Christian König
2024-04-03 15:09         ` Jason Gunthorpe
2024-04-09 10:18           ` Thomas Hellström

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=bc4c7b5f19e6479a002ef69949918a45ca89ce69.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=oak.zeng@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