From: Dave Hansen <dave.hansen@intel.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-next@vger.kernel.org, akpm@linux-foundation.org,
jack@suse.cz, kirill@shutemov.name, "Edgecombe,
Rick P" <rick.p.edgecombe@intel.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
borntraeger@de.ibm.com, david@redhat.com, aarcange@redhat.com,
linux-mm@kvack.org, frankja@linux.ibm.com, sfr@canb.auug.org.au,
jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, Will Deacon <will@kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
pasic@linux.ibm.com
Subject: Re: [PATCH v4 2/2] mm/gup/writeback: add callbacks for inaccessible pages
Date: Tue, 28 Apr 2020 17:42:20 -0700 [thread overview]
Message-ID: <26dd40c7-2a78-0e3f-ea52-cb92e4a574e6@intel.com> (raw)
In-Reply-To: <20200429013955.2b59bd99@p-imbrenda>
On 4/28/20 4:39 PM, Claudio Imbrenda wrote:
>> From where I'm standing, we have a hook in the core VM that can't
>> possibly work with some existing kernel functionality and has
>> virtually no chance of getting used on a second architecture.
> it seems to work at least for us, so it does possibly work :)
I think all you're saying is that it's been very lightly tested. :)
> regarding second architectures: when we started sending these patches
> around, there has been interest from some other architectures, so
> just because nobody else needs them now, it doesn't mean nobody will
> use them ever.
I was really interested in using them... until I looked at them.
Conceptually, they do something really useful, but the _implementation_
falls short of its promises.
I can't imagine ever using these hooks on x86.
next prev parent reply other threads:[~2020-04-29 0:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 13:25 [PATCH v4 0/2] add callbacks for inaccessible pages Claudio Imbrenda
2020-03-06 13:25 ` [PATCH v4 1/2] mm/gup: fixup for 9947ea2c1e608e32 "mm/gup: track FOLL_PIN pages" Claudio Imbrenda
2020-03-06 13:25 ` [PATCH v4 2/2] mm/gup/writeback: add callbacks for inaccessible pages Claudio Imbrenda
2020-04-13 20:22 ` Dave Hansen
2020-04-14 16:03 ` Claudio Imbrenda
2020-04-14 18:50 ` Dave Hansen
2020-04-15 9:26 ` Claudio Imbrenda
2020-04-15 11:39 ` Janosch Frank
2020-04-15 21:52 ` Dave Hansen
2020-04-15 22:17 ` Peter Zijlstra
2020-04-15 23:34 ` Dave Hansen
2020-04-16 12:15 ` Claudio Imbrenda
2020-04-16 14:20 ` Dave Hansen
2020-04-16 14:59 ` Claudio Imbrenda
2020-04-16 15:36 ` Dave Hansen
2020-04-16 16:34 ` Claudio Imbrenda
2020-04-16 19:02 ` Dave Hansen
2020-04-21 21:31 ` Dave Hansen
2020-04-28 19:43 ` Dave Hansen
2020-04-28 20:02 ` Christian Borntraeger
2020-04-28 23:39 ` Claudio Imbrenda
2020-04-29 0:42 ` Dave Hansen [this message]
2020-04-16 11:51 ` Claudio Imbrenda
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=26dd40c7-2a78-0e3f-ea52-cb92e4a574e6@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pasic@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).