From: Andi Kleen <ak@suse.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: avoid redundant preempt_disable in __unlazy_fpu
Date: Mon, 30 Apr 2007 13:23:05 +0200 [thread overview]
Message-ID: <200704301323.05459.ak@suse.de> (raw)
In-Reply-To: <4635D01A.40806@web.de>
On Monday 30 April 2007 13:16:42 Jan Kiszka wrote:
> There are two callers of __unlazy_fpu, unlazy_fpu and __switch_to, and
> none of them appear to require additional preempt_disable/enable here.
> Let's open-code save_init_fpu in __unlazy_fpu to save a few ops.
Both patches added thanks
-Andi
prev parent reply other threads:[~2007-04-30 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 11:16 [PATCH] i386: avoid redundant preempt_disable in __unlazy_fpu Jan Kiszka
2007-04-30 11:23 ` Andi Kleen [this message]
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=200704301323.05459.ak@suse.de \
--to=ak@suse.de \
--cc=jan.kiszka@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.