From: Chuck Ebbert <76306.1226@compuserve.com>
To: Linus Torvalds <torvalds@osdl.org>,
Stephane Eranian <eranian@hpl.hp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps
Date: Sun, 9 Jul 2006 19:34:04 -0400 [thread overview]
Message-ID: <200607091936_MC3-1-C489-B862@compuserve.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607081425430.3869@g5.osdl.org>
On Sat, 8 Jul 2006 14:26:53 -0700, Linus Torvalds wrote:
>
> On Fri, 7 Jul 2006, Chuck Ebbert wrote:
> >
> > From: Stephane Eranian <eranian@hpl.hp.com>
> >
> > Use thread info flags to track use of debug registers and IO bitmaps.
> >
> > - add TIF_DEBUG to track when debug registers are active
> > - add TIF_IO_BITMAP to track when I/O bitmap is used
> > - modify __switch_to() to use the new TIF flags
>
> Can you explain what the advantages of this are?
Stephane's perfmon2 patch adds yet another special-case to the
switch_to() code, so Andi suggested this change. It will allow
the perfmon2 patch to have no performance impact on normal
task-switching, since it will just use another flag.
After I saw a ~7% gain in task-switch performance, I like it now
even without perfmon2 in there.
> I don't see it. It's just creating new state to describe state that we
> already had, and as far as I can tell, it's just a way to potentially have
> more new bugs thanks to the new state getting out of sync with the old
> one?
Well yeah, there is that. But Andi and I both reviewed it and he's
already put the x86_64 version into his tree. Testing in -mm should
show whether there are any problems.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-07-09 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 23:34 Chuck Ebbert [this message]
2006-07-09 23:48 ` Linus Torvalds
2006-07-10 0:07 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 15:53 Chuck Ebbert
2006-07-07 16:22 ` Andi Kleen
2006-07-08 21:26 ` Linus Torvalds
2006-07-09 23:59 ` Andi Kleen
2006-07-10 9:28 ` 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=200607091936_MC3-1-C489-B862@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=eranian@hpl.hp.com \
--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
Powered by JetHome