From: Matthew Wilcox <willy@infradead.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/2] Convert some gmap functions to use folios
Date: Thu, 4 Apr 2024 14:38:55 +0100 [thread overview]
Message-ID: <Zg6tb7DMYGF57o2i@casper.infradead.org> (raw)
In-Reply-To: <20240326074127.6078-B-hca@linux.ibm.com>
On Tue, Mar 26, 2024 at 08:41:27AM +0100, Heiko Carstens wrote:
> On Fri, Mar 22, 2024 at 04:11:45PM +0000, Matthew Wilcox (Oracle) wrote:
> > struct page is going to lose its refcount (someday) and as part of
> > that page_ref_freeze() will go away. s390's ultravisor is one of
> > the few remaining places that uses it, so convert it over to folios.
> > From previous interactions, I understand that ultravisor doesn't support
> > large folios, so this simply declines to make large folios secure.
> > I think you'd be better off splitting the folio if it is large, but
> > that's something I'd rather leave to someone who can test it.
>
> Christian, Janosch, or Claudio, could you have a look at this please;
> and provide an ACK if this is ok with you?
Ping?
next prev parent reply other threads:[~2024-04-04 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 16:11 [PATCH 0/2] Convert some gmap functions to use folios Matthew Wilcox (Oracle)
2024-03-22 16:11 ` [PATCH 1/2] s390: Convert make_page_secure to use a folio Matthew Wilcox (Oracle)
2024-03-22 16:11 ` [PATCH 2/2] s390: Convert gmap_make_secure " Matthew Wilcox (Oracle)
2024-03-26 7:41 ` [PATCH 0/2] Convert some gmap functions to use folios Heiko Carstens
2024-04-04 13:38 ` Matthew Wilcox [this message]
2024-04-04 14:56 ` Claudio Imbrenda
2024-04-08 15:20 ` Alexander Gordeev
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=Zg6tb7DMYGF57o2i@casper.infradead.org \
--to=willy@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--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