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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=ham 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 D3454C31E50 for ; Sun, 16 Jun 2019 23:56:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9832C20818 for ; Sun, 16 Jun 2019 23:56:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=axtens.net header.i=@axtens.net header.b="mjFgfEh9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727448AbfFPX4L (ORCPT ); Sun, 16 Jun 2019 19:56:11 -0400 Received: from mail-pg1-f196.google.com ([209.85.215.196]:39045 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727225AbfFPX4L (ORCPT ); Sun, 16 Jun 2019 19:56:11 -0400 Received: by mail-pg1-f196.google.com with SMTP id 196so4724420pgc.6 for ; Sun, 16 Jun 2019 16:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axtens.net; s=google; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-transfer-encoding; bh=eKbpzEiJylVko/AqUmYGdm35tR1kAF8kyTrOQOn/LZY=; b=mjFgfEh9DpnUyYJnmm10xCAA44rjQ5vM3POmL21L1yxtntOM4gCLmgenR1CUMVLdRK bKJ5vWJRNlNGEcrq4IdxzCEHcpIe7vlLMfhuxhzjrr57rEblFOm2QshpZwxJlJUsK8FS r9C0ItB6L+JRovFIxzCuNpKzuioK88/Kll0kA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=eKbpzEiJylVko/AqUmYGdm35tR1kAF8kyTrOQOn/LZY=; b=eYC7l4q2AV3Za7jIdd64kGnaHOETRwahcA7W7MFN8HMwxSkMczpecUyZnCjoPBNfCh 6rkBaeDTyIJtZpB8Jp6oVdi72U3zAIlE22tXqurvPxlGqZEhdxFxg0/W6uwvgGIVxg5X B5bV2nTDtLGpZbIFi11gcVytD0zpnjyfzERNVL+8wzwc+AX+ioc3127kP/P7Wztt0L/F tGcyIRa8VJkoIShApfgt6yPAPTsR2e3vF6+xLFnBqF5XhVbGx0Y/Q/QbvfqZAnrRx/b9 dJkjIqBZ0QtDTbL2F1nkHEkKOZJ6gJaoIkHadt+0dq0uazwiLn1tnuclKdCf0KWlYwCB m6hg== X-Gm-Message-State: APjAAAXn5LVh33aN43DK5UMxzefJThhAtcqdxtFQAwg1oYKKJbSvJ+ge oGp6Zk9lhpXps51ktm/K4Q/8nQ== X-Google-Smtp-Source: APXvYqzVFXwvbw+h8Vy5oNuVgOROK+vJF9NO7ccBNAEWTkL02XdJ05Npe6ZqjRHegh2kVzPtwd85kA== X-Received: by 2002:a63:6981:: with SMTP id e123mr22346754pgc.136.1560729370570; Sun, 16 Jun 2019 16:56:10 -0700 (PDT) Received: from localhost (ppp167-251-205.static.internode.on.net. [59.167.251.205]) by smtp.gmail.com with ESMTPSA id v4sm9131345pfb.14.2019.06.16.16.56.08 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sun, 16 Jun 2019 16:56:09 -0700 (PDT) From: Daniel Axtens To: Nayna Cc: Nayna Jain , linuxppc-dev@ozlabs.org, linux-efi@vger.kernel.org, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, Michael Ellerman , Paul Mackerras , Benjamin Herrenschmidt , Ard Biesheuvel , Jeremy Kerr , Matthew Garret , Mimi Zohar , Claudio Carvalho , Eric Richter Subject: Re: [PATCH v3 1/3] powerpc/powernv: Add OPAL API interface to get secureboot state In-Reply-To: References: <1560198837-18857-1-git-send-email-nayna@linux.ibm.com> <1560198837-18857-2-git-send-email-nayna@linux.ibm.com> <87ftofpbth.fsf@dja-thinkpad.axtens.net> <87d0jipfr9.fsf@dja-thinkpad.axtens.net> Date: Mon, 17 Jun 2019 09:56:05 +1000 Message-ID: <87tvcp2iga.fsf@dja-thinkpad.axtens.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nayna, >> I guess I also somewhat object to calling it a 'backend' if we're using >> it as a version scheme. I think the skiboot storage backends are true >> backends - they provide different implementations of the same >> functionality with the same API, but this seems like you're using it to >> indicate different functionality. It seems like we're using it as if it >> were called OPAL_SECVAR_VERSION. > > We are changing how we are exposing the version to the kernel. The=20 > version will be exposed as device-tree entry rather than a OPAL runtime=20 > service. We are not tied to the name "backend", we can switch to calling= =20 > it as "scheme" unless there is a better name. This sounds like a good approach to me. Kind regards, Daniel > > Thanks & Regards, > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 - Nayna