From: Dave Hansen <dave.hansen@linux.intel.com>
To: riel@redhat.com, linux-kernel@vger.kernel.org
Cc: hpa@zytor.com, mingo@kernel.org, bp@alien8.de, luto@kernel.org,
oleg@redhat.comm
Subject: Re: [PATCH 1/2] x86/fpu: remove cpu argument to __cpu_invalidate_fpregs_state
Date: Fri, 14 Oct 2016 09:53:18 -0700 [thread overview]
Message-ID: <58010D7E.8050906@linux.intel.com> (raw)
In-Reply-To: <1476447331-21566-2-git-send-email-riel@redhat.com>
On 10/14/2016 05:15 AM, riel@redhat.com wrote:
> From: Rik van Riel <riel@redhat.com>
>
> The __{fpu,cpu}_invalidate_fpregs_state functions can only be used
> to invalidate a resource they control. Document that, and change
> the API a little bit to reflect that.
>
> Go back to open coding the fpu_fpregs_owner_ctx write in the CPU
> hotplug code, which should be the exception, and move __kernel_fpu_begin
> to this API.
>
> This patch has no functional changes to the current code.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
Looks totally sane to me.
Acked-by: Dave Hansen <dave.hansen@intel.com>
next prev parent reply other threads:[~2016-10-14 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 12:15 [PATCH 0/2] x86/fpu: two more FPU cleanups riel
2016-10-14 12:15 ` [PATCH 1/2] x86/fpu: remove cpu argument to __cpu_invalidate_fpregs_state riel
2016-10-14 16:53 ` Dave Hansen [this message]
2016-10-16 11:25 ` [tip:x86/fpu] x86/fpu: Remove 'cpu' argument from __cpu_invalidate_fpregs_state() tip-bot for Rik van Riel
2016-10-14 12:15 ` [PATCH 2/2] x86/fpu: split old & new fpu handling into separate functions riel
2016-10-14 17:14 ` Dave Hansen
2016-10-16 11:25 ` [tip:x86/fpu] x86/fpu: Split old_fpu & new_fpu " tip-bot for Rik van Riel
2017-01-24 12:13 ` you have a new message from... c92Y Izuchukwu Francis
2017-02-10 13:52 ` Izuchukwu Francis
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=58010D7E.8050906@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.comm \
--cc=riel@redhat.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.