LKML Archive on lore.kernel.org
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: Wed, 18 Apr 2018 08:31:36 +0000 [thread overview]
Message-ID: <1524040290.4031.25.camel@hxt-semitech.com> (raw)
In-Reply-To: <1524036520.2747.31.camel@intel.com>
Hi, Sohil
On Wed, 2018-04-18 at 07:27 +0000, Mehta, Sohil wrote:
> On Wed, 2018-04-18 at 05:58 +0000, Yang, Shunyong wrote:
> >
> > Hi, Gary and Sohil,
> >
> > On Tue, 2018-04-17 at 13:38 -0400, Hook, Gary wrote:
> > >
> > > On 4/13/2018 8:08 PM, Mehta, Sohil wrote:
> > > >
> > > >
> > > > On Fri, 2018-04-06 at 08:17 -0500, Gary R Hook wrote:
> > > > >
> > > > >
> > > > >
> > > > > +
> > > > > +void amd_iommu_debugfs_setup(struct amd_iommu *iommu)
> > > > > +{
> > > > > + char name[MAX_NAME_LEN + 1];
> > > > > + struct dentry *d_top;
> > > > > +
> > > > > + if (!debugfs_initialized())
> > > > Probably not needed.
> > > Right.
> > When will this check is needed?
> > IMO, this function is to check debugfs ready status before we want
> > to
> > use debugfs. I just want to understand when we should use
> > debugfs_initialized();
> >
> You are right debugfs_initialized() can be used to check if debugfs
> is
> ready. However in this case we can also rely on debugfs_create_dir()
> which is called in iommu_debufs_setup().
>
> debugfs_create_dir() says:
>
> * If debugfs is not enabled in the kernel, the value -%ENODEV will
> be
> * returned.
It seems "If debugfs is not enabled in the kernel"
means CONFIG_DEBUG_FS is not configured. Following is the code of no
such config.
static inline struct dentry *debugfs_create_dir(const char *name,
struct dentry *parent)
{
return ERR_PTR(-ENODEV);
}
Looking into the code, debugfs_initialized() return the value of
debugfs_registered. debugfs_registered is set to true after
debugfs_init() has been called.
However, debugfs_create_dir() doesn't call debugfs_initialized() or
check debugfs_registered value.
So, there is tiny different of checking status by debugfs_create_dir()
and debugfs_initialized(). Although it can achieve functionality here.
Maybe the original design is to call debugfs_initialized() before
calling debugfs_create_xxx()?
Thanks.
Shunyong.
>
> Sohil
>
> >
> > Thanks.
> > Shunyong.
> >
> > >
> > >
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > + return;
> > > > > +
> > > > > + mutex_lock(&amd_iommu_debugfs_lock);
> > > > > + if (!amd_iommu_debugfs) {
> > > > > + d_top = iommu_debugfs_setup();
> > > > > + if (d_top)
> > > > > + amd_iommu_debugfs =
> > > > > debugfs_create_dir("amd", d_top);
> > > > > + }
> > > > > + mutex_unlock(&amd_iommu_debugfs_lock);
next prev parent reply other threads:[~2018-04-18 8:31 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
2018-04-06 13:17 ` [PATCH v3 1/2] iommu - Enable debugfs exposure of the IOMMU Gary R Hook
2018-04-13 23:55 ` Mehta, Sohil
2018-04-17 17:36 ` Hook, Gary
2018-04-17 17:55 ` Robin Murphy
2018-04-17 18:06 ` Hook, Gary
2018-04-17 17:46 ` Hook, Gary
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
2018-04-14 0:08 ` Mehta, Sohil
2018-04-17 17:38 ` Hook, Gary
2018-04-18 5:58 ` Yang, Shunyong
2018-04-18 7:27 ` Mehta, Sohil
2018-04-18 8:31 ` Yang, Shunyong [this message]
2018-04-18 20:16 ` Mehta, Sohil
2018-04-18 20:51 ` Hook, Gary
2018-04-19 1:52 ` Yang, Shunyong
2018-04-30 19:57 ` Gary R Hook
2018-04-17 0:52 ` Mehta, Sohil
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=1524040290.4031.25.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 \
--subject='Re: [PATCH v3 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU' \
/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
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).