Hi,
I can't make February 22nd next week for LOD, I would kindly
ask you please to reschedule the call from Feb 23rd onwards.
I don't have any major update either, other than IORT
specs as already mentioned on the mailing list.
Thank you,
Lorenzo
Hi,
OP-TEE Contributions (LOC) monthly meeting is planned for Thursday Jan 27
@16.00 (UTC).
If you have any topics you'd like to discuss, please let us know and we can
schedule them.
Meeting details:
---------------
Date/time: January 27(a)16.00 (UTC)
https://everytimezone.com/s/c3460919
Connection details: https://www.trustedfirmware.org/meetings/
Meeting notes: http://bit.ly/loc-notes
Regards,
Ruchika on behalf of the Linaro OP-TEE team
Hi Lorenzo,
Starting a new thread as your previous reply disappeared somewhere deep in my
email due to threading.
> I would like to ask two things:
>
> - IORT: with new spec published, I believe Shameer should be able to
> bring the RMR work to completion. We can have a quick chat about this.
Shameer is keen to discuss this as well.
> - Virt CPU hotplug: we should split the work - ie who is preparing and
> posting kernel patches ?
Salil is currently on leave but we can talk about the general approach /
division of labor.
I did a forward port of the QEMU side of things before Xmas but got distracted
so haven't tested it yet.
>
> Please let me know if we can sync this month.
One other topic request from us is for any updates on MPAM plan and
if there is anything we can do to assist on that.
Great to hear you had some success with the DOE/SPDM stuff.
I've been head down in getting upstreamable CXL/qemu support sorted
out so not looked at that stuff yet this year.
Joyce, please could you organize for a Linaro Open Discussions call?
Personally Tuesday / Thursday / Friday (UK time) mornings next week would work well, but
we might need a poll to find a slot that works for everyone.
Thanks,
Jonathan
For sharing with Lorenzo.
I'm holding off on posting the CMA patches until the open question around
DOE / auxiliary bus is resolved. Not clear if we'll end up back where we
started.
Note that other than the devm_ fix patch I've not tweaked the DOE series
for review comments.
Base is cxl/next 53989fad1286e652ea3655ae3367ba698da8d2ff
(the tree might have moved again in the meantime)
Ira Weiny (1):
cxl/cdat: Parse out DSMAS data from CDAT table
Jonathan Cameron (9):
PCI: Add vendor ID for the PCI SIG
PCI/DOE: Add Data Object Exchange Aux Driver
cxl/pci: Add DOE Auxiliary Devices
cxl/mem: Add CDAT table reading from DOE
lib/asn1_encoder: Add a function to encode many byte integer values.
spdm: Introduce a library for DMTF SPDM
PCI/CMA: Initial support for Component Measurement and Authentication
ECN
cxl/pci: Add really basic CMA authentication support.
cxl: Fixes for wrong device in devm_ calls.
drivers/cxl/Kconfig | 2 +
drivers/cxl/cdat.h | 81 +++
drivers/cxl/core/memdev.c | 157 +++++
drivers/cxl/cxl.h | 10 +
drivers/cxl/cxlmem.h | 50 ++
drivers/cxl/pci.c | 231 ++++++-
drivers/pci/Kconfig | 19 +
drivers/pci/Makefile | 5 +
drivers/pci/cma.c | 105 +++
drivers/pci/doe.c | 701 +++++++++++++++++++
include/linux/asn1_encoder.h | 3 +
include/linux/pci-cma.h | 19 +
include/linux/pci-doe.h | 63 ++
include/linux/pci_ids.h | 1 +
include/linux/spdm.h | 104 +++
include/uapi/linux/pci_regs.h | 29 +-
lib/Kconfig | 3 +
lib/Makefile | 2 +
lib/asn1_encoder.c | 54 ++
lib/spdm.c | 1196 +++++++++++++++++++++++++++++++++
20 files changed, 2833 insertions(+), 2 deletions(-)
create mode 100644 drivers/cxl/cdat.h
create mode 100644 drivers/pci/cma.c
create mode 100644 drivers/pci/doe.c
create mode 100644 include/linux/pci-cma.h
create mode 100644 include/linux/pci-doe.h
create mode 100644 include/linux/spdm.h
create mode 100644 lib/spdm.c
--
2.32.0
Hi,
In light of the holiday season we are not expecting too many joiners on Dec
23. Hence, let's cancel the LOC (Linaro OP-TEE Contribution) monthly
meeting scheduled for next week.
Wish you all a great holiday and a happy new year. The next scheduled
meeting will be on 27th January 2022.
Regards,
Ruchika
(On behalf of OP-TEE team)
Hi all,
This email intends to ask for potential interest in extending the
support for the SCMI perf-domain protocol in the Linux kernel and in
the firmware. Please, feel free to ignore this, while a short answer
like "sounds interesting" would be sufficient information at this
point. Some more details below.
Today, the current support in the Linux kernel for the SCMI
perf-domain protocol, is limited to be used for CPU frequency scaling,
through the cpufreq subsystem. However, the SCMI perf-domain protocol
isn't really limited to CPUs, but fits well for other generic
peripheral devices too. By extending the support, we can avoid the
need for SoC specific protocols/interfaces, while scaling performance
for non-CPU devices.
>From the Linux kernel point of view, we already have generic support
for DVFS (Dynamic Voltage Frequency Scaling), through a mixture of
subsystems/libraries. Without going into details, we should be able to
tap into these existing infrastructures, to add support for the SCMI
perf-protocol. In this way, the support would be generic and nicely
abstracted from lower layer drivers/subsystems.
Thoughts?
Kind regards
Ulf Hansson, Linaro Kernel Team
This is the follow-up work to support cluster scheduler. Previously
we have added cluster level in the scheduler[1] to make tasks spread
between clusters to bring more memory bandwidth and decrease
cache contention. But it may hurt some workloads which are sensitive
to the communication latency as they will be placed across clusters.
We modified the select_idle_cpu() on the wake affine path in this
series, expecting the wake affined task to be woken more likely on
the same cluster with the waker. The latency will be decreased as
the waker and wakee in the same cluster may benefit from the hot
L3 cache tag.
[1]
https://lore.kernel.org/lkml/20210924085104.44806-1-21cnbao@gmail.com/
Hi Tim and Barry,
This the modified patch of packing path of cluster scheduler and tests
have been done on Kunpeng 920 2-socket 4-NUMA 128core platform, with
8 clusters on each NUMA. Patches based on 5.16-rc1.
Compared to the previous one[2], we give up scanning the first cpu of the
cluster as the cpu id may not be continuous. So we pickup the way of
scanning cluster first before LLC. The result from tbench and pgbench
are rather positive.
[2]
https://op-lists.linaro.org/pipermail/linaro-open-discussions/2021-October/…
Barry Song (2):
sched: Add per_cpu cluster domain info
sched/fair: Scan cluster before scanning LLC in wake-up path
include/linux/sched/sd_flags.h | 9 ++++++++
include/linux/sched/topology.h | 2 +-
kernel/sched/fair.c | 41 +++++++++++++++++++++++++++++++++-
kernel/sched/sched.h | 1 +
kernel/sched/topology.c | 5 +++++
5 files changed, 56 insertions(+), 2 deletions(-)
--
2.33.0