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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 99CD4C001B0 for ; Tue, 4 Jul 2023 09:28:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231634AbjGDJ2E (ORCPT ); Tue, 4 Jul 2023 05:28:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49200 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230382AbjGDJ2D (ORCPT ); Tue, 4 Jul 2023 05:28:03 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C6EE6138 for ; Tue, 4 Jul 2023 02:28:00 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id 3f1490d57ef6-c2cf4e61bc6so6282974276.3 for ; Tue, 04 Jul 2023 02:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1688462880; x=1691054880; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=e3TXes7w/Rmbj1DkXFlIvKaLc8Xq0FgJi7YMpllWJrA=; b=OoCw2qkjIS9uiDScfmNBkgBtmk4wM2nR69ViCcOw5vgDxOdTw0w90Ian78v4vjjtl0 jOEeYH5dAB9l2vu6zowl1gNS4Knq4xtgos/5Krc4brqkt87G6myHuET4b5h9T4eRTzAH jtjIZTpHCpo1bz/be4ypmzT8DzCk4IrLebNiL7On5eSxPZEiLK9zBhExqgVQRAikyZji wGZzLQKaAdUQ3HS8xgMYwa6pZnr3n4D+awAFX88m9wK7eYgFZGHia9ZLhD8kyCBUxQv+ sIJsAV8/whbNvJkxelVWjyf9mWZbmCgDDFMaHHF36MAqJDWkM46Xh0+bZPrBIdRrc6bx PIEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688462880; x=1691054880; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=e3TXes7w/Rmbj1DkXFlIvKaLc8Xq0FgJi7YMpllWJrA=; b=Iqmaf8lpztXU/PDIkirr93ccq60sF3VQOjtdZ4Ac/yS+Mpoepa/Agf4Ab2IycS3PGZ sH5bugWfUq2ZaFWpP/NMdVIR6ZpkVOWf5L3T60io39ezeki2pDONJKxbgCSbs98ZJyHQ nuNPOOjuMQGaciJbDfRaSNbLjrwMtuRDiqxD/0xVXAYJJ1iVbIVmjxa6mM/toxA631Q1 b0DXvUmvS73Ne1DnbidEYaIa9kSBYY0i3cpJtmEJfz2k2MG/FCk5lBes4svWzzsHRna5 Uu67SGeooP1CsnnEqoSG98G6I3Bpq/QJ6u/jm6jloE7CcKoXMDL9m0RbzGDivpKFOVnS QfvQ== X-Gm-Message-State: ABy/qLYgT9UvGDIiAzU9KQnqnsX6Kc2ncyHQ02OjcmcU70qIULGS4qOh iyNWcblUUIH2OIi7ZAMpSCUNG0q9TdAfjuxwxMGNDQ== X-Google-Smtp-Source: APBJJlGjlh3CvPVpKROT51T36lYrYgCT70VTb+HBZrybLXHHEs7NrC37lmVz+67sLTPrYH9vI8gYMaFOi6LN15jfFD0= X-Received: by 2002:a25:1d7:0:b0:c4d:96a2:5d96 with SMTP id 206-20020a2501d7000000b00c4d96a25d96mr7651767ybb.34.1688462880018; Tue, 04 Jul 2023 02:28:00 -0700 (PDT) MIME-Version: 1.0 References: <1687955688-20809-1-git-send-email-quic_mojha@quicinc.com> <2023062814-chance-flounder-f002@gregkh> In-Reply-To: From: Linus Walleij Date: Tue, 4 Jul 2023 11:27:48 +0200 Message-ID: Subject: Re: [PATCH v4 00/21] Add Qualcomm Minidump kernel driver related support To: Rob Herring , Mathieu Poirier , Alexander Shishkin Cc: Greg KH , Mukesh Ojha , corbet@lwn.net, agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com, catalin.marinas@arm.com, will@kernel.org, andy.shevchenko@gmail.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-hardening@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, Jun 29, 2023 at 1:12=E2=80=AFAM Rob Herring wr= ote: > My bigger issue with this whole series is what would this all look > like if every SoC vendor upstreamed their own custom dumping > mechanism. That would be a mess. (I have similar opinions on the > $soc-vendor hypervisors.) I agree with Rob's stance. I think it would be useful to get input from the hwtracing developers (Alexander and Mathieu) who faced this "necessarily different" issue with all the hwtrace mechanisms and found a way out of it. I suspect they can have an idea of how this should be abstracted. Yours, Linus Walleij