From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps
Date: Fri, 7 Jul 2006 18:22:12 +0200 [thread overview]
Message-ID: <200607071822.12495.ak@suse.de> (raw)
In-Reply-To: <200607071155_MC3-1-C45F-B7C2@compuserve.com>
On Friday 07 July 2006 17:53, Chuck Ebbert wrote:
>
> -static inline void
> -handle_io_bitmap(struct thread_struct *next, struct tss_struct *tss)
> +static inline void __switch_to_xtra(struct task_struct *next_p,
> + struct tss_struct *tss)
I would make that noinline
Rest looks good
-Andi
next prev parent reply other threads:[~2006-07-07 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:53 [patch] i386: use thread_info flags for debug regs and IO bitmaps Chuck Ebbert
2006-07-07 16:22 ` Andi Kleen [this message]
2006-07-08 21:26 ` Linus Torvalds
2006-07-09 23:59 ` Andi Kleen
2006-07-10 9:28 ` Stephane Eranian
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 23:34 Chuck Ebbert
2006-07-09 23:48 ` Linus Torvalds
2006-07-10 0:07 ` Andi Kleen
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=200607071822.12495.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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