public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Richard Weinberger <richard@nod.at>
Cc: Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>,
	linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH] xtensa: Fix execdomain removal
Date: Sat, 11 Apr 2015 19:19:51 -0700	[thread overview]
Message-ID: <1428805191-27089-1-git-send-email-linux@roeck-us.net> (raw)

The removal of exexdomain changes pointer offsets into the thread_info
structure.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
Applies on top of Richard's execdomain removal patches.
Tested with xtensa qemu session.

 arch/xtensa/include/asm/thread_info.h | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/arch/xtensa/include/asm/thread_info.h b/arch/xtensa/include/asm/thread_info.h
index d120278073b5..b3680a4738cd 100644
--- a/arch/xtensa/include/asm/thread_info.h
+++ b/arch/xtensa/include/asm/thread_info.h
@@ -64,12 +64,11 @@ struct thread_info {
 
 /* offsets into the thread_info struct for assembly code access */
 #define TI_TASK		 0x00000000
-#define TI_EXEC_DOMAIN	 0x00000004
-#define TI_FLAGS	 0x00000008
-#define TI_STATUS	 0x0000000C
-#define TI_CPU		 0x00000010
-#define TI_PRE_COUNT	 0x00000014
-#define TI_ADDR_LIMIT	 0x00000018
+#define TI_FLAGS	 0x00000004
+#define TI_STATUS	 0x00000008
+#define TI_CPU		 0x0000000C
+#define TI_PRE_COUNT	 0x00000010
+#define TI_ADDR_LIMIT	 0x00000014
 
 #endif
 
-- 
2.1.0

             reply	other threads:[~2015-04-12  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12  2:19 Guenter Roeck [this message]
2015-04-12 14:43 ` [PATCH] xtensa: Fix execdomain removal Jeff Epler
2015-04-12 14:43   ` Jeff Epler
2015-04-12 15:00   ` Guenter Roeck
2015-04-12 15:00     ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2015-04-12 14:58 Richard Weinberger

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=1428805191-27089-1-git-send-email-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=richard@nod.at \
    /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