From: Jan Kiszka <jan.kiszka@siemens.com>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] Lacking xsave support in Xenomai
Date: Fri, 25 Jan 2013 15:06:40 +0100 [thread overview]
Message-ID: <51029170.7070104@siemens.com> (raw)
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?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2013-01-25 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 14:06 Jan Kiszka [this message]
2013-01-25 18:44 ` [Xenomai] Lacking xsave support in Xenomai Gilles Chanteperdrix
2013-01-25 19:01 ` Jan Kiszka
2013-01-25 19:43 ` Gilles Chanteperdrix
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=51029170.7070104@siemens.com \
--to=jan.kiszka@siemens.com \
--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.