Re: [PATCH 00/10] convert the majority of file systems to mmap_prepare

Lorenzo Stoakes wrote: > This is preferred to the existing f_op->mmap() hook as it does require a > VMA to be established yet, Did you mean ".. doesn't require a VMA to be established yet, ..." David

Re: [PATCH v2 1/9] 9p: Add a migrate_folio method

since. This reduced our success at > defragmenting memory on machines which use 9p heavily. > > Fixes: 80105ed2fd27 (9p: Use netfslib read/write_iter) > Cc: sta...@vger.kernel.org > Cc: David Howells > Cc: v...@lists.linux.dev > Signed-off-by: Matthew Wilcox (Oracle) Reviewed-by: David Howells

Re: [Intel-gfx] A panic and a hang in the i915 drm driver

Jani Nikula wrote: > David, please try [1]. Assuming you mean this: https://patchwork.freedesktop.org/patch/366958/?series=77635&rev=1 yes, that works. Tested-by: David Howells ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.or

Re: [Intel-gfx] A panic and a hang in the i915 drm driver

Here's the dmesg from a successful boot (commit f84e1ba336a4f47ae251e4d2d8a694902571b0df). David --- [0.007455] Normal [mem 0x0001-0x00041fdf] [0.007456] Movable zone start for each node [0.007456] Early memory node ranges [0.007457] node 0: [mem 0x0

[Intel-gfx] A panic and a hang in the i915 drm driver

Hi, I'm seeing the attached oops and panic from the i915 drm driver. I've tried bisecting it, but there's a problem in that one of the merged branches causes the machine to hang without output. The oops for commit c41219fda6e04255c44d37fd2c0d898c1c46abf1 looks like: BUG: kernel NULL pointer de

Re: [Intel-gfx] [RFC][PATCH] wake_up_var() memory ordering

Peter Zijlstra wrote: > I tried using wake_up_var() today and accidentally noticed that it > didn't imply an smp_mb() and specifically requires it through > wake_up_bit() / waitqueue_active(). Thinking about it again, I'm not sure why you need to add the barrier when wake_up() (which this is a w

Re: [Intel-gfx] [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory

Chen Gang wrote: > > Userspace sometimes depends on the name in the guard macro:-/ > > "the guard macro" is only for prevent itself from being included by > multiple times (an id used by itself -- like a handle), it is not an id > to let other files know about it (it is not a normal using way).

Re: [Intel-gfx] [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory

Chen Gang wrote: > For "include/uapi/*", excluding "linux/" sub-directory, let all files' > macro prefix match the standard format, and give related stand comments > for their macro suffix. > > The related standard format is: > > "_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME