From: Ingo Molnar <mingo@kernel.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-metag@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/features/vm: Meta2 is capable of THP
Date: Fri, 31 Jul 2015 10:47:43 +0200 [thread overview]
Message-ID: <20150731084743.GA5576@gmail.com> (raw)
In-Reply-To: <1438266123-30978-1-git-send-email-james.hogan@imgtec.com>
* James Hogan <james.hogan@imgtec.com> wrote:
> Change metag Transparent Huge Pages (THP) support from .. to TODO. Meta2
> has variable sized pages, between 4KB and 4MB, specified at the 1st
> level page table level, and already supports hugetlbfs, so supporting
> THP is theoretically possible too.
>
> Signed-off-by: James Hogan <james.hogan@imgtec.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-metag@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
> ---
> I'm applying this to the Meta tree for v4.3.
> ---
> Documentation/features/vm/THP/arch-support.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/features/vm/THP/arch-support.txt b/Documentation/features/vm/THP/arch-support.txt
> index 972d02c2a74c..df384e3e845f 100644
> --- a/Documentation/features/vm/THP/arch-support.txt
> +++ b/Documentation/features/vm/THP/arch-support.txt
> @@ -20,7 +20,7 @@
> | ia64: | TODO |
> | m32r: | .. |
> | m68k: | .. |
> - | metag: | .. |
> + | metag: | TODO |
> | microblaze: | .. |
> | mips: | ok |
> | mn10300: | .. |
I missed that, thanks!
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-31 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 14:22 [PATCH] Documentation/features/vm: Meta2 is capable of THP James Hogan
2015-07-31 8:47 ` Ingo Molnar [this message]
[not found] ` <1438266123-30978-1-git-send-email-james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-08-02 22:15 ` Jonathan Corbet
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=20150731084743.GA5576@gmail.com \
--to=mingo@kernel.org \
--cc=corbet@lwn.net \
--cc=james.hogan@imgtec.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-metag@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.