From: Stephane Eranian <eranian@hpl.hp.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] i386 TIF flags for debug regs and io bitmap in ctxsw
Date: Tue, 4 Jul 2006 14:51:17 -0700 [thread overview]
Message-ID: <20060704215117.GC7078@frankl.hpl.hp.com> (raw)
In-Reply-To: <200607041719_MC3-1-C420-EC5A@compuserve.com>
Chuck,
On Tue, Jul 04, 2006 at 05:19:02PM -0400, Chuck Ebbert wrote:
>
> > + if (test_tsk_thread_flag(next_p, TIF_IO_BITMAP) == 0) {
>
> preferred:
>
> if (!test_tsk_thread_flag(next_p, TIF_IO_BITMAP)) {
>
Ok, I will fix that.
> And this should be added to the patch:
>
> --- 2.6.17-nb.orig/arch/i386/kernel/process.c
> +++ 2.6.17-nb/arch/i386/kernel/process.c
> @@ -360,13 +360,12 @@ EXPORT_SYMBOL(kernel_thread);
> */
> void exit_thread(void)
> {
> - struct task_struct *tsk = current;
> - struct thread_struct *t = &tsk->thread;
> -
> /* The process may have allocated an io port bitmap... nuke it. */
> - if (unlikely(NULL != t->io_bitmap_ptr)) {
> + if (unlikely(test_thread_flag(TIF_IO_BITMAP))) {
> int cpu = get_cpu();
> struct tss_struct *tss = &per_cpu(init_tss, cpu);
> + struct task_struct *tsk = current;
> + struct thread_struct *t = &tsk->thread;
>
> kfree(t->io_bitmap_ptr);
> t->io_bitmap_ptr = NULL;
Yes, I missed that test. Thanks for catching it.
--
-Stephane
next prev parent reply other threads:[~2006-07-04 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 21:19 Chuck Ebbert
2006-07-04 21:47 ` Andi Kleen
2006-07-04 21:45 ` Stephane Eranian
2006-07-04 21:51 ` Stephane Eranian [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-05 11:44 Chuck Ebbert
2006-07-04 7:29 Stephane Eranian
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=20060704215117.GC7078@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
Powered by JetHome