| 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: <ZeCXtzwX2xTyEGtK@bogus>
Date: Thu, 29 Feb 2024 14:41:59 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Cristian Marussi <cristian.marussi@....com>
Cc: Sibi Sankar <quic_sibis@...cinc.com>, andersson@...nel.org,
Sudeep Holla <sudeep.holla@....com>, konrad.dybcio@...aro.org,
jassisinghbrar@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
quic_rgottimu@...cinc.com, quic_kshivnan@...cinc.com,
conor+dt@...nel.org, Amir Vajid <avajid@...cinc.com>
Subject: Re: [RFC 4/7] soc: qcom: Utilize qcom scmi vendor protocol for bus
dvfs
On Tue, Feb 20, 2024 at 04:19:02PM +0000, Cristian Marussi wrote:
> On Wed, Jan 17, 2024 at 11:04:55PM +0530, Sibi Sankar wrote:
> > From: Shivnandan Kumar <quic_kshivnan@...cinc.com>
> >
> > This patch introduces a client driver that interacts with the SCMI QCOM
> > vendor protocol and passes on the required tuneables to start various
> > features running on the SCMI controller.
> >
> > Signed-off-by: Shivnandan Kumar <quic_kshivnan@...cinc.com>
> > Co-developed-by: Ramakrishna Gottimukkula <quic_rgottimu@...cinc.com>
> > Signed-off-by: Ramakrishna Gottimukkula <quic_rgottimu@...cinc.com>
> > Co-developed-by: Amir Vajid <avajid@...cinc.com>
> > Signed-off-by: Amir Vajid <avajid@...cinc.com>
> > Co-developed-by: Sibi Sankar <quic_sibis@...cinc.com>
> > Signed-off-by: Sibi Sankar <quic_sibis@...cinc.com>
> > ---
> > drivers/soc/qcom/Kconfig | 10 +
> > drivers/soc/qcom/Makefile | 1 +
> > drivers/soc/qcom/qcom_scmi_client.c | 486 ++++++++++++++++++++++++++++
> > 3 files changed, 497 insertions(+)
> > create mode 100644 drivers/soc/qcom/qcom_scmi_client.c
> >
> > diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
> > index c6ca4de42586..1530558aebfb 100644
> > --- a/drivers/soc/qcom/Kconfig
> > +++ b/drivers/soc/qcom/Kconfig
> > @@ -264,6 +264,16 @@ config QCOM_ICC_BWMON
> > the fixed bandwidth votes from cpufreq (CPU nodes) thus achieve high
> > memory throughput even with lower CPU frequencies.
> >
> > +config QCOM_SCMI_CLIENT
> > + tristate "Qualcomm Technologies Inc. SCMI client driver"
> > + depends on QCOM_SCMI_VENDOR_PROTOCOL || COMPILE_TEST
> > + default n
> > + help
> > + SCMI client driver registers for SCMI QCOM vendor protocol.
> > +
> > + This driver interacts with the vendor protocol and passes on the required
> > + tuneables to start various features running on the SCMI controller.
> > +
> > config QCOM_INLINE_CRYPTO_ENGINE
> > tristate
> > select QCOM_SCM
> > diff --git a/drivers/soc/qcom/Makefile b/drivers/soc/qcom/Makefile
> > index 05b3d54e8dc9..c2a51293c886 100644
> > --- a/drivers/soc/qcom/Makefile
> > +++ b/drivers/soc/qcom/Makefile
> > @@ -32,5 +32,6 @@ obj-$(CONFIG_QCOM_APR) += apr.o
> > obj-$(CONFIG_QCOM_LLCC) += llcc-qcom.o
> > obj-$(CONFIG_QCOM_KRYO_L2_ACCESSORS) += kryo-l2-accessors.o
> > obj-$(CONFIG_QCOM_ICC_BWMON) += icc-bwmon.o
> > +obj-$(CONFIG_QCOM_SCMI_CLIENT) += qcom_scmi_client.o
> > qcom_ice-objs += ice.o
> > obj-$(CONFIG_QCOM_INLINE_CRYPTO_ENGINE) += qcom_ice.o
> > diff --git a/drivers/soc/qcom/qcom_scmi_client.c b/drivers/soc/qcom/qcom_scmi_client.c
> > new file mode 100644
> > index 000000000000..418aa7900496
> > --- /dev/null
> > +++ b/drivers/soc/qcom/qcom_scmi_client.c
> > @@ -0,0 +1,486 @@
> > +// SPDX-License-Identifier: GPL-2.0-only
> > +/*
> > + * Copyright (c) 2024, The Linux Foundation. All rights reserved.
> > + */
> > +
> > +#include <linux/cpu.h>
> > +#include <linux/err.h>
> > +#include <linux/errno.h>
> > +#include <linux/init.h>
> > +#include <linux/kernel.h>
> > +#include <linux/module.h>
> > +#include <linux/of.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/qcom_scmi_vendor.h>
> > +#include <linux/scmi_protocol.h>
> > +
> > +#define MAX_MEMORY_TYPES 3
> > +#define MEMLAT_ALGO_STR 0x74616C6D656D /* "memlat" */
> > +#define INVALID_IDX 0xFF
> > +#define MAX_NAME_LEN 20
> > +#define MAX_MAP_ENTRIES 6
> > +#define MAX_MONITOR_CNT 4
> > +#define SCMI_VENDOR_MSG_START 3
> > +#define SCMI_VENDOR_MSG_MODULE_START 16
> > +
> > +enum scmi_memlat_protocol_cmd {
> > + MEMLAT_SET_LOG_LEVEL = SCMI_VENDOR_MSG_START,
> > + MEMLAT_FLUSH_LOGBUF,
> > + MEMLAT_SET_MEM_GROUP = SCMI_VENDOR_MSG_MODULE_START,
> > + MEMLAT_SET_MONITOR,
> > + MEMLAT_SET_COMMON_EV_MAP,
> > + MEMLAT_SET_GRP_EV_MAP,
> > + MEMLAT_ADAPTIVE_LOW_FREQ,
> > + MEMLAT_ADAPTIVE_HIGH_FREQ,
> > + MEMLAT_GET_ADAPTIVE_CUR_FREQ,
> > + MEMLAT_IPM_CEIL,
> > + MEMLAT_FE_STALL_FLOOR,
> > + MEMLAT_BE_STALL_FLOOR,
> > + MEMLAT_WB_PCT,
> > + MEMLAT_IPM_FILTER,
> > + MEMLAT_FREQ_SCALE_PCT,
> > + MEMLAT_FREQ_SCALE_CEIL_MHZ,
> > + MEMLAT_FREQ_SCALE_FLOOR_MHZ,
> > + MEMLAT_SAMPLE_MS,
> > + MEMLAT_MON_FREQ_MAP,
> > + MEMLAT_SET_MIN_FREQ,
> > + MEMLAT_SET_MAX_FREQ,
> > + MEMLAT_GET_CUR_FREQ,
> > + MEMLAT_START_TIMER,
> > + MEMLAT_STOP_TIMER,
> > + MEMLAT_GET_TIMESTAMP,
> > + MEMLAT_MAX_MSG
> > +};
>
> So the reason why you can have just a single qualcomm vendor SCMI protocol is
> that it really implements and expose just a couple of set/get generic commands
> and exposes a few related ops so that you can piggyback any kind of real messages
> into this new sort of transport layer and at the end the full final message payloads
> are built here in the client driver...and any future further QC SCMI client driver
> will implement its own set of payloads for different protocols.
>
> Seems a bit odd to me (but certainly a creative way to abuse the SCMI stack), anyway
> I have personally nothing against it, if you are happy with this design, but the spec
> says that the protocol messages have to be little endian-encoded so I suppose that you
> should, down below, define your smuggled (:P) payloads with __le32 & friends and use
> the proper helpers to be sure that the values tranferred are properly interpreted, from
> the endianess point-of-view, on both sides of the channel.
>
> ...but Sudeep could think differently...I would wait for his feedback...
No not really. I agree. I have more fundamental question which I expected to
find some reasoning somewhere. It could be me not having followed the patches
properly, but
1. Why this bus/memlat dvfs can't be done using perf protocol ?
2. What std perf protocol lacks that is needed here ?
3. Why it needs to be vendor specific ?
4. If so, why MEMLAT alone doesn't deserve a separate vendor protocol ?
IOW why is vendor protocol is implemented as more generic one for all
qcom needs(I am assuming here) and MEMLAT is just command extension
of that protocol(as Cristian said protocol on top of the generic qcom
vendor protocol)
These are few details that helps to understand and review the patches. So
please add as much as documentation. If it is too much, we can remove it
(but I am sure we may not reach that point).
--
Regards,
Sudeep
Powered by blists - more mailing lists