Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp4772184ybc; Fri, 15 Nov 2019 09:49:26 -0800 (PST) X-Google-Smtp-Source: APXvYqx0LYECM04Nxl7jS5Jt++nJAik0oEnn3GqfMCVBAgKZs34D2YZeS5bRaR0dQQvSFrI9+TRt X-Received: by 2002:a5d:490c:: with SMTP id x12mr2674816wrq.301.1573840165969; Fri, 15 Nov 2019 09:49:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573840165; cv=none; d=google.com; s=arc-20160816; b=G2HQDm5D9AZGUQGf+yaq29H0Sz7CeNUydChbUuMc8yNbHiP9ClyfzSggfeA+ZJ5sw6 tsDFoPSrzAYtmh+MdUVbGHPNrTiS395NmVdXrXCtEJ7iH0mb6aZSp0J5ZdMxabbdH0no hdipNlpt9xO4vubfvKXGD9qc7M1uFdgy0GHcVP2Frh6HnCYlykaMJ1tTAZEZ5z36HRXc kE6/OBQwG5BDqdGjU6MAki1hitfOseUT0PZPix+oXH9GGzwXC7XO1Ebw7Ju4X1O9IXBg EiLlJqdjgWTpGeS5MyN292Nl+r0G/COCo971wJmt7GUSSqOTmXnP/1XrNn0Kpzw4y+XJ q/jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:user-agent:in-reply-to:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=HGq8jc1LJlY1741ot7fezu8w/ETUBmd5wl0nIESlykU=; b=bTzteFli7kgHGCYahJ8/fWaSs8zcoutGqm+wXLqeF8A/YT0k/fdv8urQoZDoHjKEWz zJrkTPsZpWNMbF0W6fgtKtQx7A55XrrdyX9sC2S6vko6qJffSwYwc4ZE7lUbMBMBay33 QHMXjvfHjOe0Y7uqnNs9K8FauO0AGqbxj7hT8A0WK9kpw89nqM6g251fTinNS0WA0mfo 6lMmD0rYDS4W1vZM5c35VtQIyd6xo9pyFLbnL6O1FTSqVB0uZj9Tc9HZjwCU/ieU22Wy Kz9sKCL4StjzLtfY69jT1vY43x6uH6n2b/9RXZ2KXQOpwG8wmla7wy/iPuiSXxrIs/l2 B7HA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JcPIWFFa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s10si6313897edh.138.2019.11.15.09.49.01; Fri, 15 Nov 2019 09:49:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JcPIWFFa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726956AbfKORq7 (ORCPT + 99 others); Fri, 15 Nov 2019 12:46:59 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:48555 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726466AbfKORq7 (ORCPT ); Fri, 15 Nov 2019 12:46:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573840018; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HGq8jc1LJlY1741ot7fezu8w/ETUBmd5wl0nIESlykU=; b=JcPIWFFadQsubpdW7FThfa6cG0L3FOhJKpFfZU8qIEcKCevBfFv/TMOv3w1JkK9C0rSgYP qUKE//Vjlx7ETvw0mecehCHJwlqIkUzQvYzA8c/zDGvrZKfUKNo9nq/ByHziqeJFCXI0QK wN9P+5g8r3YmpLHYO7omZsZNwnysDY4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-423-5obBkpWmNaOQOhyMmkCmhg-1; Fri, 15 Nov 2019 12:46:54 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E13DA1005510; Fri, 15 Nov 2019 17:46:52 +0000 (UTC) Received: from treble (ovpn-120-26.rdu2.redhat.com [10.10.120.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 42BCD5C548; Fri, 15 Nov 2019 17:46:51 +0000 (UTC) Date: Fri, 15 Nov 2019 11:46:49 -0600 From: Josh Poimboeuf To: David Laight Cc: 'Shile Zhang' , Peter Zijlstra , Masahiro Yamada , Michal Marek , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "x86@kernel.org" , "H . Peter Anvin" , "linux-kernel@vger.kernel.org" , "linux-kbuild@vger.kernel.org" Subject: Re: [RFC PATCH v3 7/7] x86/unwind/orc: remove run-time ORC unwind tables sort Message-ID: <20191115174649.ldif5o7xqo5ntxeo@treble> References: <20191115064750.47888-1-shile.zhang@linux.alibaba.com> <20191115064750.47888-8-shile.zhang@linux.alibaba.com> <893d3caf85cd4ed0921fab84cfe28cad@AcuMS.aculab.com> MIME-Version: 1.0 In-Reply-To: <893d3caf85cd4ed0921fab84cfe28cad@AcuMS.aculab.com> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-MC-Unique: 5obBkpWmNaOQOhyMmkCmhg-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 15, 2019 at 04:51:24PM +0000, David Laight wrote: > From: Shile Zhang > > Sent: 15 November 2019 06:48 > ... > > arch/x86/kernel/unwind_orc.c | 8 +++++--- > > 1 file changed, 5 insertions(+), 3 deletions(-) > >=20 > > diff --git a/arch/x86/kernel/unwind_orc.c b/arch/x86/kernel/unwind_orc.= c > > index 332ae6530fa8..280da6fa9922 100644 > > --- a/arch/x86/kernel/unwind_orc.c > > +++ b/arch/x86/kernel/unwind_orc.c > > @@ -273,9 +273,11 @@ void __init unwind_init(void) > > =09=09return; > > =09} > >=20 > > -=09/* Sort the .orc_unwind and .orc_unwind_ip tables: */ > > -=09sort(__start_orc_unwind_ip, num_entries, sizeof(int), orc_sort_cmp, > > -=09 orc_sort_swap); > > +=09/* > > +=09 * Note, orc_unwind and orc_unwind_ip tables has been sorted in > > +=09 * vmlinux link phase by sorttable tool at build time. > > +=09 * Its ready for binary search now. > > +=09 */ >=20 > How fast is sort() if the table is sorted? > Relying on the kernel sources and build scripts always being in sync seem= s dangerous. > Probably better to leave the sort in for a release of two. This patch comes after the build script changes, so they'd be in sync. What would the concern be? --=20 Josh