From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CCB9FC47254 for ; Tue, 5 May 2020 10:55:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A6346206A5 for ; Tue, 5 May 2020 10:55:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728422AbgEEKz2 (ORCPT ); Tue, 5 May 2020 06:55:28 -0400 Received: from foss.arm.com ([217.140.110.172]:37084 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728180AbgEEKz2 (ORCPT ); Tue, 5 May 2020 06:55:28 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A7EAC30E; Tue, 5 May 2020 03:55:27 -0700 (PDT) Received: from arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8E4183F305; Tue, 5 May 2020 03:55:26 -0700 (PDT) Date: Tue, 5 May 2020 11:55:24 +0100 From: Dave Martin To: Walter Harms Cc: Michael Kerrisk , Catalin Marinas , Will Deacon , Vincenzo Frascino , "linux-man@vger.kernel.org" , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: Adding arch-specific user ABI documentation in linux-man Message-ID: <20200505105522.GL30377@arm.com> References: <20200504153214.GH30377@arm.com> <32259f3763344500a058a8ca8a3a33d8@bfs.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32259f3763344500a058a8ca8a3a33d8@bfs.de> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org On Tue, May 05, 2020 at 07:45:32AM +0000, Walter Harms wrote: > Hi Dave, > you are pointing to an (IMHO) interesting question. > How to document different CPUs ? > Given that an operating system should hide the different CPU's using > CPU specific features should be used sparsely at best. Agreed! But there are real situations where cpu specifics can't be avoided, and having documentation will help people to use those features correctly. > the easy part are adds-on like flags for prctrl etc. simply add it to the page. For prctl, that makes sense (it's a jumble of arch specifics already). But would it be considered a problem if the ptrace page, say, becomes 80% arch-specific stuff? That page is cumbersome enough already... > Other things should go to a cpu specific pages (can of worms). The problem will > be to keep that small but informative. I have no idea about the level of detail > (and i have worked with a range of CPUs) that could be interesting for a programmer. > An of cause every other CPU now needs also a page. Fair enough. Cheers ---Dave From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Martin Subject: Re: Adding arch-specific user ABI documentation in linux-man Date: Tue, 5 May 2020 11:55:24 +0100 Message-ID: <20200505105522.GL30377@arm.com> References: <20200504153214.GH30377@arm.com> <32259f3763344500a058a8ca8a3a33d8@bfs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <32259f3763344500a058a8ca8a3a33d8-fPG8STNUNVg@public.gmane.org> Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Walter Harms Cc: Michael Kerrisk , Catalin Marinas , Will Deacon , Vincenzo Frascino , "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" List-Id: linux-arch.vger.kernel.org On Tue, May 05, 2020 at 07:45:32AM +0000, Walter Harms wrote: > Hi Dave, > you are pointing to an (IMHO) interesting question. > How to document different CPUs ? > Given that an operating system should hide the different CPU's using > CPU specific features should be used sparsely at best. Agreed! But there are real situations where cpu specifics can't be avoided, and having documentation will help people to use those features correctly. > the easy part are adds-on like flags for prctrl etc. simply add it to the page. For prctl, that makes sense (it's a jumble of arch specifics already). But would it be considered a problem if the ptrace page, say, becomes 80% arch-specific stuff? That page is cumbersome enough already... > Other things should go to a cpu specific pages (can of worms). The problem will > be to keep that small but informative. I have no idea about the level of detail > (and i have worked with a range of CPUs) that could be interesting for a programmer. > An of cause every other CPU now needs also a page. Fair enough. Cheers ---Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com ([217.140.110.172]:37084 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728180AbgEEKz2 (ORCPT ); Tue, 5 May 2020 06:55:28 -0400 Date: Tue, 5 May 2020 11:55:24 +0100 From: Dave Martin Subject: Re: Adding arch-specific user ABI documentation in linux-man Message-ID: <20200505105522.GL30377@arm.com> References: <20200504153214.GH30377@arm.com> <32259f3763344500a058a8ca8a3a33d8@bfs.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32259f3763344500a058a8ca8a3a33d8@bfs.de> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Walter Harms Cc: Michael Kerrisk , Catalin Marinas , Will Deacon , Vincenzo Frascino , "linux-man@vger.kernel.org" , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Message-ID: <20200505105524.olxqq9pZYNExvZeYL5gHmOqDE39rLhhW8rA6aBNT4zg@z> On Tue, May 05, 2020 at 07:45:32AM +0000, Walter Harms wrote: > Hi Dave, > you are pointing to an (IMHO) interesting question. > How to document different CPUs ? > Given that an operating system should hide the different CPU's using > CPU specific features should be used sparsely at best. Agreed! But there are real situations where cpu specifics can't be avoided, and having documentation will help people to use those features correctly. > the easy part are adds-on like flags for prctrl etc. simply add it to the page. For prctl, that makes sense (it's a jumble of arch specifics already). But would it be considered a problem if the ptrace page, say, becomes 80% arch-specific stuff? That page is cumbersome enough already... > Other things should go to a cpu specific pages (can of worms). The problem will > be to keep that small but informative. I have no idea about the level of detail > (and i have worked with a range of CPUs) that could be interesting for a programmer. > An of cause every other CPU now needs also a page. Fair enough. Cheers ---Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 13828C47254 for ; Tue, 5 May 2020 10:55:36 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D7026206A5 for ; Tue, 5 May 2020 10:55:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="I8QNuKcO" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D7026206A5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=tzZTG0AKXf/PdbMcyF3NDP1qdmwGy4zFlbYNuR3d0PU=; b=I8QNuKcOBFt0SR U0O46vO01x12sWamvDKmKIKUG9QGgKztO8gPlezBSY0EQZ1MEYfMdP02tqufRnYehtRO280CZQwK8 d07XYP1Itf5h0t/d6GwATveWXhWqRMUYyHsIIVrHPRVji3SZ01X4RvzK5PTdBqFRiFLPDl7m6Zrm2 FRfgLn6Mp2eC1jLcIU/9BSM2Ut9T/xe+6Ht/8++gA+X19Rnz0y2epDkTNlxFTtAMIxB/rjbcAnHHx DlT6NQF3A4QkTHjfNGOeNWPeI3wa7/gXk06KplstzGDmeeWZGqZT+u7ETg8s39U+gy5GeYzS8jK/f nKLSGIWdxI1YxdvE3HMQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jVvEc-0001hz-9z; Tue, 05 May 2020 10:55:34 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jVvEY-0001hK-Fe for linux-arm-kernel@lists.infradead.org; Tue, 05 May 2020 10:55:31 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A7EAC30E; Tue, 5 May 2020 03:55:27 -0700 (PDT) Received: from arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8E4183F305; Tue, 5 May 2020 03:55:26 -0700 (PDT) Date: Tue, 5 May 2020 11:55:24 +0100 From: Dave Martin To: Walter Harms Subject: Re: Adding arch-specific user ABI documentation in linux-man Message-ID: <20200505105522.GL30377@arm.com> References: <20200504153214.GH30377@arm.com> <32259f3763344500a058a8ca8a3a33d8@bfs.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <32259f3763344500a058a8ca8a3a33d8@bfs.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200505_035530_568677_8D72F36C X-CRM114-Status: GOOD ( 14.30 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "linux-arch@vger.kernel.org" , "linux-man@vger.kernel.org" , Catalin Marinas , Michael Kerrisk , Vincenzo Frascino , Will Deacon , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, May 05, 2020 at 07:45:32AM +0000, Walter Harms wrote: > Hi Dave, > you are pointing to an (IMHO) interesting question. > How to document different CPUs ? > Given that an operating system should hide the different CPU's using > CPU specific features should be used sparsely at best. Agreed! But there are real situations where cpu specifics can't be avoided, and having documentation will help people to use those features correctly. > the easy part are adds-on like flags for prctrl etc. simply add it to the page. For prctl, that makes sense (it's a jumble of arch specifics already). But would it be considered a problem if the ptrace page, say, becomes 80% arch-specific stuff? That page is cumbersome enough already... > Other things should go to a cpu specific pages (can of worms). The problem will > be to keep that small but informative. I have no idea about the level of detail > (and i have worked with a range of CPUs) that could be interesting for a programmer. > An of cause every other CPU now needs also a page. Fair enough. Cheers ---Dave _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel