linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Tavis Ormandy <taviso@google.com>, Borislav Petkov <bp@alien8.de>,
	Ingo Molnar <mingo@kernel.org>
Cc: Rik van Riel <riel@redhat.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] x86/fpu: minor cleanups
Date: Mon, 2 Mar 2015 19:32:10 +0100	[thread overview]
Message-ID: <20150302183210.GA23085@redhat.com> (raw)
In-Reply-To: <20150302174818.GA16886@redhat.com>

add lkml/cc's.

On 03/02, Oleg Nesterov wrote:
>
> Btw, why xstateregs_get/set() looks so confusing? The comment says
> "Copy the 48bytes defined by the software first into the xstate" but the
> code uses ->fxsave. Yes, this is the same memory, but still. I'll send
> the cosmetic cleanup.
>
> Or fx_finit()... Again, memset(fx, 0, xstate_size) is correct but only
> because of the current layout. I think this needs a cleanup too.

Of course this is purely cosmetic, but still...

Oleg.


       reply	other threads:[~2015-03-02 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJ_zFkJkHpU4Y8wrrZjO0VnhzUVqJfyrLmNfRsBRT29bgbDSHg@mail.gmail.com>
     [not found] ` <20150301184650.GA12758@redhat.com>
     [not found]   ` <20150301185943.GA14318@redhat.com>
     [not found]     ` <20150302174818.GA16886@redhat.com>
2015-03-02 18:32       ` Oleg Nesterov [this message]
2015-03-02 18:32         ` [PATCH 1/2] x86/regsets: change xstateregs_get/set to use ->xsave.i387 rather than ->fxsave Oleg Nesterov
2015-03-03 19:23           ` Rik van Riel
2015-03-04 10:30           ` Borislav Petkov
2015-03-10 10:08           ` [tip:x86/fpu] x86/fpu: Change xstateregs_get()/set() to use -> xsave.i387 " tip-bot for Oleg Nesterov
2015-03-02 18:32         ` [PATCH 2/2] x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths Oleg Nesterov
2015-03-03 22:01           ` Rik van Riel
2015-03-04 11:38           ` Borislav Petkov
2015-03-10 10:08           ` [tip:x86/fpu] x86/fpu: Factor out memset(xstate, 0) in fpu_finit( ) paths tip-bot for Oleg Nesterov
2015-03-09 18:08 [GIT PULL] x86/fpu cleanups Borislav Petkov
2015-03-10  6:06 ` [PATCH 1/2] x86/fpu: Change xstateregs_get()/set() to use ->xsave.i387 rather than ->fxsave Borislav Petkov
2015-03-10  6:06   ` [PATCH 2/2] x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths Borislav Petkov

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=20150302183210.GA23085@redhat.com \
    --to=oleg@redhat.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=riel@redhat.com \
    --cc=taviso@google.com \
    --cc=torvalds@linux-foundation.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 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).