From: Richard Weinberger <richard@nod.at>
To: Eli Cooper <elicooper@gmx.com>,
user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [PATCH 1/3] um: extend _fpstate to _xstate
Date: Wed, 9 Mar 2016 21:44:10 +0100 [thread overview]
Message-ID: <56E08B1A.4080809@nod.at> (raw)
In-Reply-To: <1457274987-20078-2-git-send-email-elicooper@gmx.com>
Hi!
Am 06.03.2016 um 15:36 schrieb Eli Cooper:
> Extends _fpstate to _xstate, in order to hold AVX/YMM registers.
> Due to increased frame size, compilers might emit some warnings.
Hmm, this needs rework. Having everything on the stack is not good.
Can you also create a selftest such that this bug cannot happen again?
Thanks,
//richard
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2016-03-09 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 14:36 [uml-devel] [PATCH 0/3] um: Add support for extended processor state Eli Cooper
2016-03-06 14:36 ` [uml-devel] [PATCH 1/3] um: extend _fpstate to _xstate Eli Cooper
2016-03-09 20:44 ` Richard Weinberger [this message]
2016-03-12 7:08 ` Eli Cooper
2016-03-13 7:58 ` Richard Weinberger
2016-03-13 13:56 ` Eli Cooper
2016-03-14 7:58 ` stian
2016-03-06 14:36 ` [uml-devel] [PATCH 2/3] um: add extended processor state save/restore support Eli Cooper
2016-03-06 14:36 ` [uml-devel] [PATCH 3/3] um: fix ptrace PTRACE_GETFPREGS and PTRACE_SETFPREG support Eli Cooper
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=56E08B1A.4080809@nod.at \
--to=richard@nod.at \
--cc=elicooper@gmx.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).