From: Andy Lutomirski <luto@kernel.org>
To: Keno Fischer <keno@juliacomputing.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<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: Wed, 15 Apr 2020 18:07:01 -0700 [thread overview]
Message-ID: <CALCETrWTDrcynTwpWZ6u6JXRL1rz6_vakLK7=BqMjCPCkQ+9dg@mail.gmail.com> (raw)
In-Reply-To: <CABV8kRxfMNxzy8r2P4GKj-22i+GMj=VDfPWAZB-VSgfrsQsjCA@mail.gmail.com>
On Tue, Apr 14, 2020 at 5:10 PM Keno Fischer <keno@juliacomputing.com> wrote:
>
> > (why would you want to record with an unusual XCR0?)
>
Hmm. I don't personally have a strong objection to allowing XCR0 to
be overridden as long as it's done reasonably sanely. And maybe
requires a sysctl to be enabled.
Would it make matters easier if tasks with nonstandard XCR0 were not
allowed to use ptrace() at all? And if ARCH_SET_XCR0 were disallowed
if the caller is tracing anyone?
next prev parent reply other threads:[~2020-04-16 1:07 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
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 [this message]
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='CALCETrWTDrcynTwpWZ6u6JXRL1rz6_vakLK7=BqMjCPCkQ+9dg@mail.gmail.com' \
--to=luto@kernel.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--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=peterz@infradead.org \
--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 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.