On Tue 05 Jan 20:38 CST 2021, Alex Elder wrote:
> Define stub functions for the exposed MDT functions in case
> QCOM_MDT_LOADER is not configured. This allows users of these
> functions to link correctly for COMPILE_TEST builds without
> QCOM_SCM enabled.
>
Reviewed-by: Bjorn Andersson
On Tue 05 Jan 20:38 CST 2021, Alex Elder wrote:
> Stub functions are defined for SSR notifier registration in case
> QCOM_RPROC_COMMON is not configured. As a result, code that uses
> these functions can link successfully even if the common remoteproc
> code is not built.
>
> Code that
This MHI client driver allows userspace clients to transfer
raw data between MHI device and host using standard file operations.
Driver instantiates UCI device object which is associated to device
file node. UCI device object instantiates UCI channel object when device
file node is opened. UCI
On Tue, Jan 05, 2021 at 10:36:40AM -0500, Tejun Heo wrote:
> Happy new year!
>
> On Wed, Dec 16, 2020 at 12:02:37PM -0800, Vipin Sharma wrote:
> > I like the idea of having a separate controller to keep the code simple and
> > easier for maintenance.
>
> Yeah, the more I think about it, keeping
MHI userspace client driver is creating device file node
for user application to perform file operations. File
operations are handled by MHI core driver. Currently
QMI MHI channel is supported by this driver.
Signed-off-by: Hemant Kumar
Reviewed-by: Jeffrey Hugo
---
Documentation/mhi/index.rst
Currently this macro is defined in internal MHI header as
a TRE length mask. Moving it to external header allows MHI
client drivers to set this upper bound for the transmit
buffer size.
Signed-off-by: Hemant Kumar
Reviewed-by: Jeffrey Hugo
Reviewed-by: Manivannan Sadhasivam
---
This patch series adds support for UCI driver. UCI driver enables userspace
clients to communicate to external MHI devices like modem. UCI driver probe
creates standard character device file nodes for userspace clients to
perform open, read, write, poll and release file operations. These file
Thanks for the vacation notice Jessica! I'm just letting you know I'm
back as well and am happy to respond to any concerns regarding v4 when
you get all caught up.
I hope you had a relaxing holiday :)
Thanks,
Will
On Fri, Dec 18, 2020 at 4:01 AM Jessica Yu wrote:
>
> +++ Will McVicker
On Tue, 2021-01-05 at 14:05 +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 05, 2021 at 06:25:14PM +0530, Jeffrin Jose T wrote:
> > On Mon, 2021-01-04 at 16:56 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.5
> > > release.
> > > There are 63
On Tue, Jan 5, 2021 at 7:48 PM Liang Li wrote:
>
> Some key parameters for page reporting are now hard coded, different
> users of the framework may have their special requirements, make
> these parameter configrable and let the user decide them.
>
> Cc: Alexander Duyck
> Cc: Mel Gorman
> Cc:
> The "Timeout: Not all CPUs entered broadcast exception handler" message
> will appear from time to time given enough systems, but this message does
> not identify which CPUs failed to enter the broadcast exception handler.
> This information would be valuable if available, for example, in order
On Wed, Jan 06, 2021 at 09:41:02AM -0800, Paul E. McKenney wrote:
> The "Timeout: Not all CPUs entered broadcast exception handler" message
> will appear from time to time given enough systems, but this message does
> not identify which CPUs failed to enter the broadcast exception handler.
> This
Use my @google.com address in MAINTAINERS, somehow only the .mailmap
entry was added when the original update patch was applied.
Fixes: c2b1209d852f ("MAINTAINERS: Update email address for Sean
Christopherson")
Cc: k...@vger.kernel.org
Reported-by: Nathan Chancellor
Signed-off-by: Sean
On Wed, 2021-01-06 at 18:52 +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 06, 2021 at 07:43:42PM +0200, Filip Kolev wrote:
> > On 06-Jan-21 09:51, Greg Kroah-Hartman wrote:
> > > On Tue, Jan 05, 2021 at 10:29:18PM +0200, Filip Kolev wrote:
> > > > There is a debug message using hardcoded
Deinterlace core is completely compatible to H3.
Add a node for it.
Signed-off-by: Jernej Skrabec
---
Note: I didn't add H5 fallback, since the only reason why this node
is not in common H3/H5 dtsi is that it's located on different addresses.
If anyone feel fallback compatible is needed, I'll
On Wed, Jan 06, 2021, Maxim Levitsky wrote:
> If migration happens while L2 entry with an injected event to L2 is pending,
> we weren't including the event in the migration state and it would be
> lost leading to L2 hang.
But the injected event should still be in vmcs12 and
05.01.2021 06:47, Chanwoo Choi пишет:
> You might remove the 'devm_pm_opp_remove_all_dynamic(>dev)
> under ' remove_opp' goto statement.
Good catch, thank you.
On 2021-01-06 8:17 a.m., Bharat Bhushan wrote:
Hi Ankur,
We are observing below BUG_ON() with latest kernel
[10011.321645] [ cut here ]
[10011.322262] kernel BUG at mm/memory.c:1816!
[10011.323793] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
checkpatch.pl emits the following warning:
WARNING: Prefer using '"%s...", __func__' to using 'ov2722_remove', this
function's name, in a string
+ dev_dbg(>dev, "ov2722_remove...\n");
This is just a "trace" call and therefore should be removed entirely;
ftrace should be used instead.
These two patches add support for deinterlace core found on R40. It's
compatible to H3 one, so only DT node is needed.
Please take a look.
Best regards,
Jernej
Jernej Skrabec (2):
dt-bindings: media: Add Allwinner R40 deinterlace compatible
ARM: dts: sun8i: r40: Add deinterlace node
R40 contains deinterlace core compatible to that in H3. One peculiarity
is that RAM gate is shared with CSI1. User manual states it's separate
but that's not true. Shared gate was verified with BSP Linux code check
and with runtime tests (CPU crashed if CSI1 gate was not ungated).
Signed-off-by:
Allwinner R40 SoC also contains deinterlace core, compatible to H3.
Add compatible string for it.
Signed-off-by: Jernej Skrabec
---
.../bindings/media/allwinner,sun8i-h3-deinterlace.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git
On Tue, Jan 05, 2021 at 12:01:37PM +0100, SeongJae Park wrote:
> From: SeongJae Park
>
> SeongJae Park (5):
> xen/xenbus: Allow watches discard events before queueing
> xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path()
> xen/xenbus/xen_bus_type: Support will_handle
On Wed, Jan 06, 2021, Maxim Levitsky wrote:
> This is VMX version of the same issue as I reproduced on SVM.
>
> Unlike SVM, this version has 2 pending issues to resolve.
>
> 1. This seems to break 'vmx' kvm-unit-test in
> 'error code <-> (!URG || prot_mode) [+]' case.
>
> The test basically
On 06.01.2021 18:56, Ben Gardon wrote:
On Wed, Jan 6, 2021 at 9:37 AM Maciej S. Szmigiero
wrote:
On 06.01.2021 18:28, Ben Gardon wrote:
On Wed, Jan 6, 2021 at 1:26 AM Maciej S. Szmigiero
wrote:
Thanks for looking at it Ben.
On 06.01.2021 00:38, Ben Gardon wrote:
(..)
+Sean
patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Tony-Lindgren/Lost-key-up-interrupt-handling-for-omap4-keypad/20210106-210045
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
On 1/6/21 6:36 AM, Peter Zijlstra wrote:
> When the compiler fails to inline; we violate nonisntr:
>
> vmlinux.o: warning: objtool: __sev_es_nmi_complete()+0xc7: call to
> sev_es_wr_ghcb_msr() leaves .noinstr.text section
I am still seeing (a variant of) this one:
vmlinux.o: warning:
On Wed, Jan 6, 2021 at 9:37 AM Maciej S. Szmigiero
wrote:
>
> On 06.01.2021 18:28, Ben Gardon wrote:
> > On Wed, Jan 6, 2021 at 1:26 AM Maciej S. Szmigiero
> > wrote:
> >>
> >> Thanks for looking at it Ben.
> >>
> >> On 06.01.2021 00:38, Ben Gardon wrote:
> >> (..)
> >>>
> >>> +Sean
On Wed, Jan 06, 2021 at 11:47:23AM +0200, Georgi Djakov wrote:
> Hello Greg,
>
> Here is a pull request with a few interconnect fixes for 5.11-rc.
> More details are available in the signed tag. Please take them into
> char-misc-linus when possible. The patches have been in linux-next
> during
On Wed, Jan 06, 2021 at 03:49:46PM +, Valentin Schneider wrote:
> On 06/01/21 16:44, Peter Zijlstra wrote:
> > On Wed, Jan 06, 2021 at 06:46:21AM -0800, Paul E. McKenney wrote:
> >> What would break if I made the code dump out a few entries in the
> >> runqueue if the warning triggered?
> >
>
On Tue, Dec 29, 2020 at 11:56 AM Joe Perches wrote:
>
> On Fri, 2020-12-25 at 13:19 -0700, Jim Cromie wrote:
> > Well, we're mostly overeating, but we can all look forward to a diet
> > in January. And more exersize.
> >
> > dyndbg's compiled-in data-table currently uses 56 bytes per prdebug;
>
On Wed, Jan 06, 2021 at 07:43:42PM +0200, Filip Kolev wrote:
>
>
> On 06-Jan-21 09:51, Greg Kroah-Hartman wrote:
> > On Tue, Jan 05, 2021 at 10:29:18PM +0200, Filip Kolev wrote:
> > > There is a debug message using hardcoded function name instead of the
> > > __func__ macro. Replace it.
> > >
>
On Wed, Jan 06, 2021 at 03:07:24PM +, Ionela Voinescu wrote:
> > > > 367switch ((u64)reg->address) {
> >
> > That's not a dereference but I guess sparse complains of dropping the
> > __iomem. We could change the cast to (__force u64) to silence sparse.
Oh, yes, it is - that of
[Re: [PATCH RFC cpumask 4/5] cpumask: Add "last" alias for cpu list
specifications] On 06/01/2021 (Wed 10:49) Peter Zijlstra wrote:
> On Tue, Jan 05, 2021 at 04:49:55PM -0800, paul...@kernel.org wrote:
> > From: Paul Gortmaker
> >
> > It seems that a common configuration is to use the 1st
On Wed, Jan 06, 2021 at 05:20:34PM +, Will Deacon wrote:
> I've managed to reproduce the corruption on my AMD Seattle board (8x A57).
> I haven't had a chance to dig deeper yet, but here's the recipe which works
> for me:
>
> 1. I'm using GCC 4.9.4 simply to try to get as close as I can to
On 1/6/21 1:51 AM, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> The dev_close() call was added in commit c9eb3e0f8701 ("net: dsa: Add
> support for learning FDB through notification") "to indicate inconsistent
> situation" when we could not delete an FDB entry from the port.
>
> bridge
On 06-Jan-21 09:51, Greg Kroah-Hartman wrote:
On Tue, Jan 05, 2021 at 10:29:18PM +0200, Filip Kolev wrote:
There is a debug message using hardcoded function name instead of the
__func__ macro. Replace it.
Report from checkpatch.pl on the file:
WARNING: Prefer using '"%s...", __func__' to
On 1/6/21 1:51 AM, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> Currently the bridge emits atomic switchdev notifications for
> dynamically learnt FDB entries. Monitoring these notifications works
> wonders for switchdev drivers that want to keep their hardware FDB in
> sync with the
David Howells wrote:
> How about this?
> ...
> Fix the second loop so that it doesn't encode the size and type of an
> unsupported token, but rather just ignore it as does the first loop.
Actually, a better way is probably just to error out in this case. This
should only happen if a
On 1/6/21 5:22 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> BCM4908 seems to have slightly different registers but works when
> programmed just like the STB one.
>
> Signed-off-by: Rafał Miłecki
Acked-by: Florian Fainelli
--
Florian
The "Timeout: Not all CPUs entered broadcast exception handler" message
will appear from time to time given enough systems, but this message does
not identify which CPUs failed to enter the broadcast exception handler.
This information would be valuable if available, for example, in order to
Hi,
some related work caused me to look at how we use get/put_mems_online() and
get/put_online_cpus() during kmem cache creation/descruction/shrinking, and
realize that it should be actually safe to remove all of that with rather small
effort (as e.g. Michal Hocko suspected in some of the past
Commit e4f8e513c3d3 ("mm/slub: fix a deadlock in show_slab_objects()") has
fixed a problematic locking order by removing the memory hotplug lock
get/put_online_mems() from show_slab_objects(). During the discussion, it was
argued [1] that this is OK, because existing slabs on the node would
Since commit 03afc0e25f7f ("slab: get_online_mems for
kmem_cache_{create,destroy,shrink}") we are taking memory hotplug lock for SLAB
and SLUB when creating, destroying or shrinking a cache. It is quite a heavy
lock and it's best to avoid it if possible, as we had several issues with
lockdep
SLAB has been using get/put_online_cpus() around creating, destroying and
shrinking kmem caches since 95402b382901 ("cpu-hotplug: replace per-subsystem
mutexes with get_online_cpus()") in 2008, which is supposed to be replacing
a private mutex (cache_chain_mutex, called slab_mutex today) with
On Wed, Jan 06, 2021, Maxim Levitsky wrote:
> This should prevent bad things from happening if the user calls the
> KVM_SET_NESTED_STATE twice.
This doesn't exactly inspire confidence, nor does it provide much help to
readers that don't already know why KVM should "leave nested" before processing
There are two registers which can set the load capacitance for
XTAL1 and XTAL2. These are optional registers when using an
external crystal. Update the bindings to support them.
Signed-off-by: Adam Ford
---
.../devicetree/bindings/clock/idt,versaclock5.yaml | 12
1 file changed,
There are two registers which can set the load capacitance for
XTAL1 and XTAL2. These are optional registers when using an
external crystal. Parse the device tree and set the
corresponding registers accordingly.
Signed-off-by: Adam Ford
---
drivers/clk/clk-versaclock5.c | 64
From: Dexuan Cui Sent: Tuesday, December 22, 2020 4:12 PM
>
> When a Linux VM runs on Hyper-V, if the host toolstack doesn't support
> hibernation for the VM (this happens on old Hyper-V hosts like Windows
> Server 2016, or new Hyper-V hosts if the admin or user doesn't declare
> the hibernation
On 06.01.2021 18:28, Ben Gardon wrote:
On Wed, Jan 6, 2021 at 1:26 AM Maciej S. Szmigiero
wrote:
Thanks for looking at it Ben.
On 06.01.2021 00:38, Ben Gardon wrote:
(..)
+Sean Christopherson, for whom I used a stale email address.
.
I tested this series by running kvm-unit-tests on an
> -Original Message-
> From: Long Li
> Sent: Tuesday, January 5, 2021 8:16 PM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; Wei Liu ; David S. Miller
> ; Jakub Kicinski ; linux-
> hyp...@vger.kernel.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Cc: Long
From: Akira Yokosawa
This is a revert of commit 1947bfcf81a9 ("tools/memory-model: Add types
to litmus tests") with conflict resolutions.
klitmus7 [1] is aware of default types of "int" and "int*".
It accepts litmus tests for herd7 without extra type info unless
non-"int" variables are
From: Akira Yokosawa
klitmus7 of herdtools7 7.48 or earlier depends on ACCESS_ONCE(),
which was removed in Linux v4.15.
Fix the obvious typo in the table.
Fixes: d075a78a5ab1 ("tools/memory-model/README: Expand dependency of klitmus7")
Signed-off-by: Akira Yokosawa
Signed-off-by: Paul E.
From: "Paul E. McKenney"
This commit explicitly makes the connection between acquire loads and
the reads-from relation. It also adds an entry for happens-before,
and refers to the corresponding section of explanation.txt.
Reported-by: Boqun Feng
Signed-off-by: Paul E. McKenney
---
> -Original Message-
> From: Long Li
> Sent: Tuesday, January 5, 2021 8:16 PM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; Wei Liu ; David S. Miller
> ; Jakub Kicinski ; linux-
> hyp...@vger.kernel.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Cc: Long
> -Original Message-
> From: Long Li
> Sent: Tuesday, January 5, 2021 8:16 PM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; Wei Liu ; David S. Miller
> ; Jakub Kicinski ; linux-
> hyp...@vger.kernel.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Cc: Long
From: Marco Elver
Rewrite kcsan_prandom_u32_max() to not depend on code that might be
instrumented, removing any dependency on lib/random32.c. The rewrite
implements a simple linear congruential generator, that is sufficient
for our purposes (for udelay() and skip_watch counter randomness).
The
Hello!
This series provides a few LKMM updates:
1. tools/memory-model: Tie acquire loads to reads-from.
2. tools/memory-model: Remove redundant initialization in litmus
tests, courtesy of Akira Yokosawa.
3. tools/memory-model: Fix typo in klitmus7 compatibility table,
From: Marco Elver
Re-enable KCSAN instrumentation, now that KCSAN no longer relies on code
in lib/random32.c.
Signed-off-by: Marco Elver
Signed-off-by: Paul E. McKenney
---
lib/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lib/Makefile b/lib/Makefile
index afeff05..dc09208
From: "Paul E. McKenney"
This commit saves a few lines of code by creating a doyesno helper bash
function for argument parsing.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 78 ++-
1 file changed, 19 insertions(+), 59 deletions(-)
From: "Paul E. McKenney"
This commit causes torture.sh to check for zero-length runs and to take
the cowardly option of refusing to run them, logging its cowardice for
later inspection.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 25
Hello!
This series provides KCSAN updates involving random32.
1. Rewrite kcsan_prandom_u32_max() without prandom_u32_state(),
courtesy of Marco Elver.
2. Re-enable KCSAN instrumentation, courtesy of Marco Elver.
Thanx, Paul
From: "Paul E. McKenney"
This commit causes torture.sh to use the torture.verbose_sleep_frequency
kernel boot parameter to throttle verbose refscale output on large systems.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 2 +-
1 file changed, 1
From: "Paul E. McKenney"
This commit places "---" markers in the torture.sh script's allmodconfig
output, and uses "<<" to avoid overwriting earlier output from this
build test.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 9 ++---
1 file
From: "Paul E. McKenney"
The sizes of vmlinux files built with KASAN enabled can approach a full
gigabyte, which can result in disk overflow sooner rather than later.
Fortunately, the xz command compresses them by almost an order of
magnitude. This commit therefore uses xz to compress vmlinux
From: "Paul E. McKenney"
This commit adds the command and arguments to the torture.sh log file, and
also outputs the results directory. This latter allows impatient users
to quickly find the results that are being generated by the current run.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
Now that kvm.sh puts all the relevant details in the "log" file,
there is no need for torture.sh to generate a separate "log.long"
file. This commit therefore drops this from torture.sh.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
On large systems, the refscale printk() rate can overrun the file system's
ability to accept console log messages. This commit therefore uses the
new verbose_batched module parameter to rate-limit some of the higher-rate
printk() calls.
Signed-off-by: Paul E. McKenney
From: "Paul E. McKenney"
The .mod.c files created by allmodconfig builds interfers with the approach
torture.sh uses to enumerate types of rcuscale and refscale runs. This
commit therefore tightens the pattern matching to avoid this interference.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
This commit uncomments the argument checking for the --duration argument
to torture.sh. While in the area, it also corrects the duration units
from seconds to minutes.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 10
From: "Paul E. McKenney"
This commit improves torture.sh flexibility by autoscaling the number
of CPUs to be used in variable-CPUs torture tests, including scftorture,
refscale, rcuscale, and kvfree.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 19
From: "Paul E. McKenney"
This commit adds --configs-rcutorture, --configs-locktorture, and
--configs-scftorture arguments to torture.sh, allowing the desired
set of scenarios to be passed to each. The default for each has been
changed from a large-system-appropriate set to just CFLIST for each.
From: "Paul E. McKenney"
In 2020, running KCSAN often requires careful choice of compiler.
This commit therefore adds a --kcsan-kmake-arg parameter to torture.sh
to allow specifying (for example) "CC=clang" to the kernel build process
to correctly build a KCSAN-enabled kernel.
Signed-off-by:
From: "Paul E. McKenney"
This commit adds the ability to do "make allmodconfig" to torture.sh,
given that normal rcutorture runs do not normally catch missing exports.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 37 ++-
1 file
From: "Paul E. McKenney"
Although tailoring a specific set of kvm.sh runs has served rcutorture
testing well over many years, it requires a relatively distraction-free
environment, which is not always available. This commit therefore
adds a prototype torture.sh script that by default tortures
From: "Paul E. McKenney"
The bash "eval" command enables Bobby Tables attacks, which might not
be a concern in torture testing by themselves, but one could imagine
these combined with a cut-and-paste attack. This commit therefore gets
rid of them. This comes at a price in terms of bash quoting
From: "Paul E. McKenney"
This commit makes torture.sh use the new bash functions get_starttime()
and get_starttime_duration() created for kvm.sh.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/torture.sh | 20 +++-
1 file changed, 7 insertions(+),
From: "Paul E. McKenney"
Currently, if a scenario is repeated as in "--configs '4*TREE01'",
the Kconfig analysis is performed for each occurrance (four times in
this example) and each analysis places the exact same data into the
exact same files. This is not really an issue in this
Hello!
This series adds a script to run a full set of tests. My earlier practice
of testing just what changed proved inappropriate for the high-distraction
environment of a few months ago.
1. Do Kconfig analysis only once per scenario.
2. Add torture.sh torture-everything script.
3.
On Wed, Jan 6, 2021 at 1:26 AM Maciej S. Szmigiero
wrote:
>
> Thanks for looking at it Ben.
>
> On 06.01.2021 00:38, Ben Gardon wrote:
> (..)
> >
> > +Sean Christopherson, for whom I used a stale email address.
> > .
> > I tested this series by running kvm-unit-tests on an Intel Skylake
> >
On Wed, Jan 06, 2021, Maxim Levitsky wrote:
> The code to store it on the migration exists, but no code was restoring it.
>
> Signed-off-by: Maxim Levitsky
> ---
> arch/x86/kvm/svm/nested.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/x86/kvm/svm/nested.c
From: "Paul E. McKenney"
Yes, you can mentally subtract the timestamps, but this commit makes
the computer do this work.
Signed-off-by: Paul E. McKenney
---
.../testing/selftests/rcutorture/bin/functions.sh | 33 ++
tools/testing/selftests/rcutorture/bin/kvm.sh | 6
From: "Paul E. McKenney"
Currently, passing something like "--kconfig CONFIG_NR_CPUS=2" to kvm.sh
has no effect on scenario scheduling. For scenarios that do not specify
the number of CPUs, this can result in kvm.sh wastefully scheduling only
one scenario at a time even when the --kconfig
From: "Paul E. McKenney"
Currently, if a scenario is repeated as in "--configs '4*TREE01'",
the Kconfig analysis is performed for each occurrance (four times in
this example) and each analysis places the exact same data into the
exact same files. This is not really an issue in this
From: "Paul E. McKenney"
Given that kvm.sh in invoked from scripts, it is only natural for
different levels of scripting to provide their own Kconfig option values,
for example. Unfortunately, right now, the last such argument on the
command line wins.
This commit therefore makes the
From: "Paul E. McKenney"
Commit 757055ae8ded ("init/console: Use ttynull as a fallback when
there is no console") results in the string "Warning: Failed to add
ttynull console. No stdin, stdout, and stderr for the init process!"
appearing on the console, which the rcutorture scripting interprets
From: "Paul E. McKenney"
When all of the remote systems have the same number of CPUs, one
approach is to use one "--buildonly" run and one "--dryrun sched" run,
and then distributing the batches out one per remote system. However,
the output of "--dryrun sched" is not made for parsing, so this
From: "Paul E. McKenney"
This commit adds the test summary to the end of the log in the top-level
directory containing the kvm.sh test artifacts. While in the area, it adds
the kvm.sh exit code to this test summary.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
Normally, kvm-recheck.sh is run from kvm.sh, which provides the
TORTURE_TRUST_MAKE environment variable that, if a non-empty string,
indicates that the --trust-make command-line parameter has been passed
to kvm.sh. If there was no --trust-make, kvm-recheck.sh insists
From: "Paul E. McKenney"
By default, the "panic" kernel parameter is zero, which causes the kernel
to loop indefinitely after a panic(). The rcutorture scripting will
eventually kill the corresponding qemu process, but only after waiting
for the full run duration plus a few minutes. This
From: "Paul E. McKenney"
Currently, the "date" command producing the output on the kvm.sh "Test
Summary" line is executed at the beginning of the test, which produces a
date that is less than helpful to someone wanting to know the duration
of the test. This commit therefore defers this
From: "Paul E. McKenney"
The kvm.sh script uses kvm-find-errors.sh to evaluate whether or not
a build failed. Unfortunately, kvm-find-errors.sh returns success if
there are no failed runs (including when there are no runs at all) even if
there are build failures. This commit therefore makes
From: Frederic Weisbecker
The rcutorture scripts' identify_qemu_vcpus() function expects `lscpu`
to have a "CPU: " line, for example:
CPU(s): 8
But different local language settings can give different results:
Processeur(s) : 8
As a result,
From: "Paul E. McKenney"
This commit changes the "STOP" file that is used to cleanly halt a running
rcutorture run to "STOP.1" because no scenario directory will ever end
with ".1". If there really was a scenario named "STOP", its directories
would instead be named "STOP", "STOP.2", "STOP.3",
From: "Paul E. McKenney"
This commit adds a config2csv.sh script that converts the specified
torture-test scenarios' Kconfig options and kernel-boot parameters to
.csv format. This allows easier comparison of scenarios when one fails
and another does not.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
This commit simplifies exit-code plumbing. It makes kvm-recheck.sh return
the value 1 for a build error and 2 for a runtime error. It also makes
kvm-find-errors.sh avoid checking runtime files for --build-only runs.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
Distributed execution of rcutorture is eased if the qemu execution can
be split from the building of the kernel, as this allows target systems
to be used that are not set up to build kernels. It also avoids issues
with toolchain version skew across the cluster, aside of
From: "Paul E. McKenney"
Knowing the number of builds that kvm.sh will split a run into allows
estimation of the duration of a test, give or take build duration.
This commit therefore adds a line of output to "--dryrun sched" that
gives the number of builds that will be run. This excludes
From: "Paul E. McKenney"
Scripts like kvm-check-branches.sh group runs under a single directory
in resdir in order to allow easier retrospective analysis. However, they
do this by letting kvm.sh create a directory as usual and then moving it
after the run. This can be very confusing when
From: "Paul E. McKenney"
The --kcsan argument to kvm.sh adds CONFIG_KCSAN_VERBOSE=y in order to
get more detail from the KCSAN reports. However, this Kconfig option
requires lockdep to be enabled. This commit therefore causes --kcsan
to also enable lockdep.
Signed-off-by: Paul E. McKenney
501 - 600 of 1126 matches
Mail list logo
