[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ftcrtckg.fsf@nanos.tec.linutronix.de>
Date: Sun, 26 Apr 2020 00:39:27 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Sasha Levin <sashal@...nel.org>,
Andy Lutomirski <luto@...capital.net>
Cc: Andi Kleen <ak@...ux.intel.com>, Andy Lutomirski <luto@...nel.org>,
"Bae\, Chang Seok" <chang.seok.bae@...el.com>,
"Metzger\, Markus T" <markus.t.metzger@...el.com>,
"hpa\@zytor.com" <hpa@...or.com>, "bp\@alien8.de" <bp@...en8.de>,
"Hansen\, Dave" <dave.hansen@...el.com>,
"Luck\, Tony" <tony.luck@...el.com>,
Pedro Alves <palves@...hat.com>,
Simon Marchi <simark@...ark.ca>,
"Shankar\, Ravi V" <ravi.v.shankar@...el.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v9 00/17] Enable FSGSBASE instructions
Sasha Levin <sashal@...nel.org> writes:
> On Wed, Apr 22, 2020 at 04:00:16PM -0700, Andy Lutomirski wrote:
>>
>>gdb and rr are certainly a good start. If patches show up, I'll take a look.
>
> I'm sorry, but what patches are we talking about?
About patches which:
- Are rebased to current upstream
- Addressed the outstanding review comments
- Have proper documentation in the changelog of the user space visible
ABI changes why it does not break any existing usage and having the
relevant people who maintain tools which utilize the affected
interfaces Cc'ed on submission.
- Made sure that the cleanups I did when merging them initially have
been picked up. I'm not going to waste another couple of days on
this mess just to revert it because it hadn't seen any serious
testing in development.
Thanks,
tglx
Powered by blists - more mailing lists