lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <1444231603-26676-5-git-send-email-mathieu.poirier@linaro.org> Date: Wed, 7 Oct 2015 09:26:41 -0600 From: Mathieu Poirier <mathieu.poirier@...aro.org> To: gregkh@...uxfoundation.org Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, mathieu.poirier@...aro.org Subject: [PATCH 4/6] coresight: etm3x: adding cpu affinity to sysFS interface Without access to the device tree, it is impossible to know what CPU a tracer is affined to. As such adding a new sysFS interface to convey the information. Signed-off-by: Mathieu Poirier <mathieu.poirier@...aro.org> --- drivers/hwtracing/coresight/coresight-etm3x.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/drivers/hwtracing/coresight/coresight-etm3x.c b/drivers/hwtracing/coresight/coresight-etm3x.c index bf2476ed9356..4797f56e7f13 100644 --- a/drivers/hwtracing/coresight/coresight-etm3x.c +++ b/drivers/hwtracing/coresight/coresight-etm3x.c @@ -1545,6 +1545,18 @@ static ssize_t status_show(struct device *dev, } static DEVICE_ATTR_RO(status); +static ssize_t cpu_show(struct device *dev, + struct device_attribute *attr, char *buf) +{ + int val; + struct etm_drvdata *drvdata = dev_get_drvdata(dev->parent); + + val = drvdata->cpu; + return scnprintf(buf, PAGE_SIZE, "%d\n", val); + +} +static DEVICE_ATTR_RO(cpu); + static ssize_t traceid_show(struct device *dev, struct device_attribute *attr, char *buf) { @@ -1621,6 +1633,7 @@ static struct attribute *coresight_etm_attrs[] = { &dev_attr_timestamp_event.attr, &dev_attr_status.attr, &dev_attr_traceid.attr, + &dev_attr_cpu.attr, NULL, }; ATTRIBUTE_GROUPS(coresight_etm); -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists