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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 4A511C433F5 for ; Thu, 10 Mar 2022 12:37:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=IMUfxPZ4GccqKQOeV10wPs6MwTs7EoqSUREbZTR0n88=; b=UVagrw/bZgdpng 7edyr6IRvM+lQUJCPRiHWswqLNwnDkQmB96p3zi/H6DiYiYnPP0JsCJF8B3zNXalzd4tRRgco7dcs PoTKsILzIxNGysT6f6E0+QJvUDMNrpBLh4KA/WURaLf44B5reeALozMfZ/A91DPxGYCUCzIDnIDtk ftlmRGqGjbx8XPzr7/D7NOoEBPSe8nIrPwmHOnHa+RahddlTnK6FYi3a2mtTXsE4EEOAtMIKrDM5W 8ErWu+v2gY4GVUnAKxlc9BWYOi0ktl9MTTaH5kz9072RWbOOjW4wtI6CTs0THWZnejBOeNFBCDFLb IrR/YSxRW76L3d8PcyRg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nSI1n-00Co2t-HT; Thu, 10 Mar 2022 12:36:23 +0000 Received: from linux.microsoft.com ([13.77.154.182]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nSI1c-00Cnyb-P3 for linux-arm-kernel@lists.infradead.org; Thu, 10 Mar 2022 12:36:14 +0000 Received: from [192.168.254.32] (unknown [47.189.24.195]) by linux.microsoft.com (Postfix) with ESMTPSA id E7B1C20B7178; Thu, 10 Mar 2022 04:36:09 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com E7B1C20B7178 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1646915770; bh=OpLazLHgo7JUDorbgPvzn5XPP27hWdflyI7VUjRdwJM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=oWQjaQXeK6bs8wAX1nWaVSxmsT0mTsCAm8ubndFXfYmqBoPy4pR1J2MCW8qgC70/+ j2WyfH50ToQIyBVT6qVk00okQRSwfzpftPWUGJpJIetXHGVn07FRhKe+jFnwmYr7Nc 1SSZjx6jwP186N8aTa+7k3/OrfLBHo5dpEQy22ho= Message-ID: <574cbef1-89ce-3e43-cebb-5db1d8e854e5@linux.microsoft.com> Date: Thu, 10 Mar 2022 06:36:09 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v13 06/11] arm64: Use stack_trace_consume_fn and rename args to unwind() Content-Language: en-US To: Miroslav Benes , Mark Brown Cc: Mark Rutland , jpoimboe@redhat.com, ardb@kernel.org, nobuta.keiya@fujitsu.com, sjitindarsingh@gmail.com, catalin.marinas@arm.com, will@kernel.org, jmorris@namei.org, linux-arm-kernel@lists.infradead.org, live-patching@vger.kernel.org, linux-kernel@vger.kernel.org References: <95691cae4f4504f33d0fc9075541b1e7deefe96f> <20220117145608.6781-1-madvenka@linux.microsoft.com> <20220117145608.6781-7-madvenka@linux.microsoft.com> <845e4589-97d9-5371-3a0e-f6e05919f32d@linux.microsoft.com> From: "Madhavan T. Venkataraman" In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220310_043612_948569_1EADD1F5 X-CRM114-Status: GOOD ( 21.79 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 3/10/22 02:33, Miroslav Benes wrote: > On Wed, 9 Mar 2022, Mark Brown wrote: > >> On Tue, Mar 08, 2022 at 04:00:35PM -0600, Madhavan T. Venkataraman wrote: >> >>> It is just that patch 11 that defines "select >>> HAVE_RELIABLE_STACKTRACE" did not receive any comments from you >>> (unless I missed a comment that came from you. That is entirely >>> possible. If I missed it, my bad). Since you suggested that change, I >>> just wanted to make sure that that patch looks OK to you. >> >> I think that's more a question for the livepatch people to be honest - >> it's not entirely a technical one, there's a bunch of confidence level >> stuff going on. For example there was some suggestion that people might >> insist on having objtool support, though there's also substantial >> pushback on making objtool a requirement for anything from other >> quarters. I was hoping that posting that patch would provoke some >> discussion about what exactly is needed but that's not happened thus >> far. > > I think everyone will be happy with HAVE_RELIABLE_STACKTRACE on arm64 as > long as there is a guarantee that stack traces are really reliable. My > understanding is that there is still some work to be done on arm64 arch > side (but I may have misunderstood what Mark R. said elsewhere). And yes, > then there is a question of objtool. It is one option but not the only > one. There have been proposals of implementing guarantees on a compiler > side and leaving objtool for x86_64 only (albeit objtool may bring more > features to the table... ORC, arch features checking). > > Madhavan also mentioned that he enhanced objtool and he planned to submit > it eventually > (https://lore.kernel.org/all/1a0e19db-a7f8-4c8e-0163-398fcd364d54@linux.microsoft.com/T/#u), > so maybe arm64 maintainers could decide on a future direction based on > that? > Yes. I am working on that right now. Hope to send it out soon. Madhavan _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel