From: Jarkko Sakkinen <jarkko@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Nathaniel McCallum <nathaniel@profian.com>,
Reinette Chatre <reinette.chatre@intel.com>,
linux-sgx@vger.kernel.org, jaharkes@cs.cmu.edu,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
codalist@telemann.coda.cs.cmu.edu, linux-unionfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC v2] mm: Add f_ops->populate()
Date: Mon, 7 Mar 2022 17:44:17 +0200 [thread overview]
Message-ID: <YiYoUfYuTDsld6L0@iki.fi> (raw)
In-Reply-To: <3c974f25-ece6-102b-01c3-bd7e6274f613@intel.com>
On Mon, Mar 07, 2022 at 07:29:22AM -0800, Dave Hansen wrote:
> On 3/7/22 03:27, Jarkko Sakkinen wrote:
> > But e.g. in __mm_populate() anything with (VM_IO | VM_PFNMAP) gets
> > filtered out and never reach that function.
> >
> > I don't know unorthodox that'd be but could we perhaps have a VM
> > flag for SGX?
>
> SGX only works on a subset of the chips from one vendor on one
> architecture. That doesn't seem worth burning a VM flag.
What do you think of Matthew's idea of using ra_state for prediction?
BR, Jarkko
next prev parent reply other threads:[~2022-03-07 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 3:26 [PATCH RFC v2] mm: Add f_ops->populate() Jarkko Sakkinen
2022-03-06 23:24 ` Andrew Morton
2022-03-06 23:41 ` Dave Hansen
2022-03-07 11:27 ` Jarkko Sakkinen
2022-03-07 15:29 ` Dave Hansen
2022-03-07 15:44 ` Jarkko Sakkinen [this message]
2022-03-07 14:37 ` Matthew Wilcox
2022-03-07 15:43 ` Jarkko Sakkinen
2022-03-07 13:00 ` Jarkko Sakkinen
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=YiYoUfYuTDsld6L0@iki.fi \
--to=jarkko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=codalist@telemann.coda.cs.cmu.edu \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=nathaniel@profian.com \
--cc=reinette.chatre@intel.com \
/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).