All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/userptr: Acquire the page lock around set_page_dirty()
Date: Tue, 09 Jul 2019 00:45:12 +0000	[thread overview]
Message-ID: <20190709004513.002A62173C@mail.kernel.org> (raw)
In-Reply-To: <20190708140327.26825-1-chris@chris-wilson.co.uk>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 5cc9ed4b9a7a drm/i915: Introduce mapping of user pages into video memory (userptr) ioctl.

The bot has tested the following trees: v5.1.16, v4.19.57, v4.14.132, v4.9.184, v4.4.184.

v5.1.16: Build OK!
v4.19.57: Build OK!
v4.14.132: Build OK!
v4.9.184: Failed to apply! Possible dependencies:
    0e70447605f4 ("drm/i915: Move common code out of i915_gpu_error.c")
    1b36595ffb35 ("drm/i915: Show RING registers through debugfs")
    275f039db56f ("drm/i915: Move user fault tracking to a separate list")
    3594a3e21f1f ("drm/i915: Remove superfluous locking around userfault_list")
    3b3f1650b1ca ("drm/i915: Allocate intel_engine_cs structure only for the enabled engines")
    7c108fd8feac ("drm/i915: Move fence cancellation to runtime suspend")
    8baa1f04b9ed ("drm/i915: Update debugfs describe_obj() to show fault-mappable")
    96d776345277 ("drm/i915: Use a radixtree for random access to the object's backing storage")
    9c870d03674f ("drm/i915: Use RPM as the barrier for controlling user mmap access")
    a4f5ea64f0a8 ("drm/i915: Refactor object page API")
    d636951ec01b ("drm/i915: Cleanup instdone collection")
    f8a7fde45610 ("drm/i915: Defer active reference until required")

v4.4.184: Failed to apply! Possible dependencies:
    09cbfeaf1a5a ("mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release} macros")
    0a798eb92e6d ("drm/i915: Refactor duplicate object vmap functions")
    0b5372727be3 ("drm/i915/cmdparser: Use cached vmappings")
    0e749e54244e ("dax: increase granularity of dax_clear_blocks() operations")
    0eb973d31d0a ("drm/i915: Cache ringbuffer GTT VMA")
    43394c7d0d36 ("drm/i915: Extract i915_gem_obj_prepare_shmem_write()")
    4420cfd3f51c ("staging: lustre: format properly all comment blocks for LNet core")
    52db400fcd50 ("pmem, dax: clean up clear_pmem()")
    5fd88337d209 ("staging: lustre: fix all conditional comparison to zero in LNet layer")
    85d1225ec066 ("drm/i915: Introduce & use new lightweight SGL iterators")
    a188222b6ed2 ("net: Rename NETIF_F_ALL_CSUM to NETIF_F_CSUM_MASK")
    a4f5ea64f0a8 ("drm/i915: Refactor object page API")
    b2e0d1625e19 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()")
    b9bcd14a2b91 ("drm/i915: Extract checking for backing struct pages to a helper")
    d1a5f2b4d8a1 ("block: use DAX for partition table reads")
    def0c5f6b0cd ("drm/i915: Map the ringbuffer using WB on LLC machines")
    e10624f8c097 ("pmem: fail io-requests to known bad blocks")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

--
Thanks,
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-09  0:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 14:03 [PATCH] drm/i915/userptr: Acquire the page lock around set_page_dirty() Chris Wilson
2019-07-08 15:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-07-08 23:48 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-09  0:45 ` Sasha Levin [this message]
2019-07-09  6:24 ` [Intel-gfx] [PATCH] " Tvrtko Ursulin

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=20190709004513.002A62173C@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.