All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH] Fix ppc fpu support
Date: Sat, 07 Jan 2006 20:00:07 +0200	[thread overview]
Message-ID: <43C001A7.1010408@domain.hid> (raw)
In-Reply-To: <43BFFD58.80303@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

Philippe Gerum kirjoitti:
> Heikki Lindholm wrote:
> 
>> Philippe Gerum kirjoitti:
>>
>>> Heikki Lindholm wrote:
>>>
>>>> Xenomai might preempt linux when linux has cleared a tasks MSR_FP, 
>>>> but not yet set last_task_used_math to NULL. As a result the tasks 
>>>> MSR_FP will get set, although it should be cleared. If the task 
>>>> happens to hit one of the codepaths that save FPU state if MSR_FP is 
>>>> set, the wrong FPU state might be saved to the task. The attached 
>>>> patch should fix this. I couldn't try it on most recent Xenomai 
>>>> trunk, because latency wouldn't build anymore. However, I see no 
>>>> reason it shouldn't work. All thee having trouble with X and 
>>>> Xenomai, give this a shot.
>>>>
>>>
>>> Merged in r383, thanks.
>>
>>
>>
>> On a related note, how do you think patches to Linux kernel that don't 
>> fit into I-pipe should be handled? Put into patches directory 
>> separately? There are now at least two instances for 2.6.14/ppc: the 
>> fpu bug that I already posted on this thread and the ppc64 UP building 
>> bug that effectively makes impossible to build I-pipe 2.6.14 for UP on 
>> ppc64.
>>
> 
> I'm going to put those patches on GNA, so that people can access to them 
> easily. I'm going to add a fix for x86 too, which is needed at least on 
> one of my boxen since 2.6.13 to make the PCI setup correct again.
> 
> Is this patch still the right one to fix the UP build on ppc64?
> http://patchwork.ozlabs.org/linuxppc64/patchcontent?id=3178

Yep. That makes it build. But catenate it with the following and it'll 
boot, too ;)

-- Heikki Lindholm

[-- Attachment #2: 2.6.14-ppc64-UP-bootcpu.patch --]
[-- Type: text/plain, Size: 559 bytes --]

diff -Nru linux-2.6.14/arch/ppc64/kernel/prom.c linux-2.6.14-dev/arch/ppc64/kernel/prom.c
--- linux-2.6.14/arch/ppc64/kernel/prom.c	2005-10-28 03:02:08.000000000 +0300
+++ linux-2.6.14-dev/arch/ppc64/kernel/prom.c	2005-11-06 14:14:07.000000000 +0200
@@ -1019,6 +1019,7 @@
 		 */
 		boot_cpuid_phys = initial_boot_params->boot_cpuid_phys;
 		boot_cpuid = 0;
+		set_hard_smp_processor_id(boot_cpuid, boot_cpuid_phys);
 	} else {
 		/* Check if it's the boot-cpu, set it's hw index in paca now */
 		if (get_flat_dt_prop(node, "linux,boot-cpu", NULL) != NULL) {

  reply	other threads:[~2006-01-07 18:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 18:42 [Xenomai-core] [PATCH] Fix ppc fpu support Heikki Lindholm
2006-01-06 18:58 ` Jan Kiszka
2006-01-06 19:14   ` Heikki Lindholm
2006-01-06 19:25     ` Jan Kiszka
2006-01-06 19:42       ` Jan Kiszka
2006-01-06 21:38       ` Heikki Lindholm
2006-01-07 10:38   ` Heikki Lindholm
2006-01-07 10:34 ` Heikki Lindholm
2006-01-07 13:33 ` Philippe Gerum
2006-01-07 17:24   ` Heikki Lindholm
2006-01-07 17:41     ` Philippe Gerum
2006-01-07 18:00       ` Heikki Lindholm [this message]
2006-01-07 18:35         ` Philippe Gerum

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=43C001A7.1010408@domain.hid \
    --to=holindho@domain.hid \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.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.