From: wolfgang.betz@st.com (Wolfgang BETZ)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1 V2] Add Thread Support for the Context ID Register of ARM v6 & v7 Architectures
Date: Thu, 14 Jul 2011 11:33:09 +0200 [thread overview]
Message-ID: <cover.1310544641.git.wolfgang.betz@st.com> (raw)
From: Wolfgang Betz <wolfgang.betz@st.com>
The Context ID Register, CONTEXTIDR, identifies the current:
- Process Identifier (PROCID) &
- Address Space Identifier (ASID).
The value of the whole of this register is called the Context ID and is
used by:
- the ARM debug logic, for Linked and Unlinked Context ID matching
(e.g. for breakpoint debug and watchpoint debug events).
- the trace logic, to identify the current process.
The CONTEXTIDR is a 32-bit read/write register whose format is:
- PROCID, bits [31:8]
Process Identifier. This field should be programmed with a unique
value that identifies the current process and is used by the trace logic and
the debug logic to identify the process that is running currently.
- ASID, bits [7:0]
Address Space Identifier. This field must be programmed with the
value of the current ASID and is used by many memory management functions.
This change-set aims at:
- implementing thread tracing support based on the armv6 & v7 CONTEXTIDR
register while leaving the Linux kernel ASID functionality (semantically)
unchanged.
- focusing on compatibility with tracing tools such as Lauterbach's
TRACE32 tool.
- the avoidance of platform specific calls in generic code.
- simplicity, readability, and good performances.
- being general: i.e. the change-set applies to all armv7/v6 platforms &
is in general compilable for all (other) platforms.
The patch has been jointly developed by
Lauterbach GmbH (http://www.lauterbach.com) and
STMicroelectronics Srl (http://www.st.com/).
Main contributors are:
- Khaled Jmal <khaled.jmal@lauterbach.com>
- Rudi Dienstbeck <Rudolf.Dienstbeck@Lauterbach.com>
- Wolfgang Betz <wolfgang.betz@st.com>
Wolfgang Betz (1):
Add Thread Support for the Context ID Register of ARM v6 & v7
Architectures
arch/arm/Kconfig.debug | 13 +++++++
arch/arm/include/asm/mmu_context.h | 63 +++++++++++++++++++++++++++++++----
arch/arm/kernel/smp.c | 2 +-
arch/arm/mm/context.c | 42 +++++++++++++++++++++++-
arch/arm/mm/proc-v6.S | 1 -
arch/arm/mm/proc-v7.S | 1 -
6 files changed, 109 insertions(+), 13 deletions(-)
--
1.7.4.4
next reply other threads:[~2011-07-14 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 9:33 Wolfgang BETZ [this message]
2011-07-14 9:33 ` [PATCH 1/1 V2] Add Thread Support for the Context ID Register of ARM v6 & v7 Architectures Wolfgang BETZ
2011-07-14 10:02 ` Will Deacon
[not found] ` <4E1ECDD4.1020800@st.com>
2011-07-14 11:36 ` Will Deacon
[not found] ` <4E241E60.7040403@st.com>
2011-07-18 12:57 ` Will Deacon
[not found] ` <4E24446C.4060204@st.com>
2011-07-18 17:09 ` Will Deacon
[not found] ` <4E251465.4070001@st.com>
2011-07-19 16:43 ` Will Deacon
2011-07-19 10:23 ` Russell King - ARM Linux
[not found] ` <4E2D418D.4000800@st.com>
2011-07-25 10:33 ` Russell King - ARM Linux
2011-07-25 21:27 ` Will Deacon
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.1310544641.git.wolfgang.betz@st.com \
--to=wolfgang.betz@st.com \
--cc=linux-arm-kernel@lists.infradead.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).