Hi, Thorsten here, the Linux kernel's regression tracker.
Frederic, I noticed a report about a regression in bugzilla.kernel.org
that appears to be caused by the following change of yours:
55d4669ef1b768 ("rcu: Fix rcu_barrier() VS post CPUHP_TEARDOWN_CPU
invocation")
As many (most?) kernel deve
[reply to self to CC the tg3 maintainers, netdev, and linux-wireless;
sorry, forgot them earlier, but they should be involved, as I guess this
is a problem in tg3 interfering with wifi drivers that the rcu change
just exposed]
On 23.10.24 10:27, Linux regression tracking (Thorsten Leemhuis) wrote:
Hi Thorsten,
First, thanks for letting us know.
Le Wed, Oct 23, 2024 at 10:27:18AM +0200, Linux regression tracking (Thorsten
Leemhuis) a écrit :
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> Frederic, I noticed a report about a regression in bugzilla.kernel.org
> that appears
Le Wed, Oct 23, 2024 at 08:30:14AM +0200, Sebastian Andrzej Siewior a écrit :
> On 2024-10-23 00:27:34 [+0200], Frederic Weisbecker wrote:
> > > Try again without the "ksoftirqd will collect it all" since this won't
> > > happen since the revert I mentioned.
> >
> > I still don't get it, this make
On 23.10.24 12:09, Frederic Weisbecker wrote:
> Le Wed, Oct 23, 2024 at 10:27:18AM +0200, Linux regression tracking (Thorsten
> Leemhuis) a écrit :
>> Hi, Thorsten here, the Linux kernel's regression tracker.
>>
>> Frederic, I noticed a report about a regression in bugzilla.kernel.org
>> that appe
Fix incompatible function pointer type warnings in sched_ext BPF selftests by
explicitly casting the function pointers when initializing struct_ops.
This addresses multiple -Wincompatible-function-pointer-types warnings from the
clang compiler where function signatures didn't match exactly.
The vo
On 2024-10-23 08:30:18 [+0200], To Frederic Weisbecker wrote:
> > > > > +void raise_timer_softirq(void)
> > > > > +{
> > > > > + unsigned long flags;
> > > > > +
> > > > > + local_irq_save(flags);
> > > > > + raise_ktimers_thread(TIMER_SOFTIRQ);
> > > > > + wake_timersd();
> > > >
On Oct 22, 2024, at 22:26, Paul E. McKenney wrote:
>
> On Tue, Oct 22, 2024 at 12:13:12AM -0700, Christoph Hellwig wrote:
>> On Tue, Oct 22, 2024 at 09:10:18AM +0200, Peter Zijlstra wrote:
>>> Ah, well, the thing that got us here is that we (Andrii and me) wanted
>>> to use -1 as an 'invalid' val
On Tue, Oct 22, 2024 at 05:53:00PM -0700, Shakeel Butt wrote:
> On Thu, Oct 17, 2024 at 10:05:50PM GMT, Lorenzo Stoakes wrote:
> > It is useful to be able to utilise the pidfd mechanism to reference the
> > current thread or process (from a userland point of view - thread group
> > leader from the
On Thu, Sep 05, 2024 at 03:01:19PM -0300, Jason Gunthorpe wrote:
> On Tue, Aug 27, 2024 at 10:02:06AM -0700, Nicolin Chen wrote:
> > The iommufd core provides a lookup helper for an IOMMU driver to find a
> > device pointer by device's per-viommu virtual ID. Yet a driver may need
> > an inverted lo
On Wed, 23 Oct 2024 00:20:45 +0100, Mark Brown wrote:
> Currently if we encounter an error between fork() and exec() of a child
> process we log the error to stderr. This means that the errors don't get
> annotated with the child information which makes diagnostics harder and
> means that if we mis
Hi Yuanchu,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.12-rc4 next-20241023]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Mon, Oct 21, 2024 at 12:25:26PM +0200, Matthieu Baerts (NGI0) wrote:
> Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT
> creates this splat when an MPTCP socket is created:
>
> =
> WARNING: suspicious RCU usage
> 6.12.0-rc2+ #11 Not tainted
On Mon, Oct 21, 2024 at 12:25:28PM +0200, Matthieu Baerts (NGI0) wrote:
> Listing all the values linked to the MPTCP sysctl knobs was not
> exercised in MPTCP test suite.
>
> Let's do that to avoid any regressions, but also to have a kernel with a
> debug kconfig verifying more assumptions. For th
On Mon, Oct 21, 2024 at 12:25:27PM +0200, Matthieu Baerts (NGI0) wrote:
> mptcp_get_available_schedulers() needs to iterate over the schedulers'
> list only to read the names: it doesn't modify anything there.
>
> In this case, it is enough to hold the RCU read lock, no need to combine
> this with
Hello Daniel,
On Fri, Oct 18, 2024 at 02:09:29PM +0300, Daniel Baluta wrote:
> Currently we generate notifyids in the linux kernel and override
> those found in rsc_table.
>
> This doesn't play well with users expecting to use the exact ids
> from rsc_table.
>
> So, use predefined notifyids foun
That should make it possible to do expected payload validation on
the caller side.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 61 +-
1 file changed, 30 insertions(+), 31 deletions(-)
diff --git a/tools/testin
So we can plug the other ones in the future if needed.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 198 +++--
1 file changed, 117 insertions(+), 81 deletions(-)
diff --git a/tools/testing/selftests/net/ncdevmem.c
There is a bunch of places where error() calls look out of place.
Use the same error(1, errno, ...) pattern everywhere.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
Kunit tests to test hash table add, delete, duplicate add and delete.
Add following configs and compile kernel code:
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_NET=y
CONFIG_KUNIT=m
CONFIG_CN_HASH_KUNIT_TEST=m
To run kunit tests:
sudo modprobe cn_hash_test
Output of kunit tests and hash table
From: Laurentiu Mihalcea
Add imx95 DTS for SOF usage.
Signed-off-by: Laurentiu Mihalcea
---
arch/arm64/boot/dts/freescale/Makefile| 1 +
.../dts/freescale/imx95-19x19-evk-sof.dts | 86 +++
2 files changed, 87 insertions(+)
create mode 100644 arch/arm64/boot/dts/fr
From: Laurentiu Mihalcea
Add SOF driver for imx95.
Signed-off-by: Laurentiu Mihalcea
---
sound/soc/sof/imx/Kconfig | 8 +
sound/soc/sof/imx/Makefile | 2 +
sound/soc/sof/imx/imx95.c | 383 +
3 files changed, 393 insertions(+)
create mode 100644 sound/
From: Laurentiu Mihalcea
Introduce the 'widgets' property, allowing the creation of widgets from
4 template widgets: Microphone, Line, Headphone, and Speaker. Also
introduce the 'hp-det-gpios' property, which allows using headphone
detection using the specified GPIO.
Signed-off-by: Laurentiu Mih
From: Laurentiu Mihalcea
Add sof support on imx95. This series also includes some changes to
the audio-graph-card2 binding required for the support.
Laurentiu Mihalcea (4):
dt-bindings: remoteproc: fsl,imx-rproc: add new compatible
ASoC: dt-bindings: audio-graph-card2: add widgets and hp-det
On Tue, Oct 22, 2024 at 11:40 PM Christoph Hellwig wrote:
>
> On Tue, Oct 22, 2024 at 10:29:13AM -0700, Andrii Nakryiko wrote:
> > >
> > > Would this work?
> > >
> > > #define SRCU_INVALID_INDEX -1
> > >
> >
> > But why?
>
> Becaue it very clearly documents what is going on.
So does saying "retur
What's more, I have open a pull request of the user space tool kpatch[1]
to use this new kernel sysfs attribute 'stack_order'.
Maintainers who feel interesting in this function can come for a look.
Best Regards.
Wardenjohn.
[1]: https://github.com/dynup/kpatch/pull/1419
On 10/23, Anjali Kulkarni wrote:
> […snip…]
>
>
> Yes, make sure all required options are picked up by
> "./tools/testing/kunit/kunit.py run" instead of manually adding options
> and doing modprobe.
> >>>
> >>> The environment issues are resolved and I am able to run kunit.py
Le Tue, Oct 22, 2024 at 12:53:07PM +0200, Uladzislau Rezki (Sony) a écrit :
> KCSAN reports a data race when access the krcp->monitor_work.timer.expires
> variable in the schedule_delayed_monitor_work() function:
>
>
> BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu
>
> read to 0x8882
> On Oct 23, 2024, at 8:05 AM, Stanislav Fomichev wrote:
>
> On 10/23, Anjali Kulkarni wrote:
>> […snip…]
>>
>>
>> Yes, make sure all required options are picked up by
>> "./tools/testing/kunit/kunit.py run" instead of manually adding options
>> and doing modprobe.
>
Add a new type PROC_CN_MCAST_NOTIFY to proc connector API, which allows a
thread to notify the kernel that is going to exit with a non-zero exit
code and specify the exit code in it. When thread exits in the kernel,
it will send this exit code as a proc filter notification to any
listening process.
Recently we committed a fix to allow processes to receive notifications for
non-zero exits via the process connector module. Commit is a4c9a56e6a2c.
However, for threads, when it does a pthread_exit(&exit_status) call, the
kernel is not aware of the exit status with which pthread_exit is called.
I
Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows
a thread's non-zero exit status to be returned to proc_filter.
The threads.c program creates 2 child threads. 1st thread handles signal
SIGSEGV, and 2nd thread needs to indicate some error condition (value 1)
to the kernel
Support 3-tuple filtering by making client_ip optional. When -c is
not passed, don't specify src-ip/src-port in the filter.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
From: Eduard Zingerman
[ Upstream commit a41b3828ec056a631ad22413d4560017fed5c3bd ]
This test was added because of a bug in verifier.c:sync_linked_regs(),
upon range propagation it destroyed subreg_def marks for registers.
The test is written in a way to return an upper half of a register
that i
On Wed, Oct 23, 2024 at 08:18:35AM GMT, Lorenzo Stoakes wrote:
> On Tue, Oct 22, 2024 at 05:53:00PM -0700, Shakeel Butt wrote:
> > On Thu, Oct 17, 2024 at 10:05:50PM GMT, Lorenzo Stoakes wrote:
> > > It is useful to be able to utilise the pidfd mechanism to reference the
> > > current thread or pro
Only RX side for now and small message to test the setup.
In the future, we can extend it to TX side and to testing
both sides with a couple of megs of data.
make \
-C tools/testing/selftests \
TARGETS="drivers/hw/net" \
install INSTALL_PATH=~/tmp/ksft
scp ~/tmp/ksft $
Some versions of the pmic_glink firmware does not allow dynamic GLINK
intent allocations, attempting to send a message before the firmware has
allocated its receive buffers and announced these intent allocations
will fail. When this happens something like this showns up in the log:
pmic_glink_
GLINK operates using pre-allocated buffers, aka intents, where incoming
messages are aggregated before being passed up the stack. In the case
that no suitable intents have been announced by the receiver, the sender
can request an intent to be allocated.
The initial implementation of the response t
On Mon, Oct 21, 2024 at 10:46:44AM -0700, Leo Stone wrote:
> Add tests that check if getsockopt(TCP_AO_GET_KEYS) returns the right
> keys when using different filters.
>
> Sample output:
>
> > # ok 114 filter keys: by sndid, rcvid, address
> > # ok 115 filter keys: by is_current
> > # ok 116 filt
From: Tyrone Wu
[ Upstream commit b836cbdf3b81a4a22b3452186efa2e5105a77e10 ]
Add assertions in `bpf_link_info.uprobe_multi` test to verify that
`count` and `path_size` fields are correctly populated when the fields
are unset.
This tests a previous bug where the `path_size` field was not populat
On 10/21/24 12:33, Luis Chamberlain wrote:
...
> +gen_template_module_exit()
> +{
> + cat < +static int __init auto_test_module_init(void)
> +{
> + return auto_runtime_test();
> +}
> +module_init(auto_test_module_init);
> +
> +static void __exit auto_test_module_exit(void)
Hi,
On Tue, Oct 22, 2024 at 7:39 AM Petr Pavlu wrote:
>
> On 10/8/24 20:38, Sami Tolvanen wrote:
> > +/*
> > + * KABI_USE_ARRAY(fqn)
> > + * Treat the struct fqn as a declaration, i.e. even if a definition
> > + * is available, don't expand the contents.
> > + */
> > +#define KABI_STRUCT_DECL
On Fri 2024-10-11 23:11:51, Wardenjohn wrote:
> Add selftest test cases to sysfs attribute 'stack_order'.
>
> Signed-off-by: Wardenjohn
> ---
> .../testing/selftests/livepatch/test-sysfs.sh | 74 +++
> 1 file changed, 74 insertions(+)
>
> diff --git a/tools/testing/selftests/liv
On 10/8/24 20:38, Sami Tolvanen wrote:
> The compiler may choose not to emit type information in DWARF for
> external symbols. Clang, for example, does this for symbols not
> defined in the current TU.
>
> To provide a way to work around this issue, add support for
> __gendwarfksyms_ptr_ pointers
On 10/8/24 20:38, Sami Tolvanen wrote:
> When MODVERSIONS is enabled, allow selecting gendwarfksyms as the
> implementation, but default to genksyms.
>
> Signed-off-by: Sami Tolvanen
> Acked-by: Neal Gompa
> ---
> kernel/module/Kconfig | 25 -
> scripts/Makefile |
This will be used as a 'probe' mode in the selftest to check whether
the device supports the devmem or not. Use hard-coded queue layout
(two last queues) and prevent user from passing custom -q and/or -t.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/ne
Use single last queue of the device and probe it dynamically.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 40 --
1 file changed, 38 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/net/ncdevm
This is where all the tests that depend on the HW functionality live in
and this is where the automated test is gonna be added in the next
patch.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/drivers/net/hw/.gitignore | 1 +
tools/testing/selfte
ntuple off/on might be not enough to do it on all NICs.
Add a bunch of shell crap to explicitly remove the rules.
Reviewed-by: Mina Almasry
Signed-off-by: Stanislav Fomichev
---
tools/testing/selftests/net/ncdevmem.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
di
The goal of the series is to simplify and make it possible to use
ncdevmem in an automated way from the ksft python wrapper.
ncdevmem is slowly mutated into a state where it uses stdout
to print the payload and the python wrapper is added to
make sure the arrived payload matches the expected one.
To make it clear what's required and what's not. Also, some of the
values don't seem like a good defaults; for example eth1.
Move the invocation comment to the top, add missing -s to the client
and cleanup the client invocation a bit to make more readable.
Reviewed-by: Mina Almasry
Signed-off-by
Hi, Petr.
> On Oct 23, 2024, at 20:38, Petr Mladek wrote:
>
> Please, try to send the next version together with the patch adding
> the "stack_order" attribute.
>
Do you mean I should resend the patch of "livepatch: Add stack_order sysfs
attribute" again with this "livepatch selftest" patch?
From: Eduard Zingerman
[ Upstream commit a41b3828ec056a631ad22413d4560017fed5c3bd ]
This test was added because of a bug in verifier.c:sync_linked_regs(),
upon range propagation it destroyed subreg_def marks for registers.
The test is written in a way to return an upper half of a register
that i
On 10/8/24 20:38, Sami Tolvanen wrote:
> Distributions that want to maintain a stable kABI need the ability
> to make ABI compatible changes to kernel data structures without
> affecting symbol versions, either because of LTS updates or backports.
>
> With genksyms, developers would typically hide
On Wed, Oct 23, 2024 at 12:21:11PM -0400, Laurentiu Mihalcea wrote:
> From: Laurentiu Mihalcea
>
> Add new compatible for imx95's CM7 with SOF.
It is not only add compatible string, but also change reg, reg-names ...
Please add descripts in commit message about these.
>
> Signed-off-by: Laurent
Hi,
= START =
TEST: enq_last_no_enq_fails
DESCRIPTION: Verify we fail to load a scheduler if we specify the
SCX_OPS_ENQ_LAST flag without defining ops.enqueue()
OUTPUT:
ERR: enq_last_no_enq_fails.c:35
Incorrectly succeeded in to attaching scheduler
not ok 2 enq_last_no_enq_fails #
=
On 23/10/24 01:30, Sean Christopherson wrote:
> On Tue, Oct 22, 2024, Adrian Hunter wrote:
>> On 22/10/24 19:30, Sean Christopherson wrote:
> LOL, yeah, this needs to be burned with fire. It's wildly broken. So
> for stable@,
It doesn't seem wildly broken. Just the VMM passing
On Wed, Oct 23, 2024 at 02:58:07PM +0800, Alan Huang wrote:
> On Oct 22, 2024, at 22:26, Paul E. McKenney wrote:
> >
> > On Tue, Oct 22, 2024 at 12:13:12AM -0700, Christoph Hellwig wrote:
> >> On Tue, Oct 22, 2024 at 09:10:18AM +0200, Peter Zijlstra wrote:
> >>> Ah, well, the thing that got us he
Hi Petr,
On Tue, Oct 22, 2024 at 4:48 AM Petr Pavlu wrote:
>
> I had some minor comment about adjusting the name of function
> symbol_print_versions() and possibly changing sym->name to 'char *' on
> the v2 of the patch:
> https://lore.kernel.org/all/286b1cc5-1757-4f0a-bb66-0875f4608...@suse.com/
Hi Simon,
Thank you for the reviews!
On 23/10/2024 14:21, Simon Horman wrote:
> On Mon, Oct 21, 2024 at 12:25:27PM +0200, Matthieu Baerts (NGI0) wrote:
>> mptcp_get_available_schedulers() needs to iterate over the schedulers'
>> list only to read the names: it doesn't modify anything there.
>>
>>
On Oct 24, 2024, at 00:34, Andrii Nakryiko wrote:
>
> On Tue, Oct 22, 2024 at 11:40 PM Christoph Hellwig wrote:
>>
>> On Tue, Oct 22, 2024 at 10:29:13AM -0700, Andrii Nakryiko wrote:
Would this work?
#define SRCU_INVALID_INDEX -1
>>>
>>> But why?
>>
>> Becaue it ve
On Wed, Oct 23, 2024 at 12:22:15AM -0700, Nicolin Chen wrote:
> On Thu, Sep 05, 2024 at 03:01:19PM -0300, Jason Gunthorpe wrote:
> > On Tue, Aug 27, 2024 at 10:02:06AM -0700, Nicolin Chen wrote:
> > > The iommufd core provides a lookup helper for an IOMMU driver to find a
> > > device pointer by de
On Wed, Oct 23, 2024 at 10:18:28AM -0700, Shakeel Butt wrote:
> On Wed, Oct 23, 2024 at 08:18:35AM GMT, Lorenzo Stoakes wrote:
> > On Tue, Oct 22, 2024 at 05:53:00PM -0700, Shakeel Butt wrote:
> > > On Thu, Oct 17, 2024 at 10:05:50PM GMT, Lorenzo Stoakes wrote:
> > > > It is useful to be able to ut
Hi
> > From: Laurentiu Mihalcea
> >
> > Introduce the 'widgets' property, allowing the creation of widgets from
> > 4 template widgets: Microphone, Line, Headphone, and Speaker. Also
> > introduce the 'hp-det-gpios' property, which allows using headphone
> > detection using the specified GPIO.
From: Laurentiu Mihalcea
Add new compatible for imx95's CM7 with SOF.
Signed-off-by: Laurentiu Mihalcea
---
.../bindings/remoteproc/fsl,imx-rproc.yaml| 58 +--
1 file changed, 53 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,im
On Oct 24, 2024, at 00:40, Paul E. McKenney wrote:
>
> On Wed, Oct 23, 2024 at 02:58:07PM +0800, Alan Huang wrote:
>> On Oct 22, 2024, at 22:26, Paul E. McKenney wrote:
>>>
>>> On Tue, Oct 22, 2024 at 12:13:12AM -0700, Christoph Hellwig wrote:
On Tue, Oct 22, 2024 at 09:10:18AM +0200, Pete
On 10/23/2024 10:24 AM, Bjorn Andersson wrote:
Some versions of the pmic_glink firmware does not allow dynamic GLINK
intent allocations, attempting to send a message before the firmware has
allocated its receive buffers and announced these intent allocations
will fail. When this happens someth
On 10/23/2024 10:24 AM, Bjorn Andersson wrote:
GLINK operates using pre-allocated buffers, aka intents, where incoming
messages are aggregated before being passed up the stack. In the case
that no suitable intents have been announced by the receiver, the sender
can request an intent to be allo
On Wed, Oct 23, 2024 at 12:21:12PM -0400, Laurentiu Mihalcea wrote:
> From: Laurentiu Mihalcea
>
> Introduce the 'widgets' property, allowing the creation of widgets from
> 4 template widgets: Microphone, Line, Headphone, and Speaker. Also
> introduce the 'hp-det-gpios' property, which allows usin
Hello,
On Wed, Oct 23, 2024 at 10:13:19PM +0530, Vishal Chourasia wrote:
...
> static int scx_ops_enable(struct sched_ext_ops *ops, struct bpf_link *link)
> {
> ...
> ret = validate_ops(ops);
> if (ret)
> goto err_disable;
> ...
> err_disable:
> mut
The irritator handlers for the fp-stress test programs all use ADR to load
an address into x0 which is then not referenced. Remove these ADRs as they
just cause confusion.
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/fp/fpsimd-test.S | 1 -
tools/testing/selftests/arm64/fp/sve-tes
| 6 ++
tools/testing/selftests/arm64/fp/za-test.S | 13 -
tools/testing/selftests/arm64/fp/zt-test.S | 13 -
6 files changed, 16 insertions(+), 26 deletions(-)
---
base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354
change-id: 20241023-arm64-fp-stress-irri
Currently in fp-stress we test signal delivery to the test threads by
sending SIGUSR2 which simply counts how many signals are delivered. The
test programs now also all have a SIGUSR1 handler which for the threads
doing userspace testing additionally modifies the floating point register
state in th
The other stress test programs provide a SIGUSR1 handler which modifies the
live register state in order to validate that signal context is being
restored during signal return. While we can't usefully do this when testing
kernel mode FP usage provide a handler for SIGUSR1 which just counts the
numb
When building for streaming SVE the irritator for SVE skips updates of both
P15 and FFR. While FFR is skipped since it might not be present there is no
reason to skip corrupting P15 so move the ifdef appropriately.
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/fp/sve-test.S | 2 +-
Currently we don't use the irritator signal in our floating point stress
tests so when we added ZA and ZT stress tests we didn't actually bother
implementing any actual action in the handlers, we just counted the signal
deliveries. In preparation for using the irritators let's implement them,
just
On Wed, Oct 23, 2024 at 01:59:05PM -0300, Jason Gunthorpe wrote:
> > [Comparison] | This v1 | Draft
> > 1. Adds to master | A lock and vdev ptr | A lock and viommu ptr
> > 2. Set/unset ptr | In ->vdevice_alloc/free | In all ->attach_dev
> > 3. Do dev_to_vdev | master->vdev
On Wed, Oct 23, 2024 at 12:21:13PM -0400, Laurentiu Mihalcea wrote:
> From: Laurentiu Mihalcea
>
> Add SOF driver for imx95.
>
> Signed-off-by: Laurentiu Mihalcea
> ---
> sound/soc/sof/imx/Kconfig | 8 +
> sound/soc/sof/imx/Makefile | 2 +
> sound/soc/sof/imx/imx95.c | 383
On 10/22/24 10:01, Alexandre Belloni wrote:
On 20/10/2024 20:22:13-0700, Joseph Jang wrote:
In alarm_wkalm_set and alarm_wkalm_set_minute test, they use different
ioctl (RTC_ALM_SET/RTC_WKALM_SET) for alarm feature detection. They will
skip testing if RTC_ALM_SET/RTC_WKALM_SET ioctl returns an E
On Wed, Oct 23, 2024 at 12:21:14PM -0400, Laurentiu Mihalcea wrote:
> From: Laurentiu Mihalcea
>
> Add imx95 DTS for SOF usage.
>
> Signed-off-by: Laurentiu Mihalcea
> ---
> arch/arm64/boot/dts/freescale/Makefile| 1 +
> .../dts/freescale/imx95-19x19-evk-sof.dts | 86 +++
In the next patch the hard-coded queue numbers are gonna be removed.
So introduce some initial support for ethtool YNL and use
it to enable header split.
Also, tcp-data-split requires latest ethtool which is unlikely
to be present in the distros right now.
(ideally, we should not shell out to eth
Hi Yuanchu,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.12-rc4 next-20241023]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Wed, Oct 23, 2024 at 02:15:00PM +0530, Vishal Chourasia wrote:
> Fix incompatible function pointer type warnings in sched_ext BPF selftests by
> explicitly casting the function pointers when initializing struct_ops.
> This addresses multiple -Wincompatible-function-pointer-types warnings from
>
With the transition of pd-mapper into the kernel, the timing was altered
such that on some targets the initial rpmsg_send() requests from
pmic_glink clients would be attempted before the firmware had announced
intents, and the firmware reject intent requests.
Fix this
Signed-off-by: Bjorn Anderss
Hi,
On Wed, Oct 23, 2024 at 2:59 PM Petr Pavlu wrote:
>
> On 10/8/24 20:38, Sami Tolvanen wrote:
> > +gendwarfksyms := scripts/gendwarfksyms/gendwarfksyms
> > +getexportsymbols = $(NM) $(1) | sed -n 's/.* __export_symbol_\(.*\)/$(2)/p'
> > +
> > genksyms = scripts/genksyms/genksyms \
> >
The comments in the handlers for the irritator signal in the test threads
for fp-stress suggest that the irritator will corrupt the register state
observed by the main thread but this is not the case, instead the FPSIMD
and SVE irritators (which are the only ones that are implemented) modify
the cu
This happens on 64-bit big-endian machines.
SO_RCVLOWAT requires an int parameter. However, instead of int, the test
uses unsigned long in one place and size_t in another. Both are 8 bytes
long on 64-bit machines. The kernel, having received the 8 bytes, doesn't
test for the exact size of the param
On Wed, Oct 23, 2024 at 2:53 PM Petr Pavlu wrote:
>
> I've noted some nits above which you might want to trivially address.
These all looked reasonable to me, I'll address them in the next version.
> Otherwise this looks ok to me, feel free to add:
>
> Reviewed-by: Petr Pavlu
Thanks!
Sami
On Tue, Oct 22, 2024 at 05:30:55PM GMT, Johan Hovold wrote:
> On Tue, Oct 22, 2024 at 04:17:12AM +, Bjorn Andersson wrote:
[..]
> > Reported-by: Johan Hovold
> > Closes: https://lore.kernel.org/all/zqet8iinndhnx...@hovoldconsulting.com/#t
>
> This indeed seems to fix the -ECANCELED related er
On Wed, Oct 23, 2024 at 9:46 AM Alan Huang wrote:
>
> On Oct 24, 2024, at 00:34, Andrii Nakryiko wrote:
> >
> > On Tue, Oct 22, 2024 at 11:40 PM Christoph Hellwig
> > wrote:
> >>
> >> On Tue, Oct 22, 2024 at 10:29:13AM -0700, Andrii Nakryiko wrote:
>
> Would this work?
>
> #
Add "stack_order" sysfs attribute which holds the order in which a live
patch module was loaded into the system. A user can then determine an
active live patched version of a function.
cat /sys/kernel/livepatch/livepatch_1/stack_order -> 1
means that livepatch_1 is the first live patch applied
c
Fix incompatible function pointer type warnings in sched_ext BPF selftests by
explicitly casting the function pointers when initializing struct_ops.
This addresses multiple -Wincompatible-function-pointer-types warnings from the
clang compiler where function signatures didn't match exactly.
The vo
On Wed, Oct 23, 2024 at 05:24:33PM +, Bjorn Andersson wrote:
> Some versions of the pmic_glink firmware does not allow dynamic GLINK
> intent allocations, attempting to send a message before the firmware has
> allocated its receive buffers and announced these intent allocations
> will fail.
>
93 matches
Mail list logo
