public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/2] s390: Remove uses of page->index
Date: Thu, 19 Dec 2024 16:22:48 +0000	[thread overview]
Message-ID: <20241219162252.1025317-1-willy@infradead.org> (raw)

These two patches compile ... I can promise nothing more than that.

David suggested to me that the gmap code really should be using ptdesc,
and I think I agree with him.  The vsie code looks quite different
and probably shouldn't be using a ptdesc, but we can use page->private
instead of page->index.  It's not yet clear to me if we'll ever manage
to get rid of page->private.

Matthew Wilcox (Oracle) (2):
  s390: Convert gmap code to use ptdesc
  s390: Convert vsie code to use page->private

 arch/s390/kvm/vsie.c |   6 +-
 arch/s390/mm/gmap.c  | 181 +++++++++++++++++++++----------------------
 2 files changed, 92 insertions(+), 95 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-12-19 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 16:22 Matthew Wilcox (Oracle) [this message]
2024-12-19 16:22 ` [PATCH 1/2] s390: Convert gmap code to use ptdesc Matthew Wilcox (Oracle)
2024-12-19 21:23   ` Matthew Wilcox
2024-12-20  9:22     ` David Hildenbrand
2024-12-19 16:22 ` [PATCH 2/2] s390: Convert vsie code to use page->private Matthew Wilcox (Oracle)
2024-12-20  9:55   ` David Hildenbrand
2024-12-20 11:40     ` Claudio Imbrenda
2024-12-19 16:33 ` [PATCH 0/2] s390: Remove uses of page->index David Hildenbrand
2024-12-19 16:52   ` Matthew Wilcox
2024-12-19 16:56     ` David Hildenbrand
2025-01-03 14:53 ` Claudio Imbrenda
2025-01-07 10:23   ` David Hildenbrand

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=20241219162252.1025317-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox