From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org
Subject: m68k: remove thread_info struct from thread struct
Date: Mon, 5 Sep 2011 14:41:48 +1000 [thread overview]
Message-ID: <1315197709-21421-1-git-send-email-gerg@snapgear.com> (raw)
The following patch cleans up the duplicated thread_info struct within
each task. m68knommu only used the stack based one, but m68k mostly
used the threaad_struct one. All other architectures only used the
stack based one.
Unfortunately it adds a couple of instructions into the exception
processing paths. This could be reduced a little, since the act of
calculating the current pointer (%a2) actually gets us the thread_info
pointer. I have not taken advantage of this just yet, though this patch
does take advantage of what the GET_CURRENT() macro does internally.
I have tested this on ARAnyM and it seems to work just fine. Of course
tested on ColdFire as well, no problems there.
Thoughts on this one?
Regards
Greg
next reply other threads:[~2011-09-05 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 4:41 gerg [this message]
2011-09-05 4:41 ` [PATCH] m68k: remove thread_info struct from thread struct gerg
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=1315197709-21421-1-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox