iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>
To: "sohil.mehta@intel.com" <sohil.mehta@intel.com>,
	"gary.hook@amd.com" <gary.hook@amd.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"ghook@amd.com" <ghook@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU
Date: Thu, 19 Apr 2018 01:52:02 +0000	[thread overview]
Message-ID: <1524102722.10902.1.camel@hxt-semitech.com> (raw)
In-Reply-To: <151f3396-959b-86f6-e056-58d38682d858@amd.com>

Hi, Gary,

On Wed, 2018-04-18 at 16:51 -0400, Hook, Gary wrote:
> On 4/18/2018 4:16 PM, Mehta, Sohil wrote:
> > 
> > On Wed, 2018-04-18 at 08:31 +0000, Yang, Shunyong wrote:
> > > 
> > > Maybe the original design is to call debugfs_initialized() before
> > > calling debugfs_create_xxx()?
> > I am unaware of the original design. Someone else would probably
> > have
> > more context. However, looking at other places in the kernel where
> > debugfs_create_xx() is used, the common convention seems to be to
> > avoid
> > calling debugfs_initialized().
> > 
> >   Sohil
> > 
> debugfs_initialized() was introduced in commit c0f92ba99 back in 
> 2.6.30-rc1. It was intended as a helper, not as a gatekeeper, which
> is 
> why one doesn't see it used. Given that my use in this proposed patch
> is 
> straightforward, I'm not seeing the need here. I had just seen some 
> other code that used it, and copied the model.
> 
> Unless someone comes along to say, yes, use it, I'll not.
> 

I agree with you and Sohil on removing the unnecessary function
calling.

Thanks.
Shunyong.


> Gary

  reply	other threads:[~2018-04-19  1:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 13:17 [PATCH v3 0/2] Base enablement of IOMMU debugfs support Gary R Hook
     [not found] ` <152302042701.47565.17954813724758433858.stgit-tq90VzyE+wXkLsZ8J5Uweg@public.gmane.org>
2018-04-06 13:17   ` [PATCH v3 1/2] iommu - Enable debugfs exposure of the IOMMU Gary R Hook
     [not found]     ` <152302066417.47565.4017200105445420643.stgit-tq90VzyE+wXkLsZ8J5Uweg@public.gmane.org>
2018-04-13 23:55       ` Mehta, Sohil
     [not found]         ` <1523663790.2747.4.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-04-17 17:36           ` Hook, Gary
     [not found]             ` <10e422dd-a3ca-8ecb-50fa-e7f131a55a12-5C7GfCeVMHo@public.gmane.org>
2018-04-17 17:55               ` Robin Murphy
2018-04-17 18:06                 ` Hook, Gary
2018-04-17 17:46       ` Hook, Gary
     [not found]         ` <9123cd44-e01f-bff6-8441-792acbde10bc-5C7GfCeVMHo@public.gmane.org>
2018-04-17 18:13           ` Robin Murphy
2018-04-06 13:17   ` [PATCH v3 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook
     [not found]     ` <152302067362.47565.628887796165116844.stgit-tq90VzyE+wXkLsZ8J5Uweg@public.gmane.org>
2018-04-14  0:08       ` Mehta, Sohil
2018-04-17 17:38         ` Hook, Gary
     [not found]           ` <efa2b7a3-04a7-20b1-3651-89ebafa85c27-5C7GfCeVMHo@public.gmane.org>
2018-04-18  5:58             ` Yang, Shunyong
     [not found]               ` <1524031122.4031.5.camel-PT9Dzx9SjPiXmMXjJBpWqg@public.gmane.org>
2018-04-18  7:27                 ` Mehta, Sohil
2018-04-18  8:31                   ` Yang, Shunyong
2018-04-18 20:16                     ` Mehta, Sohil
     [not found]                       ` <1524082659.2747.37.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-04-18 20:51                         ` Hook, Gary
2018-04-19  1:52                           ` Yang, Shunyong [this message]
2018-04-30 19:57             ` Gary R Hook
2018-04-17  0:52       ` Mehta, Sohil
     [not found]         ` <1523926423.2747.19.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-04-17 17:42           ` Hook, Gary
2018-04-17 18:05             ` Robin Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1524102722.10902.1.camel@hxt-semitech.com \
    --to=shunyong.yang@hxt-semitech.com \
    --cc=gary.hook@amd.com \
    --cc=ghook@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sohil.mehta@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).