From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v4 5/6] parisc: wire up rseq system call Date: Fri, 12 Oct 2018 13:52:15 +0200 Message-ID: References: <1539337442-3676-1-git-send-email-firoz.khan@linaro.org> <1539337442-3676-6-git-send-email-firoz.khan@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Firoz Khan Cc: Parisc List , "James E.J. Bottomley" , Helge Deller , Thomas Gleixner , gregkh , Philippe Ombredanne , Kate Stewart , y2038 Mailman List , Linux Kernel Mailing List , linux-arch , Deepa Dinamani , Marcin Juszkiewicz List-Id: linux-arch.vger.kernel.org On Fri, Oct 12, 2018 at 12:16 PM Firoz Khan wrote: > > Hi Arnd, > > On Fri, 12 Oct 2018 at 15:26, Arnd Bergmann wrote: > > > > On Fri, Oct 12, 2018 at 11:45 AM Firoz Khan wrote: > > > > > > Wire up rseq system call requires an architecture specific > > > implementation as it not present now. > > > > > > Signed-off-by: Firoz Khan > > > > Didn't we conclude that this should be skipped? > > Helge told "I prefer to keep the warning for rseq for now. > It reminds me that we still may want the rseq syscall. > If the warning is a problem, you may simply add the __IGNORE_rseq define." > > I chose this option; I feel it looks clean > "# rseq requires an architecture specific implementation" in syscall.tbl > hopefully remind him to add rseq syscall implementation in this architecture. > But he said he wants the warning instead. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-f193.google.com ([209.85.160.193]:44369 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727816AbeJLTYh (ORCPT ); Fri, 12 Oct 2018 15:24:37 -0400 MIME-Version: 1.0 References: <1539337442-3676-1-git-send-email-firoz.khan@linaro.org> <1539337442-3676-6-git-send-email-firoz.khan@linaro.org> In-Reply-To: From: Arnd Bergmann Date: Fri, 12 Oct 2018 13:52:15 +0200 Message-ID: Subject: Re: [PATCH v4 5/6] parisc: wire up rseq system call Content-Type: text/plain; charset="UTF-8" Sender: linux-arch-owner@vger.kernel.org List-ID: To: Firoz Khan Cc: Parisc List , "James E.J. Bottomley" , Helge Deller , Thomas Gleixner , gregkh , Philippe Ombredanne , Kate Stewart , y2038 Mailman List , Linux Kernel Mailing List , linux-arch , Deepa Dinamani , Marcin Juszkiewicz Message-ID: <20181012115215.DujteyRcmQaJDJKqq1hwCNF2KzI7ghJn57nqtuhXzqU@z> On Fri, Oct 12, 2018 at 12:16 PM Firoz Khan wrote: > > Hi Arnd, > > On Fri, 12 Oct 2018 at 15:26, Arnd Bergmann wrote: > > > > On Fri, Oct 12, 2018 at 11:45 AM Firoz Khan wrote: > > > > > > Wire up rseq system call requires an architecture specific > > > implementation as it not present now. > > > > > > Signed-off-by: Firoz Khan > > > > Didn't we conclude that this should be skipped? > > Helge told "I prefer to keep the warning for rseq for now. > It reminds me that we still may want the rseq syscall. > If the warning is a problem, you may simply add the __IGNORE_rseq define." > > I chose this option; I feel it looks clean > "# rseq requires an architecture specific implementation" in syscall.tbl > hopefully remind him to add rseq syscall implementation in this architecture. > But he said he wants the warning instead. Arnd