From: Peter Zijlstra <peterz@infradead.org>
To: Keno Fischer <keno@juliacomputing.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>, Kyle Huey <khuey@kylehuey.com>,
Robert O'Callahan <robert@ocallahan.org>
Subject: Re: [RFC PATCH v2] x86/arch_prctl: Add ARCH_SET_XCR0 to set XCR0 per-thread
Date: Tue, 7 Apr 2020 14:21:03 +0200 [thread overview]
Message-ID: <20200407122103.GU20730@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200407011259.GA72735@juliacomputing.com>
On Mon, Apr 06, 2020 at 09:12:59PM -0400, Keno Fischer wrote:
> This is a follow-up to my from two-years ago [1]. I've been using
> rebased versions of that patch locally for my needs, but I've had
> more people ask me about this patch recently, so I figured, I'd
> have another go at this. Even if this doesn't make it into mainline,
> I figure I can at least improve the quality of the patch for others
> who want to use it. That's said, here's how this version is
> different from v1:
Aside of having an inconsistent comment style and whitespace damage, it
adds exports without a module user.
But my main reason for replying is asking: 'What the heck for?'
You had a fairly long changelog detailing what the patchd does; but I've
failed to find a single word on _WHY_ we want to do any of that.
next prev parent reply other threads:[~2020-04-07 12:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 1:12 [RFC PATCH v2] x86/arch_prctl: Add ARCH_SET_XCR0 to set XCR0 per-thread Keno Fischer
2020-04-07 3:57 ` Andy Lutomirski
2020-04-07 4:44 ` Keno Fischer
2020-04-07 4:53 ` Kyle Huey
2020-04-07 12:33 ` Peter Zijlstra
2020-04-07 13:52 ` Keno Fischer
2020-04-07 12:21 ` Peter Zijlstra [this message]
2020-04-07 14:06 ` Dave Hansen
2020-04-07 14:16 ` Andy Lutomirski
2020-04-07 18:30 ` Keno Fischer
2020-04-14 23:20 ` Andy Lutomirski
2020-04-15 0:09 ` Keno Fischer
2020-04-16 1:07 ` Andy Lutomirski
2020-04-16 1:14 ` Keno Fischer
2020-04-16 1:16 ` Keno Fischer
2020-04-16 1:22 ` Andy Lutomirski
2020-04-07 16:29 ` Kyle Huey
2020-04-07 13:14 ` Dave Hansen
[not found] ` <CABV8kRw1TQsqs+z43bSfZ5isctuFGMB4g_ztDYihiiXHcy4nVA@mail.gmail.com>
2020-04-07 16:27 ` Dave Hansen
2020-04-07 17:55 ` Keno Fischer
2020-04-07 20:21 ` Dave Hansen
2020-04-07 21:42 ` Andy Lutomirski
2020-04-07 22:15 ` Keno Fischer
2020-04-14 19:55 ` Keno Fischer
2020-04-07 14:20 ` Andi Kleen
2020-04-07 18:06 ` Keno Fischer
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=20200407122103.GU20730@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keno@juliacomputing.com \
--cc=khuey@kylehuey.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robert@ocallahan.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).