From: "H. Peter Anvin" <hpa@zytor.com>
To: Leonid Shatz <leonid.shatz@ravellosystems.com>,
"'Yu-cheng Yu'" <yu-cheng.yu@intel.com>
Cc: "'Ingo Molnar'" <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
"'Andy Lutomirski'" <luto@amacapital.net>,
"'Borislav Petkov'" <bp@alien8.de>,
"'Dave Hansen'" <dave.hansen@linux.intel.com>,
"'Fenghua Yu'" <fenghua.yu@intel.com>,
"'Linus Torvalds'" <torvalds@linux-foundation.org>,
"'Oleg Nesterov'" <oleg@redhat.com>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Quentin Casasnovas'" <quentin.casasnovas@oracle.com>,
"'Ravi V. Shankar'" <ravi.v.shankar@intel.com>,
"'Sai Praneeth Prakhya'" <sai.praneeth.prakhya@intel.com>,
"'Thomas Gleixner'" <tglx@linutronix.de>,
liran.alon@ravellosystems.com, mendel.aizner@ravellosystems.com,
"'Elazar Leibovich'" <elazar.leibovich@ravellosystems.com>,
"'Eyal Moscovici'" <eyal.moscovici@ravellosystems.com>,
gil.hoffer@ravellosystems.com
Subject: Re: Linux patch disabling AVX when eagerfpu is turned off - possibly not required
Date: Thu, 21 Jan 2016 13:22:51 -0800 [thread overview]
Message-ID: <56A14C2B.30802@zytor.com> (raw)
In-Reply-To: <00f901d15491$71ae6260$550b2720$@ravellosystems.com>
On 01/21/16 13:19, Leonid Shatz wrote:
>
> Thank you all for your feedback and clarifications. That's was my assumption
> that SDM was somewhat misleading, but I was not %100 sure about it. It could
> be nice, though to see future releases of SDM taking this issue in account.
>
It will.
-hpa
prev parent reply other threads:[~2016-01-21 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 10:33 Linux patch disabling AVX when eagerfpu is turned off - possibly not required Leonid Shatz
2016-01-21 20:08 ` Dave Hansen
2016-01-21 20:11 ` H. Peter Anvin
2016-01-21 21:03 ` Andy Lutomirski
2016-01-21 21:03 ` Yu-cheng Yu
2016-01-21 21:08 ` H. Peter Anvin
2016-01-21 21:12 ` Yu-cheng Yu
2016-01-21 21:19 ` Leonid Shatz
2016-01-21 21:22 ` H. Peter Anvin [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=56A14C2B.30802@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elazar.leibovich@ravellosystems.com \
--cc=eyal.moscovici@ravellosystems.com \
--cc=fenghua.yu@intel.com \
--cc=gil.hoffer@ravellosystems.com \
--cc=leonid.shatz@ravellosystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@ravellosystems.com \
--cc=luto@amacapital.net \
--cc=mendel.aizner@ravellosystems.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=quentin.casasnovas@oracle.com \
--cc=ravi.v.shankar@intel.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yu-cheng.yu@intel.com \
/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.