From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5102D28D.2010908@xenomai.org>
Date: Fri, 25 Jan 2013 19:44:29 +0100
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
MIME-Version: 1.0
References: <51029170.7070104@siemens.com>
In-Reply-To: <51029170.7070104@siemens.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai] Lacking xsave support in Xenomai
List-Id: Discussions about the Xenomai project <xenomai.xenomai.org>
List-Unsubscribe: <http://www.xenomai.org/mailman/options/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=unsubscribe>
List-Archive: <http://www.xenomai.org/pipermail/xenomai>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-request@xenomai.org?subject=help>
List-Subscribe: <http://www.xenomai.org/mailman/listinfo/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>

On 01/25/2013 03:06 PM, Jan Kiszka wrote:

> Hi all,
> 
> yesterday I pushed a fix to my for-upstream queue that properly disables
> all xsave-dependent CPU features (AVX/AVX2 namely). However, this is no
> real solution for us as it blocks a lot of acceleration potential on
> current Intel CPUs.
> 
> Did anyone already look into this in more details? Is it just a matter
> of implementing the necessary context switching bits? Are there known

> pitfalls?


The known pitfalls of FPU support is that we never get it right the
first time. And debugging why it fails is hard.

-- 
                                                                Gilles.