[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjk-2c4XvWjdzc-bs9Hbgvy-p7ASSnKKphggr5qDoXRDQ@mail.gmail.com>
Date: Thu, 1 Nov 2018 08:33:35 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
boqun.feng@...il.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-api@...r.kernel.org, tglx@...utronix.de, luto@...capital.net,
davejwatson@...com, pjt@...gle.com,
Andrew Morton <akpm@...ux-foundation.org>,
linux@....linux.org.uk, Ingo Molnar <mingo@...hat.com>,
Peter Anvin <hpa@...or.com>, andi@...stfloor.org,
Christoph Lameter <cl@...ux.com>, bmaurer@...com,
rostedt@...dmis.org, josh@...htriplett.org,
Catalin Marinas <catalin.marinas@....com>, will.deacon@....com,
mtk.manpages@...il.com, joelaf@...gle.com
Subject: Re: [RFC PATCH for 4.21 00/16] rseq updates, new cpu_opv system call (v2)
On Thu, Nov 1, 2018 at 2:59 AM Mathieu Desnoyers
<mathieu.desnoyers@...icios.com> wrote:
>
> Here is an updated patchset submitted as RFC for 4.21 (next merge
> window).
So I'm not willing to take the cpu_opv system call until I see the the
regular rseq code getting more real-life use.
Maybe people are using it. Maybe they aren't. I want to hold off and
wait until we _know_ it's getting used, and not just in test
libraries.
Linus
Powered by blists - more mailing lists