On Sat, 2024-12-14 at 00:10 +0100, Kumar Kartikeya Dwivedi wrote:
[...]
> > @@ -11199,10 +11266,17 @@ static int check_helper_call(struct
> > bpf_verifier_env *env, struct bpf_insn *insn
> > "kernel subsystem misconfigured
> > verifier\n");
> >
On Fri, 2024-12-13 at 15:14 -0800, Eduard Zingerman wrote:
[...]
> Great point, I'm sure this does not happen.
I mean, mark_chain_precision() does not happen at the moment.
Le Fri, Dec 13, 2024 at 08:33:45PM +, Usama Arif a écrit :
> The following warning is being encountered at boot time:
>
>WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086
> hrtimer_start_range_ns+0x289/0x2d0
>Modules linked in:
>CPU: 94 UID: 0 PID: 58
On Thu, Dec 12, 2024 at 3:23 PM Daniel Xu wrote:
>
> This commit allows progs to elide a null check on statically known map
> lookup keys. In other words, if the verifier can statically prove that
> the lookup will be in-bounds, allow the prog to drop the null check.
>
> This is useful for two rea
On Sat, Dec 14, 2024 at 12:08:42AM +0100, Frederic Weisbecker wrote:
> Le Thu, Dec 12, 2024 at 10:42:13AM -0800, Paul E. McKenney a écrit :
> > From: Frederic Weisbecker
> >
> > It's more convenient to benefit from the fallthrough feature of
> > switch / case to handle the timer state machine. Al
From: Isaku Yamahata
Annotate the KVM selftests' _no_printf() with the printf format attribute
so that the compiler can help check parameters provided to pr_debug() and
pr_info() irrespective of DEBUG and QUIET being defined.
[reinette: move attribute right after storage class, rework changelog]
Hi Armin,
On 2024-12-13 01:21:37+0100, Armin Wolf wrote:
> Am 05.12.24 um 18:35 schrieb Thomas Weißschuh:
>
> > The generic function from the sysfs core can replace the custom one.
>
> Sorry for taking quite a bit to respond, i totally overlooked this patch.
>
> This patch is superseded by a pa
Hi,
On Wed, Dec 11, 2024 at 04:31:41PM -0800, Brian Norris wrote:
> We recently updated these device_match*() (and therefore, various
> *find_device_by*()) functions to return a consistent 'false' value when
> trying to match a NULL handle. Add tests for this.
>
> This provides regression-testing
On 13/12/2024 11:54, Vladimir Zapolskiy wrote:
New additions should include this bus-type number as we will need it
when we add CPHY support and the subsequently move to the PHY API for
CAMSS PHYs.
This particular reason is invalid IMO, since dtb changes are not relied on
drivers and shall be
On 12/13/24 13:22, Luca Weiss wrote:
On Fri Dec 13, 2024 at 12:02 PM CET, Vladimir Zapolskiy wrote:
On 12/9/24 14:32, Bryan O'Donoghue wrote:
On 09/12/2024 12:01, Luca Weiss wrote:
Currently the Qualcomm CAMSS driver only supports D-PHY while the
hardware on most SoCs also supports C-PHY. Unti
On 12/13/24 13:34, Bryan O'Donoghue wrote:
On 13/12/2024 11:24, Luca Weiss wrote:
On Fri Dec 13, 2024 at 11:50 AM CET, Vladimir Zapolskiy wrote:
On 12/13/24 11:34, Krzysztof Kozlowski wrote:
On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
The CSIPHY of Qualcomm SoCs support both D
On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
> The CSIPHY of Qualcomm SoCs support both D-PHY and C-PHY standards for
> CSI-2, but not any others so restrict the bus-type property describing
> this to the supported values.
>
> The only exception here is MSM8916 which only supports D
Hi all,
v5 here is a small set of fixes and a rebase of the previous versions.
If there are no major issues, I'd like to land this soon so it can be
used and tested ready for 6.14.
This series was originally written by José Expósito, and has been
modified and updated by Matt Gilbride and myself.
From: José Expósito
Add a couple of Rust const functions and macros to allow to develop
KUnit tests without relying on generated C code:
- The `kunit_unsafe_test_suite!` Rust macro is similar to the
`kunit_test_suite` C macro. It requires a NULL-terminated array of
test cases (see below).
From: José Expósito
Add a new procedural macro (`#[kunit_tests(kunit_test_suit_name)]`) to
run KUnit tests using a user-space like syntax.
The macro, that should be used on modules, transforms every `#[test]`
in a `kunit_case!` and adds a `kunit_unsafe_test_suite!` registering
all of them.
The
From: José Expósito
In some cases, we need to call test-only code from outside the test
case, for example, to mock a function or a module.
In order to check whether we are in a test or not, we need to test if
`CONFIG_KUNIT` is set.
Unfortunately, we cannot rely only on this condition because:
-
On 12/13/24 11:34, Krzysztof Kozlowski wrote:
On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
The CSIPHY of Qualcomm SoCs support both D-PHY and C-PHY standards for
CSI-2, but not any others so restrict the bus-type property describing
this to the supported values.
The only exceptio
Sean Christopherson writes:
> When clearing CONSTANT_TSC during CPUID emulation due to a Hyper-V quirk,
> use feature_bit() instead of SF() to ensure the bit is actually cleared.
> SF() evaluates to zero if the _host_ doesn't support the feature. I.e.
> KVM could keep the bit set if userspace ad
On 12/9/24 14:32, Bryan O'Donoghue wrote:
On 09/12/2024 12:01, Luca Weiss wrote:
Currently the Qualcomm CAMSS driver only supports D-PHY while the
hardware on most SoCs also supports C-PHY. Until this support is added,
check for D-PHY to make it somewhat explicit that C-PHY won't work.
Signed-o
On Fri Dec 13, 2024 at 12:02 PM CET, Vladimir Zapolskiy wrote:
> On 12/9/24 14:32, Bryan O'Donoghue wrote:
> > On 09/12/2024 12:01, Luca Weiss wrote:
> >> Currently the Qualcomm CAMSS driver only supports D-PHY while the
> >> hardware on most SoCs also supports C-PHY. Until this support is added,
>
On Fri Dec 13, 2024 at 11:50 AM CET, Vladimir Zapolskiy wrote:
> On 12/13/24 11:34, Krzysztof Kozlowski wrote:
> > On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
> >> The CSIPHY of Qualcomm SoCs support both D-PHY and C-PHY standards for
> >> CSI-2, but not any others so restrict the b
On Fri, 2024-12-13 at 10:54 +0100, Gabriele Monaco wrote:
> OVERHEAD COMPARISON
>
> [..]
>
> I will post another email with the scripts used to retrieve the data
> and
> more details about the runtime distribution.
This message contains the performance results produced by my scripts, which are
at
The script currently uses the subystem's status (S: field) to change how
maintainers are reported. One prominent example is when the status is
Supported, the maintainers are reported as "(supporter:SUBSYSTEM)".
This is misleading, as the Supported status defined as "Someone is
actually paid to loo
On 13/12/2024 11:24, Luca Weiss wrote:
On Fri Dec 13, 2024 at 11:50 AM CET, Vladimir Zapolskiy wrote:
On 12/13/24 11:34, Krzysztof Kozlowski wrote:
On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
The CSIPHY of Qualcomm SoCs support both D-PHY and C-PHY standards for
CSI-2, but not
On Fri Dec 13, 2024 at 10:34 AM CET, Krzysztof Kozlowski wrote:
> On Mon, Dec 09, 2024 at 01:01:05PM +0100, Luca Weiss wrote:
> > The CSIPHY of Qualcomm SoCs support both D-PHY and C-PHY standards for
> > CSI-2, but not any others so restrict the bus-type property describing
> > this to the support
This patchset moves the task_mm_cid_work to a preemptible and migratable
context. This reduces the impact of this task to the scheduling latency
of real time tasks.
The change makes the recurrence of the task a bit more predictable.
We also add optimisation and fixes to make sure the task_mm_cid_wo
The checks for the scan time in task_mm_cid_work are now superfluous
since the task runs in a delayed_work and the minimum periodicity is
already implied.
This patch removes those checks and the field from the mm_struct.
Additionally, we include a simple check to quickly terminate the
function if
From: Mathieu Desnoyers
When a process reduces its number of threads or clears bits in its CPU
affinity mask, the mm_cid allocation should eventually converge towards
smaller values.
However, the change introduced by:
commit 7e019dcc470f ("sched: Improve cache locality of RSEQ concurrency
IDs f
Currently, the task_mm_cid_work function is called in a task work
triggered by a scheduler tick. This can delay the execution of the task
for the entire duration of the function, negatively affecting the
response of real time tasks.
This patch runs the task_mm_cid_work in a new delayed work connec
A task in the kernel (task_mm_cid_work) runs somewhat periodically to
compact the mm_cid for each process, this test tries to validate that
it runs correctly and timely.
The test spawns 1 thread pinned to each CPU, then each thread, including
the main one, run in short bursts for some time. During
>>
>> Added support to read the vendor-specific PCI capability to identify the
>> type of device being emulated.
>>
>> Reviewed-by: Dan Carpenter
>> Signed-off-by: Shijith Thotton
>> ---
>> drivers/vdpa/octeon_ep/octep_vdpa.h | 20 ++
>> drivers/vdpa/octeon_ep/octep_vdpa_hw.c
>> Added macro definition for VIRTIO_PCI_CAP_VENDOR_CFG to identify the
>PCI
>> vendor data type in the virtio_pci_cap structure. Defined a new struct
>> virtio_pci_vndr_data for the vendor data capability header as per the
>> specification.
>>
>> Signed-off-by: Shijith Thotton
>> ---
>> include/
Hi Luis, Petr, Sami, Dani,
I just noticed that I failed in email and forgot to add you to the
recipient list of this series. Do you want a resend, or is this
sufficient?
Best regards,
Andreas Hindborg
"Andreas Hindborg" writes:
> This series extends the `module!` macro with support module p
On Wed, 11 Dec 2024 at 21:32, Antonio Quartulli wrote:
>
> static int ovpn_newlink(struct net *src_net, struct net_device *dev,
> struct nlattr *tb[], struct nlattr *data[],
> struct netlink_ext_ack *extack)
> {
> - return -EOPNOTSUPP;
> +
On 13/12/2024 13:32, Donald Hunter wrote:
On Wed, 11 Dec 2024 at 21:32, Antonio Quartulli wrote:
static int ovpn_newlink(struct net *src_net, struct net_device *dev,
struct nlattr *tb[], struct nlattr *data[],
struct netlink_ext_ack *extack)
If the header is included in a test without
certain other headers, it produces compiler warnings like:
In file included from [...]
../include/kunit/platform_device.h:15:57: warning: ‘struct completion’
declared inside parameter list will not be visible outside of this
definition or declaration
On Fri, Dec 13, 2024 at 03:37:13PM +0100, Alice Ryhl wrote:
[...]
> > > > @@ -0,0 +1,19 @@
> > > > +// SPDX-License-Identifier: GPL-2.0
> > > > +
> > > > +//! Atomic primitives.
> > > > +//!
> > > > +//! These primitives have the same semantics as their C counterparts:
> > > > and the precise defi
On Fri, Dec 13, 2024, Maxim Levitsky wrote:
> On Thu, 2024-12-12 at 22:19 -0800, Sean Christopherson wrote:
> > On Thu, Dec 12, 2024, Maxim Levitsky wrote:
> > > On Wed, 2024-12-11 at 16:44 -0800, Sean Christopherson wrote:
> > > > But, I can't help but wonder why KVM bothers emulating PML. I can
Hi Luca.
On 12/9/24 14:01, Luca Weiss wrote:
Currently the Qualcomm CAMSS driver only supports D-PHY while the
hardware on most SoCs also supports C-PHY. Until this support is added,
check for D-PHY to make it somewhat explicit that C-PHY won't work.
Signed-off-by: Luca Weiss
---
drivers/med
On Thu, Dec 12, 2024 at 11:42:37AM -0800, Sean Christopherson wrote:
> Gah, I got my enums mixed up. I conflated RET_PF_WRITE_PROTECTED with
> EMULTYPE_WRITE_PF_TO_SP. Ignore the above.
>
> FWIW, KVM _can't_ unprotect and retry in the EMULTYPE_WRITE_PF_TO_SP case.
> From
> kvm_unprotect_and_re
On Fri, 2024-12-13 at 16:10 +0100, Stefano Garzarella wrote:
> On Wed, Dec 11, 2024 at 11:47:05AM +0100, Philipp Stanner wrote:
> > The PCI functions
> >
> > pcim_iomap_regions()
> > pcim_iounmap_regions()
> > pcim_iomap_table()
> >
> > have been deprecated by the PCI subsystem.
> >
The following warning is being encountered at boot time:
WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086
hrtimer_start_range_ns+0x289/0x2d0
Modules linked in:
CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted
Stopper: multi_cpu_stop+0x0/0x1
We (meta) are running 6.12 release kernel in production and are encoutering
the below warning, mostly at boot time, reported by Vlad Poenaru.
[ cut here ]
WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086
hrtimer_start_range_ns+0x289/0x2d0
On Fri, Dec 13, 2024 at 02:20:24PM +, Shijith Thotton wrote:
> >>>
> >>> Added support to read the vendor-specific PCI capability to identify the
> >>> type of device being emulated.
> >>>
> >>> Reviewed-by: Dan Carpenter
> >>> Signed-off-by: Shijith Thotton
> >>> ---
> >>> drivers/vdpa/octe
On Thu, Dec 12, 2024 at 08:04:45PM GMT, Eduard Zingerman wrote:
> On Thu, 2024-12-12 at 16:22 -0700, Daniel Xu wrote:
>
> I think these changes are fine in general, but see below.
>
> > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > index 58b36cc96bd5..4947ef884a18 100644
> > ---
On Fri, Dec 13, 2024 at 01:28:27PM +0100, Andreas Hindborg wrote:
>
> Hi Luis, Petr, Sami, Dani,
>
> I just noticed that I failed in email and forgot to add you to the
> recipient list of this series. Do you want a resend, or is this
> sufficient?
If the patches didn't go to linux-modules, then
The get_state_synchronize_rcu_full() and poll_state_synchronize_rcu_full()
functions use the root rcu_node structure's ->gp_seq field to detect
the beginnings and ends of grace periods, respectively. This choice is
necessary for the poll_state_synchronize_rcu_full() function because
(give or take
On Thu, Dec 12, 2024 at 08:04:28PM GMT, Eduard Zingerman wrote:
> On Thu, 2024-12-12 at 16:22 -0700, Daniel Xu wrote:
> > Previously, the verifier was treating all PTR_TO_STACK registers passed
> > to a helper call as potentially written to by the helper. However, all
> > calls to check_stack_range
On Thu, 2024-12-12 at 22:19 -0800, Sean Christopherson wrote:
> On Thu, Dec 12, 2024, Maxim Levitsky wrote:
> > On Wed, 2024-12-11 at 16:44 -0800, Sean Christopherson wrote:
> > > But, I can't help but wonder why KVM bothers emulating PML. I can
> > > appreciate
> > > that avoiding exits to L1 wo
On Fri, Dec 13, 2024, Ivan Orlov wrote:
> On Thu, Dec 12, 2024 at 11:42:37AM -0800, Sean Christopherson wrote:
> > Unprotect and re-execute is fine, what I'm worried about is *successfully*
> > emulating the instruction. E.g.
> >
> > 1. CPU executes instruction X and hits a #GP.
> > 2. While
On Fri, Dec 13, 2024 at 03:32:47PM +0100, Alice Ryhl wrote:
> On Thu, Dec 12, 2024 at 6:34 PM Boqun Feng wrote:
> >
> > On Thu, Dec 12, 2024 at 11:57:07AM +0100, Alice Ryhl wrote:
> > [...]
> > > > diff --git a/rust/kernel/sync/atomic/generic.rs
> > > > b/rust/kernel/sync/atomic/generic.rs
> > >
Hi Maxime,
On Fri, Dec 13, 2024 at 12:59:57PM +0100, Maxime Ripard wrote:
> On Wed, Dec 11, 2024 at 04:31:41PM -0800, Brian Norris wrote:
> > --- a/drivers/base/test/platform-device-test.c
> > +++ b/drivers/base/test/platform-device-test.c
> > @@ -217,7 +219,45 @@ static struct kunit_suite
> > p
Updated the driver to utilize all the MSI-X interrupt vectors supported
by each OCTEON endpoint VF, instead of relying on a single vector.
Enabling more interrupts allows packets from multiple rings to be
distributed across multiple cores, improving parallelism and
performance.
Reviewed-by: Dan Ca
Added support to read the vendor-specific PCI capability to identify the
type of device being emulated.
Reviewed-by: Dan Carpenter
Signed-off-by: Shijith Thotton
---
drivers/vdpa/octeon_ep/octep_vdpa.h | 20 +
drivers/vdpa/octeon_ep/octep_vdpa_hw.c | 36 ++
From: Satha Rao
The first interrupt of the device is used to notify the host about
device configuration changes, such as link status updates. The ISR
configuration area is updated to indicate a config change event when
triggered.
Signed-off-by: Satha Rao
Reviewed-by: Dan Carpenter
Acked-by: Ja
Added macro definition for VIRTIO_PCI_CAP_VENDOR_CFG to identify the PCI
vendor data type in the virtio_pci_cap structure. Defined a new struct
virtio_pci_vndr_data for the vendor data capability header as per the
specification.
Signed-off-by: Shijith Thotton
---
include/uapi/linux/virtio_pci.h
>> >>> Added support to read the vendor-specific PCI capability to identify the
>> >>> type of device being emulated.
>> >>>
>> >>> Reviewed-by: Dan Carpenter
>> >>> Signed-off-by: Shijith Thotton
>> >>> ---
>> >>> drivers/vdpa/octeon_ep/octep_vdpa.h | 20 ++
>> >>> drivers/vdpa
On Thu, 2024-12-12 at 16:22 -0700, Daniel Xu wrote:
> Test that nullness elision works for common use cases. For example, we
> want to check that both full and subreg stack slots are recognized. As
> well as when there's both const and non-const values of R2 leading up to
> a lookup. And obviously
>>>
>>> Added support to read the vendor-specific PCI capability to identify the
>>> type of device being emulated.
>>>
>>> Reviewed-by: Dan Carpenter
>>> Signed-off-by: Shijith Thotton
>>> ---
>>> drivers/vdpa/octeon_ep/octep_vdpa.h | 20 ++
>>> drivers/vdpa/octeon_ep/octep_vdp
On Wed, 11 Dec 2024 at 21:32, Antonio Quartulli wrote:
>
> +name: peer
> +type: nest
> +doc: |
> + The peer object containing the attributed of interest for the
> specific
typo: attributes
> + operation
> +nested-attributes: peer
I also spotted
On 13/12/2024 17:45, Donald Hunter wrote:
On Wed, 11 Dec 2024 at 21:32, Antonio Quartulli wrote:
+name: peer
+type: nest
+doc: |
+ The peer object containing the attributed of interest for the
specific
typo: attributes
+ operation
+nested-
On 2024-12-13 04:54, Gabriele Monaco wrote:
Currently, the task_mm_cid_work function is called in a task work
triggered by a scheduler tick. This can delay the execution of the task
for the entire duration of the function, negatively affecting the
response of real time tasks.
This patch runs the
On Fri, 2024-12-13 at 09:29 -0500, Mathieu Desnoyers wrote:
> On 2024-12-13 04:54, Gabriele Monaco wrote:
> > A task in the kernel (task_mm_cid_work) runs somewhat periodically
> > to
> > compact the mm_cid for each process, this test tries to validate
> > that
> > it runs correctly and timely.
>
Hi all,
This patch series continues the work to migrate the script tests into
prog_tests.
test_xdp_meta.sh uses the BPF programs defined in progs/test_xdp_meta.c
to do a simple XDP/TC functional test that checks the metadata
allocation performed by the bpf_xdp_adjust_meta() helper.
This is alrea
SEC("t") and SEC("x") can't be loaded by the __load() helper.
Rename these sections SEC("tc") and SEC("xdp") so they can be
interpreted by the __load() helper in upcoming patch.
Update the test_xdp_meta.sh to fit these new names.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/tes
test_xdp_meta.sh can't be used by the BPF CI.
Migrate test_xdp_meta.sh in a new test case in xdp_context_test_run.c.
It uses the same BPF programs located in progs/test_xdp_meta.c and the
same network topology.
Remove test_xdp_meta.sh and its Makefile entry.
Signed-off-by: Bastien Curutchet (eBPF
On Wed, Dec 11, 2024 at 11:47:05AM +0100, Philipp Stanner wrote:
The PCI functions
pcim_iomap_regions()
pcim_iounmap_regions()
pcim_iomap_table()
have been deprecated by the PCI subsystem.
Replace these functions with their successors pcim_iomap_region() and
pcim_iounma
On 2024-12-13 04:54, Gabriele Monaco wrote:
The checks for the scan time in task_mm_cid_work are now superfluous
since the task runs in a delayed_work and the minimum periodicity is
already implied.
This patch removes those checks and the field from the mm_struct.
Additionally, we include a sim
On 2024-12-13 04:54, Gabriele Monaco wrote:
From: Mathieu Desnoyers
When a process reduces its number of threads or clears bits in its CPU
affinity mask, the mm_cid allocation should eventually converge towards
smaller values.
I target v6.13 for this patch. As it fixes a commit which was
rece
On Thu, Dec 12, 2024 at 6:07 PM Boqun Feng wrote:
>
> On Thu, Dec 12, 2024 at 11:51:23AM +0100, Alice Ryhl wrote:
> > On Fri, Nov 1, 2024 at 7:03 AM Boqun Feng wrote:
> > >
> > > Preparation for generic atomic implementation. To unify the
> > > ipmlementation of a generic method over `i32` and `i
On Thu, Dec 12, 2024 at 1:32 AM Brian Norris wrote:
>
> of_find_device_by_node(), bus_find_device_by_of_node(),
> bus_find_device_by_fwnode(), ..., all produce arbitrary results when
> provided with a NULL of_node, fwnode, ACPI handle, etc. This is
> counterintuitive, and the source of a few bugs,
On Wed, 11 Dec 2024 19:16:39 +0800, Weizhao Ouyang wrote:
> When using svcr_in to check ZA and Streaming Mode, we should make sure
> that the value in x2 is correct, otherwise it may trigger an Illegal
> instruction if FEAT_SVE and !FEAT_SME.
>
>
Applied to arm64 (for-next/fixes), thanks!
[1/1]
On Thu, Dec 12, 2024 at 6:34 PM Boqun Feng wrote:
>
> On Thu, Dec 12, 2024 at 11:57:07AM +0100, Alice Ryhl wrote:
> [...]
> > > diff --git a/rust/kernel/sync/atomic/generic.rs
> > > b/rust/kernel/sync/atomic/generic.rs
> > > new file mode 100644
> > > index ..204da38e2691
> > > --- /d
On 2024-12-13 04:54, Gabriele Monaco wrote:
A task in the kernel (task_mm_cid_work) runs somewhat periodically to
compact the mm_cid for each process, this test tries to validate that
it runs correctly and timely.
The test spawns 1 thread pinned to each CPU, then each thread, including
the main
On Fri, 2024-12-13 at 09:14 -0500, Mathieu Desnoyers wrote:
> On 2024-12-13 04:54, Gabriele Monaco wrote:
> > Currently, the task_mm_cid_work function is called in a task work
> > triggered by a scheduler tick. This can delay the execution of the
> > task
> > for the entire duration of the functi
On Fri, 13 Dec 2024 at 00:24, Daniel Xu wrote:
>
> This commit allows progs to elide a null check on statically known map
> lookup keys. In other words, if the verifier can statically prove that
> the lookup will be in-bounds, allow the prog to drop the null check.
>
> This is useful for two reaso
Le Thu, Dec 12, 2024 at 10:42:14AM -0800, Paul E. McKenney a écrit :
> From: Frederic Weisbecker
>
> After a CPU has set itself offline and before it eventually calls
> rcutree_report_cpu_dead(), there are still opportunities for callbacks
> to be enqueued, for example from an IRQ. When that happ
Le Thu, Dec 12, 2024 at 10:42:13AM -0800, Paul E. McKenney a écrit :
> From: Frederic Weisbecker
>
> It's more convenient to benefit from the fallthrough feature of
> switch / case to handle the timer state machine. Also a new state is
> about to be added that will take advantage of it.
>
> No i
On Fri, Dec 13, 2024 at 03:02:11PM GMT, Andrii Nakryiko wrote:
> On Thu, Dec 12, 2024 at 3:23 PM Daniel Xu wrote:
> >
> > This commit allows progs to elide a null check on statically known map
> > lookup keys. In other words, if the verifier can statically prove that
> > the lookup will be in-boun
On Fri, 2024-12-13 at 19:44 -0700, Daniel Xu wrote:
[...]
> > > + /* First handle precisely tracked STACK_ZERO, up to BPF_REG_SIZE
> > > */
> > > + stype = state->stack[spi].slot_type;
> > > + for (i = 0; i < BPF_REG_SIZE && stype[i] == STACK_ZERO; i++)
> >
> > it's Friday and
On Fri, 13 Dec 2024 07:18:08 + Hangbin Liu wrote:
> On Thu, Dec 12, 2024 at 06:27:34AM -0800, Jakub Kicinski wrote:
> > On Wed, 11 Dec 2024 07:11:25 + Hangbin Liu wrote:
> > > The first patch fixes the xfrm offload feature during setup active-backup
> > > mode. The second patch add a ipse
81 matches
Mail list logo
