public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Brian Gerst <brgerst@gmail.com>,
	Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/4] Virtually mapped stack prep for -mm
Date: Thu, 14 Jul 2016 12:14:09 -0700	[thread overview]
Message-ID: <cover.1468523549.git.luto@kernel.org> (raw)

Hi akpm-

We're delaying virtually mapped stacks to 4.9.  These four patches
are simple and seem like -mm material.  Could you apply them for
4.8 so we can get the easy core bits in place?

Thanks,
Andy

Andy Lutomirski (4):
  mm: Track NR_KERNEL_STACK in KiB instead of number of stacks
  mm: Fix memcg stack accounting for sub-page stacks
  kdb: Use task_cpu() instead of task_thread_info()->cpu
  printk: When dumping regs, show the stack, not thread_info

 drivers/base/node.c        |  3 +--
 fs/proc/meminfo.c          |  2 +-
 include/linux/kdb.h        |  2 +-
 include/linux/memcontrol.h |  2 +-
 include/linux/mmzone.h     |  2 +-
 kernel/fork.c              | 20 +++++++++-----------
 kernel/printk/printk.c     |  5 ++---
 mm/memcontrol.c            |  2 +-
 mm/page_alloc.c            |  3 +--
 9 files changed, 18 insertions(+), 23 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-07-14 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 19:14 Andy Lutomirski [this message]
2016-07-14 19:14 ` [PATCH 1/4] mm: Track NR_KERNEL_STACK in KiB instead of number of stacks Andy Lutomirski
2016-07-14 19:22   ` Johannes Weiner
2016-07-14 19:14 ` [PATCH 2/4] mm: Fix memcg stack accounting for sub-page stacks Andy Lutomirski
2016-07-14 19:24   ` Johannes Weiner
2016-07-14 20:53   ` Andrew Morton
2016-07-14 19:14 ` [PATCH 3/4] kdb: Use task_cpu() instead of task_thread_info()->cpu Andy Lutomirski
2016-07-14 19:14 ` [PATCH 4/4] printk: When dumping regs, show the stack, not thread_info Andy Lutomirski

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=cover.1468523549.git.luto@kernel.org \
    --to=luto@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brgerst@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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