Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5755714ybl; Tue, 27 Aug 2019 09:12:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqx084d3s5NNDybYzmAAKByi7PgmVuuuYvy9/3gpgWADeXqldEBGHmwIEn48o6YFloJwBymA X-Received: by 2002:a63:9d43:: with SMTP id i64mr22043512pgd.306.1566922347759; Tue, 27 Aug 2019 09:12:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566922347; cv=none; d=google.com; s=arc-20160816; b=kwmHpy0sxF6h6mDwoblNmD6AECRBxDDWX3R0WnN9s4WJj0AQLm0/cqmBoqDwAX2duC ZIQIpPXgkZ07m0o27ARXROzAQp1RiW88frjXxaPN+HOSBnoNLwoS1LwLqf7oXwx/5Wc8 i7uDs1KNgef7ElSGMFIqxyxM99z/+wVyoKIvmHrK+CwGDXR3gurQ0ZW6W7SQ6Hqo+SJl OL87rIMYGnBGWb4tPAFg/Gim5ajDlTxkp6OSaaz4tyBlT2CoVHoUIAaZ7UHdtCbFF97T PFyenFefqwV/aWkvV7E3lFrNRkCkiMx6DGyweC3SIeTyR/LBJfqF7rk1gJqzYjgWrjis +skQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=wAZSFhrkNg8EdOkX7+bIojO3qOZTJEurdw0nzGyP6oc=; b=Nfv+VGmdpEyFUd3+SFJjeGK3Sea9HPkwqKEJoJCxqzIb/MQDfROG5Dv12WF4j70T7o MMFD8JlN8amDegkXhwcDlfhNljzPO1KJHaicY7t4uBmOCfPsrEwZyMZ3wcbjCTtrrRUh JwnQAxx5Qzg6dVVA//7Nf+cGnozA4nb5mB5QXx26IchEURg9gya3pXfCV8jbfxhoMo+R Th0SE6bjjm9PbnQe0kwHZov8zzt52AJFayWaJd16l4qW0zoqVsL9OnQ4m4caMlf8vIC9 zzPw8y++RCS2ZuhP16SnIX2IQHT97iu0WHSLgBi04r/WxuwxtYLJ72dP8vMezL7dcqqw xn6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=c7Qmh9V0; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a24si1909684pfl.15.2019.08.27.09.12.09; Tue, 27 Aug 2019 09:12:27 -0700 (PDT) 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=@google.com header.s=20161025 header.b=c7Qmh9V0; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729570AbfH0QK6 (ORCPT + 99 others); Tue, 27 Aug 2019 12:10:58 -0400 Received: from mail-io1-f67.google.com ([209.85.166.67]:38469 "EHLO mail-io1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726420AbfH0QK5 (ORCPT ); Tue, 27 Aug 2019 12:10:57 -0400 Received: by mail-io1-f67.google.com with SMTP id p12so47639303iog.5 for ; Tue, 27 Aug 2019 09:10:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wAZSFhrkNg8EdOkX7+bIojO3qOZTJEurdw0nzGyP6oc=; b=c7Qmh9V0mJfsmJ0EtwOBmGCFdov/0upZx5p7QsvvjmGhxRJqV+e8Z3ZHDER41CuEts K9cPQ1cOAheQbiqZ2SmTXQ1ZGiBiSjya9NaJFFWjm/BXZM++XyBrYhgHB5v1k5v2rd8e EAgsk1PetLvEQljYTJ1wKgeWp/Rr+wCQvCS20bG9aYWDplPJq+R6g3sqy/l0AmyBoSso f5VcH+pNgnuxyy9+HJXmprUUDNDHbFzyQ3WeemOF5F5fYMTMwHeB/sbcNgkq6WDiCtf+ yWdYD1L2ttJF8xjf2NNWIWCP/dzG/kIBLeUXWrR/aCXcTjQDkKfJ1eSIKLOvamky62TS rvHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wAZSFhrkNg8EdOkX7+bIojO3qOZTJEurdw0nzGyP6oc=; b=J1bnYPNaonLbUXOfrXNhwMTJIUQO7UQT59kwPIj0hB7cDCKtJsMIIQxs9kCNJPXkmK iL0pi+TS+d+kJ6zDmBBDLJ2ExHNhsu29W/RULmeD58KMPeq8EqeAVCh0qAjs0bnNoqYs EAiGvQzgVK97q9LpsQDmTkEceoQd6t6+zUWvRl/TUzM19YYjmR2PnC/HTtXnTQaIJ4+G 4Cc1XdSCO3YcpIf52aIpMHJiZw0ty+7IBrr+BblEKmfVP9Zq8O8bVQ7yPRhpdYvMTF4h SZHi3gM1H91TIW9xHk5ot7D+Upf8pnjtix6v5RyJU7i5AjCAkQdiQeoGdCE+qv8i7t/p gv2Q== X-Gm-Message-State: APjAAAV4x7L/bT19UA/YDi0sZtIxvf9xPRf96cu1nHOnaIL5jDzCrhw5 BsX4p+GnJdR3N/P3dBm+AurAfMo8S7ql1MAv8AW+Wg== X-Received: by 2002:a02:cc8f:: with SMTP id s15mr23773601jap.53.1566922256653; Tue, 27 Aug 2019 09:10:56 -0700 (PDT) MIME-Version: 1.0 References: <20190826081752.57258-1-kkamagui@gmail.com> In-Reply-To: From: Matthew Garrett Date: Tue, 27 Aug 2019 09:10:45 -0700 Message-ID: Subject: Re: [PATCH] x86: tpm: Remove a busy bit of the NVS area for supporting AMD's fTPM To: Seunghun Han Cc: Jarkko Sakkinen , Matthew Garrett , Peter Huewe , "open list:TPM DEVICE DRIVER" , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 27, 2019 at 1:23 AM Seunghun Han wrote: > If the regions allocated in the NVS region need to be handled by a > driver, the callback mechanism is good for it. However, this case > doesn't need it because the regions allocated in NVS are just I/O > regions. > > In my opinion, if the driver wants to handle the region in the NVS > while suspending or hibernating, it has to use register_pm_notifier() > function and handle the event. We already had the mechanism that could > ensure that the cases you worried about would be handled, so it seems > to me that removing the busy bit from the NVS region is fine. No. The NVS regions are regions that need to be saved and restored over hibernation, but which aren't otherwise handled by a driver - that's why the NVS code exists. If drivers are allowed to bind to NVS regions without explicit handling, they risk conflicting with that.