[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210206124732.GK2172@grain>
Date: Sat, 6 Feb 2021 15:47:32 +0300
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Chris Wilson <chris@...is-wilson.co.uk>
Cc: linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, Kees Cook <keescook@...omium.org>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Dave Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Lucas Stach <l.stach@...gutronix.de>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
stable@...r.kernel.org, Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [PATCH v3] kcmp: Support selection of SYS_kcmp without
CHECKPOINT_RESTORE
On Fri, Feb 05, 2021 at 10:00:12PM +0000, Chris Wilson wrote:
> Userspace has discovered the functionality offered by SYS_kcmp and has
> started to depend upon it. In particular, Mesa uses SYS_kcmp for
> os_same_file_description() in order to identify when two fd (e.g. device
> or dmabuf) point to the same struct file. Since they depend on it for
> core functionality, lift SYS_kcmp out of the non-default
> CONFIG_CHECKPOINT_RESTORE into the selectable syscall category.
>
...
Reviewed-by: Cyrill Gorcunov <gorcunov@...il.com>
Powered by blists - more mailing lists