From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: fweisbec@gmail.com, Anton Blanchard <anton@au1.ibm.com>,
linux-kernel@vger.kernel.org, paulus@samba.org,
paulmck@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v3 0/5] powerpc: Support context tracking for Power pSeries
Date: Mon, 13 May 2013 15:51:46 +1000 [thread overview]
Message-ID: <1368424306.19924.20.camel@pasglop> (raw)
In-Reply-To: <1368422493-9831-1-git-send-email-zhong@linux.vnet.ibm.com>
On Mon, 2013-05-13 at 13:21 +0800, Li Zhong wrote:
> These patches try to support context tracking for Power arch, beginning with
> 64-bit pSeries. The codes are ported from that of the x86_64, and in each
> patch, I listed the corresponding patch for x86.
So that's yet another pile of bloat on all syscall entry/exit and
exception entry/exit. What is it used for ? (I haven't followed on
x86_64 side).
Cheers,
Ben.
> v3:
>
> This version is mainly a rebasing, against 3.10-rc1, also as the common code
> to handle the exception are pulled into 3.10, so there is no dependency on
> tip tree. So patch #2 and #6 in previous version_2 is merged together.
>
> Li Zhong (5):
> powerpc: Syscall hooks for context tracking subsystem
> powerpc: Exception hooks for context tracking subsystem
> powerpc: Exit user context on notify resume
> powerpc: Use the new schedule_user API on userspace preemption
> powerpc: select HAVE_CONTEXT_TRACKING for pSeries
>
> arch/powerpc/include/asm/context_tracking.h | 10 +++
> arch/powerpc/include/asm/thread_info.h | 7 ++-
> arch/powerpc/kernel/entry_64.S | 3 +-
> arch/powerpc/kernel/ptrace.c | 5 ++
> arch/powerpc/kernel/signal.c | 5 ++
> arch/powerpc/kernel/traps.c | 91 ++++++++++++++++++++-------
> arch/powerpc/mm/fault.c | 16 ++++-
> arch/powerpc/mm/hash_utils_64.c | 38 ++++++++---
> arch/powerpc/platforms/pseries/Kconfig | 1 +
> 9 files changed, 140 insertions(+), 36 deletions(-)
> create mode 100644 arch/powerpc/include/asm/context_tracking.h
>
next prev parent reply other threads:[~2013-05-13 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 5:21 [RFC PATCH v3 0/5] powerpc: Support context tracking for Power pSeries Li Zhong
2013-05-13 5:21 ` [RFC PATCH v3 1/5] powerpc: Syscall hooks for context tracking subsystem Li Zhong
2013-05-13 5:21 ` [RFC PATCH v3 2/5] powerpc: Exception " Li Zhong
2013-05-13 5:57 ` Benjamin Herrenschmidt
2013-05-13 8:44 ` Li Zhong
2013-05-13 9:06 ` Benjamin Herrenschmidt
2013-05-13 9:46 ` Li Zhong
2013-05-13 10:01 ` Benjamin Herrenschmidt
2013-05-13 5:21 ` [RFC PATCH v3 3/5] powerpc: Exit user context on notify resume Li Zhong
2013-05-13 5:21 ` [RFC PATCH v3 4/5] powerpc: Use the new schedule_user API on userspace preemption Li Zhong
2013-05-13 5:21 ` [RFC PATCH v3 5/5] powerpc: select HAVE_CONTEXT_TRACKING for pSeries Li Zhong
2013-05-13 5:51 ` Benjamin Herrenschmidt [this message]
2013-05-13 8:03 ` [RFC PATCH v3 0/5] powerpc: Support context tracking for Power pSeries Li Zhong
2013-05-13 8:59 ` Benjamin Herrenschmidt
2013-05-13 9:22 ` Li Zhong
2013-05-29 21:32 ` Frederic Weisbecker
2013-05-29 21:29 ` Frederic Weisbecker
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=1368424306.19924.20.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anton@au1.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=zhong@linux.vnet.ibm.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).