The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	jackit-devel <jackit-devel@lists.sourceforge.net>
Subject: Re: 2.4.x vs 2.6.x: denormal handling and audio performance
Date: Mon, 09 Aug 2004 21:09:10 -0400	[thread overview]
Message-ID: <1092100150.22613.16.camel@mindpipe> (raw)
In-Reply-To: <1092099606.22613.12.camel@mindpipe>

On Mon, 2004-08-09 at 21:00, Lee Revell wrote:
> On Mon, 2004-08-09 at 15:19, Fernando Pablo Lopez-Lezcano wrote:
> > Hi all, I've been trying to track weird behavior I'm experiencing when
> > trying to use 2.6.x for "pro audio" applications
>
> In case anyone thinks this is an application bug, here are some links
> pertaining to the P4 denormals-are-zero issue


If the denormals-are-zero bit is the issue then I believe this patch
should fix the problem.

Lee

--- arch/i386/kernel/i387_orig.c	2004-08-09 21:06:00.000000000 -0400
+++ arch/i386/kernel/i387.c	2004-08-09 21:06:05.000000000 -0400
@@ -34,7 +34,7 @@
 		memset(&current->thread.i387.fxsave, 0, sizeof(struct i387_fxsave_struct));
 		asm volatile("fxsave %0" : : "m" (current->thread.i387.fxsave)); 
 		mask = current->thread.i387.fxsave.mxcsr_mask;
-		if (mask == 0) mask = 0x0000ffbf;
+		if (mask == 0) mask = 0x0000ffff;
 	} 
 	mxcsr_feature_mask &= mask;
 	stts();




  reply	other threads:[~2004-08-10  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 19:19 2.4.x vs 2.6.x: denormal handling and audio performance Fernando Pablo Lopez-Lezcano
2004-08-10  1:00 ` Lee Revell
2004-08-10  1:09   ` Lee Revell [this message]
2004-08-10  2:35   ` Fernando Pablo Lopez-Lezcano
2004-08-10  5:28     ` Lee Revell

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=1092100150.22613.16.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=jackit-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    /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