From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM Coresight: Add PID control support for ETM tracing
Date: Wed, 4 Dec 2013 07:27:43 -0800 [thread overview]
Message-ID: <20131204152743.GC12847@kroah.com> (raw)
In-Reply-To: <CANsc=4Vy911xcf7fYEjyeV_CNGp8POje9BZrLSP8xrk4YAfSNA@mail.gmail.com>
On Tue, Dec 03, 2013 at 11:40:59PM -0500, Adrien Verg? wrote:
> @@ -616,7 +670,7 @@ static int etm_probe(struct amba_device *dev,
> const struct amba_id *id)
> if (ret)
> goto out_unmap;
>
> - /* failing to create any of these three is not fatal */
> + /* failing to create any of these four is not fatal */
> ret = sysfs_create_file(&dev->dev.kobj, &trace_info_attr.attr);
> if (ret)
> dev_dbg(&dev->dev, "Failed to create trace_info in sysfs\n");
> @@ -629,6 +683,10 @@ static int etm_probe(struct amba_device *dev,
> const struct amba_id *id)
> if (ret)
> dev_dbg(&dev->dev, "Failed to create trace_addrrange in sysfs\n");
>
> + ret = sysfs_create_file(&dev->dev.kobj, &trace_pid_attr.attr);
> + if (ret)
> + dev_dbg(&dev->dev, "Failed to create trace_pid in sysfs\n");
> +
> dev_dbg(t->dev, "ETM AMBA driver initialized.\n");
>
> out:
Again, not your fault, but you just raced with userspace, so now
userspace can't see your device files at all. Please use the correct
api for this (groups), and actually, it should all be using debugfs if
anything, not sysfs at all.
thanks,
greg k-h
next prev parent reply other threads:[~2013-12-04 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 4:40 [PATCH 3/3] ARM Coresight: Add PID control support for ETM tracing Adrien Vergé
2013-12-04 15:27 ` Greg Kroah-Hartman [this message]
2013-12-04 17:05 ` Greg Kroah-Hartman
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=20131204152743.GC12847@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).