linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Jaya Kumar <jayakumar.lkml@gmail.com>,
	Simona Vetter <simona@ffwll.ch>, Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [RFC PATCH v2 0/3] expose mapping wrprotect, fix fb_defio use
Date: Mon, 3 Feb 2025 11:24:50 +0100	[thread overview]
Message-ID: <b284f594-2b28-4c1b-b00e-2fe7e9036b2f@suse.de> (raw)
In-Reply-To: <cover.1736809898.git.lorenzo.stoakes@oracle.com>

Hi


Am 14.01.25 um 00:15 schrieb Lorenzo Stoakes:
[...]
>
> *** REVIEWERS NOTES: ***
>
> I do not have any hardware that uses fb_defio, so I'm asking for help with
> testing this series from those who do :) I have tested the mm side of this,
> and done a quick compile smoke test of the fb_defio side but this _very
> much_ requires testing on actual hardware to ensure everything behaves as
> expected.

With a recent Linux distro, you likely boot up graphics with simpledrm, 
which uses fb_defio as part of its console emulation. To test, boot the 
kernel with the 'nomodeset' parameter and write to /dev/fb0.

Best regards
Thomas

>
> This is based on Andrew's tree [0] in the mm-unstable branch - I was
> thinking it'd be best to go through the mm tree (with fb_defio maintainer
> approval, of course!) as it relies upon the mm changes to work correctly.
>
> [0]: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/
>
> RFC v2:
> * Updated Jaya Kumar's email on cc - the MAINTAINERS section is apparently incorrect.
> * Corrected rmap_walk_file() comment to refer to folios as per Matthew.
> * Reference folio->mapping rather than folio_mapping(folio) in rmap_walk_file()
>    as per Matthew.
> * Reference folio->index rather than folio_pgoff(folio) in rmap_walk_file() as
>    per Matthew.
> * Renamed rmap_wrprotect_file_page() to mapping_wrprotect_page() as per Matthew.
> * Fixed kerneldoc and moved to implementation as per Matthew.
> * Updated mapping_wrprotect_page() to take a struct page pointer as per David.
> * Removed folio lock when invoking mapping_wrprotect_page() in
>    fb_deferred_io_work() as per Matthew.
> * Removed compound_nr() in fb_deferred_io_work() as per Matthew.
>
> RFC v1:
> https://lore.kernel.org/all/1e452b5b65f15a9a5d0c2ed3f5f812fdd1367603.1736352361.git.lorenzo.stoakes@oracle.com/
>
> Lorenzo Stoakes (3):
>    mm: refactor rmap_walk_file() to separate out traversal logic
>    mm: provide mapping_wrprotect_page() function
>    fb_defio: do not use deprecated page->mapping, index fields
>
>   drivers/video/fbdev/core/fb_defio.c |  38 ++-----
>   include/linux/fb.h                  |   1 +
>   include/linux/rmap.h                |   3 +
>   mm/rmap.c                           | 152 +++++++++++++++++++++++-----
>   4 files changed, 141 insertions(+), 53 deletions(-)
>
> --
> 2.48.0

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)



  parent reply	other threads:[~2025-02-03 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 23:15 Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 1/3] mm: refactor rmap_walk_file() to separate out traversal logic Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 2/3] mm: provide mapping_wrprotect_page() function Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 3/3] fb_defio: do not use deprecated page->mapping, index fields Lorenzo Stoakes
2025-02-01 17:01   ` Lorenzo Stoakes
2025-02-01 17:03     ` Lorenzo Stoakes
2025-01-27 18:45 ` [RFC PATCH v2 0/3] expose mapping wrprotect, fix fb_defio use Lorenzo Stoakes
2025-01-31 17:03 ` Lorenzo Stoakes
2025-01-31 18:01   ` Kajtár Zsolt
2025-02-03 10:24 ` Thomas Zimmermann [this message]
2025-02-03 10:54   ` Lorenzo Stoakes

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=b284f594-2b28-4c1b-b00e-2fe7e9036b2f@suse.de \
    --to=tzimmermann@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jayakumar.lkml@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=simona@ffwll.ch \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox