On Mon, Jun 23, 2025 at 03:28:03PM +0200, Dmitry Vyukov wrote:
Nice!
A bag of assorted comments:
1. I share the same concern of duplicating info.
If there are lots of duplication it may lead to failure of the whole effort
since folks won't update these and/or they will get out of sync.
If a sys
Add the refscale test for shazptr to measure the reader side
performance.
Signed-off-by: Boqun Feng
---
kernel/rcu/refscale.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/kernel/rcu/refscale.c b/kernel/rcu/refscale.c
index f11a7c2af778..154520e4ee4
For synchronization mechanisms similar to RCU, there could be no "grace
period" concept (e.g. hazard pointers), therefore allow
rcu_scale_ops::get_gp_seq to be a NULL pointer for these cases, and
simply treat started and finished grace period as 0.
Signed-off-by: Boqun Feng
---
kernel/rcu/rcusca
On Mon, Jun 23, 2025 at 11:11 PM Mathieu Poirier
wrote:
>
> Good day,
>
> On Wed, Jun 18, 2025 at 02:26:43PM +0800, Shengjiu Wang wrote:
> > when recovery is triggered, rproc_stop() is called first then
> > rproc_start(), but there is no rproc_unprepare_device() and
> > rproc_prepare_device() in t
Erik Lundgren and Breno Leitao reported [1] a case where
lockdep_unregister_key() can be called from time critical code pathes
where rntl_lock() may be held. And the synchronize_rcu() in it can slow
down operations such as using tc to replace a qdisc in a network device.
In fact the synchronize_rc
Add two rcu_scale_ops to include tests from simple hazard pointers
(shazptr). One is with evenly distributed readers, and the other is with
all WILDCARD readers. This could show the best and worst case scenarios
for the synchronization time of simple hazard pointers.
Signed-off-by: Boqun Feng
---
Add a module parameter for shazptr to allow skip the self scan in
synchronize_shaptr(). This can force every synchronize_shaptr() to use
shazptr scan kthread, and help testing the shazptr scan kthread.
Another reason users may want to set this paramter is to reduce the self
scan CPU cost in synchr
For a general purpose hazard pointers implemenation, always busy waiting
is not an option. It may benefit some special workload, but overall it
hurts the system performance when more and more users begin to call
synchronize_shazptr(). Therefore avoid busy waiting for hazard pointer
slots changes by
Add the refscale test for shazptr, which starts another shazptr critical
section inside an existing one to measure the reader side performance
when wildcard logic is triggered.
Signed-off-by: Boqun Feng
---
kernel/rcu/refscale.c | 40 +++-
1 file changed, 39 i
As its name suggests, simple hazard pointers (shazptr) is a
simplification of hazard pointers [1]: it has only one hazard pointer
slot per-CPU and is targeted for simple use cases where the read-side
already has preemption disabled. It's a trade-off between full features
of a normal hazard pointer
Hi,
This is the official first version of simple hazard pointers following
the RFC:
https://lore.kernel.org/lkml/20250414060055.341516-1-boqun.f...@gmail.com/
I rebase it onto v6.16-rc3 and hope to get more feedback this time.
Thanks a lot for Breno Leitao to try the RFC out and share
On 6/9/25 04:28, Thomas Weißschuh wrote:
Add support for SuperH/"sh" to nolibc.
Only sh4 is tested for now.
This is only tested on QEMU so far.
Additional testing would be very welcome.
I ran this by Jeff Dionne (the j-core architect) who said:
> Looks correct to me. There are no endian assu
From: Peng Fan
Add SCMI LMM/CPU nodes which is for remoteproc to handle remote cores.
Signed-off-by: Peng Fan
---
arch/arm64/boot/dts/freescale/imx95.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi
b/arch/arm64/boot/dts/freescale/imx95
From: Peng Fan
i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
one Cortex-M7 core. The System Control Management Interface(SCMI)
firmware runs on the M33 core. The i.MX95 SCMI firmware named System
Manager(SM) includes vendor extension protocols, Logical Machine
Management(LMM) proto
From: Peng Fan
Add compatible string for the Cortex-M7 core in i.MX95
Signed-off-by: Peng Fan
---
Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
b/Documentation
i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
one Cortex-M7 core. The System Control Management Interface(SCMI)
firmware runs on the M33 core. The i.MX95 SCMI firmware named System
Manager(SM) includes vendor extension protocols, Logical Machine
Management(LMM) protocol and CPU proto
Arguments passed into WEXITSTATUS() should have been initialized earlier.
Otherwise following warning show up while building platform selftests on
arm64. Hence just zero out all the relevant local variables to avoid the
build warning.
Warning: ‘status’ may be used uninitialized in this function
[
On 6/24/25 12:15 AM, Thomas Weißschuh wrote:
> For the test implementation of the SuperH architecture a second serial
> serial port needs to be used. Unfortunately the currently used 'stdio'
"Serial" typed twice? :-)
> driver does not support multiple serial ports at the same time.
>
> Switc
Hi!
> 6. What's the goal of validation of the input arguments?
> Kernel code must do this validation anyway, right.
> Any non-trivial validation is hard, e.g. even for open the validation function
> for file name would need to have access to flags and check file precense for
> some flags combinatio
On Fri, 23 May 2025 23:43:52 +0530, Rahul Kumar wrote:
> Corrected two instances of the misspelled word 'occurences' to
> 'occurrences' in comments explaining node invariants in sparsebit.c.
> These comments describe core behavior of the data structure and
> should be clear.
Applied to kvm-x86 s
On Tue, Jun 24, 2025 at 3:45 PM Eduard Zingerman wrote:
>
> On Mon, 2025-06-23 at 00:03 -0400, Harishankar Vishwanathan wrote:
> > The previous commit improves the precision in scalar(32)_min_max_add,
> > and scalar(32)_min_max_sub. The improvement in precision occurs in cases
> > when all outcome
On 6/24/25 17:02, Paolo Abeni wrote:
On 6/21/25 4:49 PM, Bui Quang Minh wrote:
When calling buf_to_xdp, the len argument is the frame data's length
without virtio header's length (vi->hdr_len). We check that len with
xsk_pool_get_rx_frame_size() + vi->hdr_len
to ensure the provided len
The current implementation of test_unmerge_uffd_wp() explicitly sets
`uffdio_api.features = UFFD_FEATURE_PAGEFAULT_FLAG_WP` before calling
UFFDIO_API. This can cause the ioctl() call to fail with EINVAL on kernels
that do not support UFFD-WP, leading the test to fail unnecessarily:
# ---
Rename is_signed_type() to is_signed_var() to avoid colliding with a macro
of the same name defined by linux/overflow.h. Note, overflow.h's version
takes a type as the input, whereas the harness's version takes a variable!
This fixes warnings (and presumably potential test failures) in tests
that
On Tue, Jun 24, 2025 at 03:49:06PM -0700, David Dai wrote:
> For systems using a sched_ext scheduler and has panic_on_rcu_stall
> enabled, try kicking out the current scheduler before issuing a panic.
>
> While there are numerous reasons for RCU CPU stalls that are not
> directly attributed to the
For systems using a sched_ext scheduler and has panic_on_rcu_stall
enabled, try kicking out the current scheduler before issuing a panic.
While there are numerous reasons for RCU CPU stalls that are not
directly attributed to the scheduler, deferring the panic gives
sched_ext an opportunity to pro
On Mon, 2025-06-23 at 00:03 -0400, Harishankar Vishwanathan wrote:
> The previous commit improves the precision in scalar(32)_min_max_add,
> and scalar(32)_min_max_sub. The improvement in precision occurs in cases
> when all outcomes overflow or underflow, respectively.
>
> This commit adds selfte
"Benno Lossin" writes:
> On Mon Jun 23, 2025 at 4:31 PM CEST, Andreas Hindborg wrote:
>> "Benno Lossin" writes:
>>
>>> On Mon Jun 23, 2025 at 11:44 AM CEST, Andreas Hindborg wrote:
"Benno Lossin" writes:
> On Fri Jun 20, 2025 at 1:29 PM CEST, Andreas Hindborg wrote:
>> "Benno
On Mon, Jun 23, 2025 at 06:30:06PM -0700, Jakub Kicinski wrote:
> Could you turn this into a docstring?
Sure, I will fix all of them except C0301, which is a error message
string and I prefer not to truncate.
> > +def set_single_rx_tx_queue(interface_name: str) -> None:
> > +"""Set the numb
On 6/24/25 3:20 AM, Cristian Cozzolino via B4 Relay wrote:
> From: Cristian Cozzolino
>
> Billion Capture+ (flipkart,rimob) is a smartphone released in 2017, based
> on Snapdragon 625 (MSM8953) SoC.
>
> Add a device tree with initial support for:
>
> - GPIO keys
> - SDHCI (internal and external
On 24/06/2025 21:46, Luca Weiss wrote:
Hi Dmitry,
On 24-06-2025 2:59 a.m., Dmitry Baryshkov wrote:
On Sat, Jun 21, 2025 at 03:19:55PM +0200, Luca Weiss wrote:
Switch over the ADSP PIL to use power-domains instead of a regulator,
and have one commit switching over the MSM8974 SoC plus all the d
On Tue, Jun 17, 2025 at 06:20:49PM +0200, Uros Bizjak wrote:
> On Tue, Jun 17, 2025 at 5:01 PM Dave Hansen wrote:
> >
> > On 6/17/25 07:44, Jarkko Sakkinen wrote:
> > > I don't really see how this is that useful. That said, f a bug fix or
> > > feature used encls mnemonic, I'd had no problems with
On Tue, Jun 17, 2025 at 08:01:28AM -0700, Dave Hansen wrote:
> On 6/17/25 07:44, Jarkko Sakkinen wrote:
> > I don't really see how this is that useful. That said, f a bug fix or
> > feature used encls mnemonic, I'd had no problems with acking it.
>
> It's not _that_ useful.
>
> But old assemblers
Hello,
syzbot found the following issue on:
HEAD commit:4f4040ea5d3e net: ti: icssg-prueth: Add prp offload suppor..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11630dd458
kernel config: https://syzkaller.appspot.com/x/.config?x=fab0bcec5be1995b
das
The test_kexec_jump program builds correctly when invoked from the top-level
selftests/Makefile, which explicitly sets the OUTPUT variable. However,
building directly in tools/testing/selftests/kexec fails with:
make: *** No rule to make target '/test_kexec_jump', needed by
'test_kexec_jump.sh'
Utilize per-vma locks to stabilize vma after lookup without taking
mmap_lock during PROCMAP_QUERY ioctl execution. While we might take
mmap_lock for reading during contention, we do that momentarily only
to lock the vma.
This change is designed to reduce mmap_lock contention and prevent
PROCMAP_QUE
With maple_tree supporting vma tree traversal under RCU and per-vma
locks, /proc/pid/maps can be read while holding individual vma locks
instead of locking the entire address space.
Completely lockless approach (walking vma tree under RCU) would be quite
complex with the main issue being get_vma_na
Add verbose mode to the proc tests to print debugging information.
Usage: proc-pid-vm -v
Signed-off-by: Suren Baghdasaryan
---
tools/testing/selftests/proc/proc-pid-vm.c | 154 +++--
1 file changed, 141 insertions(+), 13 deletions(-)
diff --git a/tools/testing/selftests/proc/pro
Extend /proc/pid/maps tearing test to verify PROCMAP_QUERY ioctl operation
correctness while the vma is being concurrently modified.
Signed-off-by: Suren Baghdasaryan
---
tools/testing/selftests/proc/proc-pid-vm.c | 60 ++
1 file changed, 60 insertions(+)
diff --git a/tools/
Test that /proc/pid/maps does not report unexpected holes in the address
space when we concurrently remap a part of a vma into the middle of
another vma. This remapping results in the destination vma being split
into three parts and the part in the middle being patched back from,
all done concurren
Test that /proc/pid/maps does not report unexpected holes in the address
space when a vma at the edge of the page is being concurrently remapped.
This remapping results in the vma shrinking and expanding from under the
reader. We should always see either shrunk or expanded (original) version
of th
The /proc/pid/maps file is generated page by page, with the mmap_lock
released between pages. This can lead to inconsistent reads if the
underlying vmas are concurrently modified. For instance, if a vma split
or merge occurs at a page boundary while /proc/pid/maps is being read,
the same vma might
Reading /proc/pid/maps requires read-locking mmap_lock which prevents any
other task from concurrently modifying the address space. This guarantees
coherent reporting of virtual address ranges, however it can block
important updates from happening. Oftentimes /proc/pid/maps readers are
low priority
The hugepage test cases of iommufd_dirty_tracking have the 64MB and 128MB
coverages. Both of them are smaller than the default hugepage size 512MB,
when CONFIG_PAGE_SIZE_64KB=y. However, these test cases have a variant of
using huge pages, which would mmap(MAP_HUGETLB) using these smaller sizes
tha
On 6/23/25 6:44 PM, Luca Weiss wrote:
> On 23-06-2025 2:39 p.m., Konrad Dybcio wrote:
>> On 6/21/25 3:19 PM, Luca Weiss wrote:
>>> Due to historical reasons all msm8974 boards have used the CX power rail
>>> as regulator instead of going through the power domain framework.
>>>
>>> Since rpmpd has g
Hi Dmitry,
On 24-06-2025 2:59 a.m., Dmitry Baryshkov wrote:
On Sat, Jun 21, 2025 at 03:19:55PM +0200, Luca Weiss wrote:
Switch over the ADSP PIL to use power-domains instead of a regulator,
and have one commit switching over the MSM8974 SoC plus all the devices
to use power-domains.
Note, that
Because SRCU-lite is being replaced by SRCU-fast, this commit removes
support for SRCU-lite from rcutorture.c
Signed-off-by: Paul E. McKenney
---
include/linux/srcu.h| 2 +-
kernel/rcu/rcutorture.c | 7 ---
2 files changed, 1 insertion(+), 8 deletions(-)
diff --git a/include/linux/srcu.
Commit 869c788909b9 ("selftests: harness: Stop using setjmp()/longjmp()")
changed the harness structure. For some unknown reason, two build warnings
occur to the iommufd selftest:
iommufd.c: In function ‘wrapper_iommufd_mock_domain_all_aligns’:
iommufd.c:1807:17: warning: ‘mfd’ may be used uniniti
The mfd and mfd_buffer will be used in the tests directly without an extra
check. Test them in setup_sizes() to ensure they are safe to use.
Fixes: 0bcceb1f51c7 ("iommufd: Selftest coverage for IOMMU_IOAS_MAP_FILE")
Cc: sta...@vger.kernel.org
Reviewed-by: Jason Gunthorpe
Signed-off-by: Nicolin Ch
Do not forget to close mfd in the error paths, since none of the callers
would close it when ASSERT_NE(MAP_FAILED, buf) fails.
Fixes: 0bcceb1f51c7 ("iommufd: Selftest coverage for IOMMU_IOAS_MAP_FILE")
Cc: sta...@vger.kernel.org
Reviewed-by: Jason Gunthorpe
Signed-off-by: Nicolin Chen
---
tools
A few selftest harness changes being merged to v6.16, which exposed some
bugs and vulnerabilities in the iommufd selftest code. Fix them properly.
Note that the patch fixing the build warnings at mfd is not ideal, as it
has possibly hit some corner case in the gcc:
https://lore.kernel.org/all/aei8
On Tue, 24 Jun 2025 15:27:27 +0100 Breno Leitao wrote:
> > > +try:
> > > +for key, value in config_data.items():
> > > +if DEBUG:
> > > +ksft_pr(f"Setting {key} to {value}")
> > > +with open(
> > > +f"{NETCONSOLE_CONFIGFS_PATH}/{ta
This commit prepares for the removal of SRCU-Lite by removing the SRCU-L
rcutorture scenario that tests it.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/configs/rcu/CFLIST | 1 -
tools/testing/selftests/rcutorture/configs/rcu/SRCU-L | 10 --
.../selftests/rcu
On Mon, Jun 23, 2025 at 09:32:54AM -0600, Mathieu Poirier wrote:
> On Tue, Jun 17, 2025 at 04:34:47PM -0300, Hiago De Franco wrote:
> > From: Hiago De Franco
> >
> > This patch series depends on Ulf's patches that are currently under
> > review, "pmdomain: Add generic ->sync_state() support to ge
On Mon, Jun 23, 2025 at 09:29:47AM -0600, Mathieu Poirier wrote:
> On Tue, Jun 17, 2025 at 04:34:50PM -0300, Hiago De Franco wrote:
> > From: Hiago De Franco
> >
> > When the remote core is started before Linux boots (e.g., by the
> > bootloader), the driver currently is not able to attach becaus
Hi Mathieu,
On Mon, Jun 23, 2025 at 09:15:52AM -0600, Mathieu Poirier wrote:
> Hi Hiago,
>
> On Tue, Jun 17, 2025 at 04:34:49PM -0300, Hiago De Franco wrote:
> > From: Hiago De Franco
> >
> > For the i.MX8X and i.MX8 family SoCs, when the M-core is powered up
> > by the bootloader, M-core and L
Now that SRCU-lite has been removed from the kernel, let's remove the
now-redundant deprecation from checkpatch.pl.
Signed-off-by: Paul E. McKenney
---
scripts/checkpatch.pl | 2 --
1 file changed, 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 664f7b7a622c2..86
Because SRCU-lite is being replaced by SRCU-fast, this commit removes
support for SRCU-lite from refscale.c.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/refscale.c | 32 +---
1 file changed, 1 insertion(+), 31 deletions(-)
diff --git a/kernel/rcu/refscale.c b/kern
This commit removes the SRCU-lite implementation, which has been replaced
by SRCU-fast.
Signed-off-by: Paul E. McKenney
---
include/linux/srcu.h | 47 ++--
include/linux/srcutiny.h | 3 ---
include/linux/srcutree.h | 38
3
Hello!
This series removes the deprecated SRCU-lite flavor:
1. Remove support for SRCU-lite.
2. Remove SRCU-lite scenarios.
3. Remove support for SRCU-lite.
4. Remove SRCU-lite implementation.
5. Remove SRCU-lite deprecation.
On 6/21/25 4:49 PM, Bui Quang Minh wrote:
> This commit does not do any functional changes. It moves xdp->data
> adjustment for buffer other than first buffer to buf_to_xdp() helper so
> that the xdp_buff adjustment does not scatter over different functions.
>
> Signed-off-by: Bui Quang Minh
> --
Add a new test to ensure that when the transport changes a null pointer
dereference does not occur. The bug was reported upstream [1] and fixed
with commit 2cb7c756f605 ("vsock/virtio: discard packets if the
transport changes").
KASAN: null-ptr-deref in range [0x0060-0x0067
On 24.06.25 06:24, Li Wang wrote:
The current implementation of test_unmerge_uffd_wp() explicitly sets
`uffdio_api.features = UFFD_FEATURE_PAGEFAULT_FLAG_WP` before calling
UFFDIO_API. This can cause the ioctl() call to fail with EINVAL on kernels
that do not support UFFD-WP, leading the test to
Hi!
> > You may wonder if such kind of tests are useful at all, since quite a
> > few of these errors are checked for and generated from a common
> > functions. There are at least two cases I can think of. First of all it
> > makes sure that errors are stable when particular function/subsystem is
>
On 6/24/25 17:17, Paolo Abeni wrote:
On 6/21/25 4:49 PM, Bui Quang Minh wrote:
This commit does not do any functional changes. It moves xdp->data
adjustment for buffer other than first buffer to buf_to_xdp() helper so
that the xdp_buff adjustment does not scatter over different functions.
Signe
is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: using specified base-commit 0ff41df1cb268fc69e703a08a57ee14ae967d0ca
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_D
On Mon, Jun 24, 2025 at 00:00:00 +, Lorenzo Stoakes wrote:
> Sorry if it seemed harsh, I appreciate the first patch can be difficult
> (I still remember mine!) but hopefully it's clear the focus is on
> getting things right technically and this is all :)
>
> Overall I think something more like
On 6/24/25 14:34, Clément Léger wrote:
Gentle ping.
I put it back again on my for-next branch.
Thanks,
Alex
Thanks,
Clément
On 22/05/2025 14:51, Clément Léger wrote:
This selftest tests all the currently emulated instructions (except for
the RV32 compressed ones which are left as a fu
Gentle ping.
Thanks,
Clément
On 22/05/2025 14:51, Clément Léger wrote:
> This selftest tests all the currently emulated instructions (except for
> the RV32 compressed ones which are left as a future exercise for a RV32
> user). For the FPU instructions, all the FPU registers are tested.
>
> Sig
> Subject: Re: [PATCH v2 1/3] dt-bindings: remoteproc: fsl,imx-rproc:
> Add support for i.MX95
>
> On 06/06/2025 03:55, Peng Fan (OSS) wrote:
> >fsl,entry-address:
> > $ref: /schemas/types.yaml#/definitions/uint32
> > description:
> > @@ -78,6 +85,12 @@ properties:
> > descripti
I used the "virtio-net-pci,...,in_order=on" to test this series of
patches v3 with regression tests, everything works fine.
Tested-by: Lei Yang
On Mon, Jun 16, 2025 at 4:27 PM Jason Wang wrote:
>
> To be consistent with virtqueue_reset().
>
> Reviewed-by: Xuan Zhuo
> Signed-off-by: Jason Wang
Tested this series of patches with virtio-net regression tests,
everything works fine.
Tested-by: Lei Yang
On Tue, Jun 17, 2025 at 8:31 PM Eugenio Perez Martin
wrote:
>
> On Tue, Jun 17, 2025 at 2:18 AM wrote:
> >
> > From: "Dr. David Alan Gilbert"
> >
> > Hi,
> > The following pair of patc
On 6/21/25 4:49 PM, Bui Quang Minh wrote:
> When calling buf_to_xdp, the len argument is the frame data's length
> without virtio header's length (vi->hdr_len). We check that len with
>
> xsk_pool_get_rx_frame_size() + vi->hdr_len
>
> to ensure the provided len does not larger than the allo
On Sat, 21 Jun 2025 21:49:52 +0700, Bui Quang Minh
wrote:
> This commit does not do any functional changes. It moves xdp->data
> adjustment for buffer other than first buffer to buf_to_xdp() helper so
> that the xdp_buff adjustment does not scatter over different functions.
>
> Signed-off-by: Bui
Hi Adrian,
On Tue, Jun 24, 2025 at 08:03:47AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Thomas,
>
> On Mon, 2025-06-23 at 23:15 +0200, Thomas Weißschuh wrote:
> > Add support for SuperH/"sh" to nolibc.
> > Only sh4 is tested for now.
> >
> > This is only tested on QEMU so far.
> > Additional
On Sat, 21 Jun 2025 21:49:52 +0700, Bui Quang Minh
wrote:
> This commit does not do any functional changes. It moves xdp->data
> adjustment for buffer other than first buffer to buf_to_xdp() helper so
> that the xdp_buff adjustment does not scatter over different functions.
>
> Signed-off-by: Bui
On Sat, 21 Jun 2025 21:49:51 +0700, Bui Quang Minh
wrote:
> When calling buf_to_xdp, the len argument is the frame data's length
> without virtio header's length (vi->hdr_len). We check that len with
>
> xsk_pool_get_rx_frame_size() + vi->hdr_len
>
> to ensure the provided len does not larg
On Mon, 23 Jun 2025 14:52:10 +0800, WangYuli wrote:
> Add missing parameter documentation for virtio_dma_buf_attach()
> function to fix kernel-doc warnings:
>
> Warning: drivers/virtio/virtio_dma_buf.c:41 function parameter 'dma_buf' not
> described in 'virtio_dma_buf_attach'
> Warning: drivers/v
Hi Thomas,
On Mon, 2025-06-23 at 23:15 +0200, Thomas Weißschuh wrote:
> Add support for SuperH/"sh" to nolibc.
> Only sh4 is tested for now.
>
> This is only tested on QEMU so far.
> Additional testing would be very welcome.
> Test instructions:
> $ cd tools/testings/selftests/nolibc/
> $ make -f
79 matches
Mail list logo
