Unbalanced calls to imx_ssi_trigger() may result in endless
SSI activity and thus provoke eternal sound. While on the first glance,
the switch statement looks pretty symmetric, the SUSPEND/RESUME
pair is not: the suspend case comes along snd_pcm_suspend_all(),
which for fsl/imx-pcm-fiq is called
Hi,
On Fri, Nov 15, 2013 at 03:56:22PM -0800, Grant Grundler wrote:
> From: Stephen Hurd
>
> Add two new quirks needed by BCM57785 card reader:
> SDHCI_QUIRK2_BROKEN_UHS:
> Disables all UHS modes.
This seems appropriate. You _could_ use SDHCI_QUIRK_MISSING_CAPS and
hardcode them instead,
On Fri, Nov 15, 2013 at 12:56:04PM +1100, Stephen Rothwell wrote:
> Hi Dan,
>
> Today's linux-next merge of the dmaengine tree got a conflict in
> drivers/dma/dmatest.c between commit 19e9f99f273b ("dmaengine: dmatest:
> use DMA_COMPLETE for dma completion status") from the slave-dma tree and
>
On Thu, Nov 14, 2013 at 03:50:40PM +0100, Miroslav Lichvar wrote:
> include/linux/timekeeper_internal.h | 4 +
> kernel/time/timekeeping.c | 209
> +---
> 2 files changed, 31 insertions(+), 182 deletions(-)
This looks like an impressive
Hi,
[PATCH 3/3] usb: storage: uas: Proper cmd result assignment
This change replaces DID_ABORT with DID_TIMEOUT as a command result
whenever US_FLIDX_TIMED_OUT bit is set.
This change is made to bring USB storage inline with a recent change:
commit18a4d0a22ed6c54b67af7718c305cd010f09ddf8
Hi,
[PATCH 2/3] keucr: Proper cmd result assignment
This change replaces DID_ABORT with DID_TIMEOUT as a command result
whenever US_FLIDX_TIMED_OUT bit is set.
This change is made to bring USB storage inline with a recent change:
commit18a4d0a22ed6c54b67af7718c305cd010f09ddf8
[SCSI]
Hi,
Here are the updated patches:
[PATCH 1/3] usb: storage: Proper cmd result assignment
This change replaces DID_ABORT with DID_TIMEOUT as a command result
whenever US_FLIDX_TIMED_OUT bit is set.
This change is made to bring USB storage inline with a recent change:
commit
On 11/15/2013 04:01 PM, Taras Kondratiuk wrote:
From: Victor Kamensky
All OMAP IP blocks expect LE data, but CPU may operate in BE mode.
Need to use endian neutral functions to read/write h/w registers.
I.e instead of __raw_read[lw] and __raw_write[lw] functions code
need to use
We should use f2fs_put_page to release page for uniform style of f2fs code.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index aa3438c..076a60c 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
For better read performance, we add a new function to support for merging
contiguous read as the one for write.
v1-->v2:
o add declarations here as Gu Zheng suggested.
Signed-off-by: Chao Yu
Acked-by: Gu Zheng
---
fs/f2fs/data.c | 45 +
Previously we read sit entries page one by one, this method lost the chance of
reading contiguous page together.
So we read pages as contiguous as possible for better mount performance.
v1-->v2:
o merge judgements/use 'Continue' or 'Break' instead of 'Goto' as Gu Zheng
suggested.
o add
On 11/15/2013 06:12 PM, Viresh Kumar wrote:
This patch adds PM notifiers for handling suspend/resume of cpufreq governors.
This is required for early suspend and late resume of governors.
There are multiple reasons that support this patch:
- Firstly it looks very much logical to stop governors
In deadline scheduler, in a FIFO list when a request insert it and
other request remove it in the same time,whether it make conflict???
Whether it need lock??
Thank you!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Friday 15 November 2013 04:24 PM, Viresh Kumar wrote:
> Though the patch I have sent fixes a problem similar to this but I don't think
> patch of any of us will solve the issue Rainer is facing..
>
> I checked his system configuration and its like this:
> - Four CPUs, all having separate clock
On Saturday 16 November 2013 06:40 AM, Rafael J. Wysocki wrote:
> On Friday, November 15, 2013 06:20:43 PM Nishanth Menon wrote:
>> So, instead of having a statistics information that never ever
>> reflects valid data in the mentioned case and scratching our heads, we
>> instead, refuse to
Hello,
On Fri, Nov 15, 2013 at 09:53:14AM -0500, Don Morris wrote:
> Are we getting some other thread from while_each_task()
> repeatedly keeping us in the loop? Or is there something
> else going on? The gut instinct is that calling something
> like while_each_task() on an exiting thread would
Hello, Bjorn.
On Fri, Nov 15, 2013 at 05:28:20PM -0700, Bjorn Helgaas wrote:
> It would be better to fix PCI so we don't call VF driver .probe() methods
> from inside a PF driver .probe() method, but that's a bigger project.
Yeah, if pci doesn't need the recursion, we can simply revert restore
于 2013/11/16 8:40, Paul E. McKenney 写道:
> From: "Paul E. McKenney"
>
> The sparse checking for rcu_assign_pointer() was recently upgraded
> to reject non-__kernel address spaces. This also rejects __rcu,
> which is almost always the right thing to do. However, the uses in
>
On 11/15/2013 06:22 PM, Viresh Kumar wrote:
On 15 November 2013 13:45, Lan Tianyu wrote:
Currently, governor of nonboot cpus will be put to EXIT when system suspend.
Since all these cpus will be unplugged and the governor usage_count decreases
to zero. The governor data and its sysfs
On Saturday 16 November 2013 05:54 AM, Rafael J. Wysocki wrote:
> Will cpufreq work during system-wide power transitions (suspend/resume etc.)
> after this? In particular, what about hibernation?
I am disabling governors as soon as we start suspend. So No, cpufreq wouldn't
work during
On 11/15/2013 12:58 PM, Markus Mayer wrote:
This commit adds support for the watchdog timer used on the BCM281xx
family of SoCs.
Signed-off-by: Markus Mayer
You are using two different e-mail addresses, the one here and the one in
MODULE_AUTHOR.
Any chance to use only one ? Of course, there
On 11/16/2013 08:38 AM, Rafael J. Wysocki wrote:
On Friday, November 15, 2013 04:15:34 PM Lan Tianyu wrote:
Currently, governor of nonboot cpus will be put to EXIT when system suspend.
Since all these cpus will be unplugged and the governor usage_count decreases
to zero. The governor data and
On Fri, Nov 15, 2013 at 06:01:20PM -0800, Greg KH wrote:
> On Fri, Nov 15, 2013 at 08:47:27PM -0500, Steven Rostedt wrote:
> > On Fri, 15 Nov 2013 17:21:16 -0800
> > "Paul E. McKenney" wrote:
> >
> >
> > > > Oh, one very minor comment on the patches, you should delete the address
> > > > of the
On many development platforms, at boot, the bootloader configured
frequency maynot match the valid frequencies that are stated to be
supported in OPP table. This may occur due to various reasons:
a) older or default bootloader in development platform without latest
updates
b) SoC documentation
On Fri, Nov 15, 2013 at 2:59 PM, Yinghai Lu wrote:
> On Wed, Nov 13, 2013 at 5:57 PM, Ethan Zhao wrote:
>> On Wed, Nov 6, 2013 at 10:49 PM, ethan.zhao wrote:
>>> Though no specification about NumVFs register initial value after POST, to
>>> void the confusion
>>> lspci output as following
[ This was in my spam collection. I don't quite know why, but it might
signify problems with your email setup. Quite often, when gmail is
unhappy about kernel developer emails, it's been because their email
provider ends up doing something odd.
But the headers actually have "spf=pass" and
On Fri, Nov 15, 2013 at 08:47:27PM -0500, Steven Rostedt wrote:
> On Fri, 15 Nov 2013 17:21:16 -0800
> "Paul E. McKenney" wrote:
>
>
> > > Oh, one very minor comment on the patches, you should delete the address
> > > of the FSF from your file headers, unless you want to track the office
> > >
Quoting Boris BREZILLON (2013-10-13 10:17:10)
> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
> index 73bdb69..942811d 100644
> --- a/include/linux/clk-provider.h
> +++ b/include/linux/clk-provider.h
...
> @@ -194,6 +204,7 @@ struct clk_hw {
> struct clk_fixed_rate {
>
On Fri, 15 Nov 2013 17:21:16 -0800
"Paul E. McKenney" wrote:
> > Oh, one very minor comment on the patches, you should delete the address
> > of the FSF from your file headers, unless you want to track the office
> > movements of them for the next 40+ years. We've been removing them from
> >
From: Petko Manolov
Date: Fri, 15 Nov 2013 12:23:44 +0200
> From: Petko Manolov
> Date: Fri, 15 Nov 2013 11:51:54 +0200
> Subject: [PATCH] Update Pegasus and RTL8150 repositories;
Do not include this metadata in your patch postings, it duplicates
the commit header line when people try to apply
On Fri, Nov 15, 2013 at 05:05:28PM -0800, Greg KH wrote:
> On Fri, Nov 15, 2013 at 04:35:14PM -0800, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > This commit adds the test framework that I used to test RCU under KVM.
> > This consists of a group of scripts and Kconfig fragments.
On Fri, 15 Nov 2013 17:02:36 -0800
Stephen Boyd wrote:
> On 11/15/13 06:36, Steven Rostedt wrote:
> > diff --git a/scripts/tags.sh b/scripts/tags.sh
> > index 74f02e4..b985371 100755
> > --- a/scripts/tags.sh
> > +++ b/scripts/tags.sh
> > @@ -218,7 +218,7 @@ exuberant()
> >
> > emacs()
> > {
On Tuesday, November 12, 2013 11:48:19 AM Mika Westerberg wrote:
> Some recent Intel PCHs with LPSS have different ACPI IDs for the LPSS
> devices, so add these to the list as well.
>
> Signed-off-by: Mika Westerberg
Queued up for the next ACPI pull request, thanks!
> ---
>
On Wednesday, November 13, 2013 11:27:42 AM Lan Tianyu wrote:
> Now the pointer of struct acpi_device can be got by
> ACPI_COMPANION(struct acpi_ac->pdev->dev). So the pointer
> is not necessary and remove it.
>
> Signed-off-by: Lan Tianyu
Queued up for the next ACPI pull request, thanks!
--
-- Forwarded message --
From: 韩磊
Date: 2013/11/15
Subject: A problem about IO scheduler in kernel
To: Linux Kernel Mailing List
These days I was programming about IO scheduler called
"Simple_Deadline" in kernel.
"Simple_Deadline" is based on "deadline-iosched".The algorithm is
On Fri, Nov 15, 2013 at 04:35:14PM -0800, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> This commit adds the test framework that I used to test RCU under KVM.
> This consists of a group of scripts and Kconfig fragments.
>
> Signed-off-by: Paul E. McKenney
> Cc: Greg KH
Yeah! Thanks
On 11/15/13 06:36, Steven Rostedt wrote:
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index 74f02e4..b985371 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -218,7 +218,7 @@ exuberant()
>
> emacs()
> {
> - all_target_sources | xargs $1 -a\
> +
On Fri, Nov 15, 2013 at 09:29:51AM -0700, David Ahern wrote:
> HI Frederic:
>
> On 11/13/13, 11:03 AM, Frederic Weisbecker wrote:
> >
> >I see. I can reproduce, I'll check and see what happens. It would be nice if
> >we could have an option to dump internal perf events like comm events as well
>
On Wednesday, November 13, 2013 03:39:23 PM Viresh Kumar wrote:
> With a recent change "d4019f0 cpufreq: move freq change notifications to
> cpufreq
> core" few variables (r & ret) are removed by mistake and hence these warnings:
>
> drivers/cpufreq/omap-cpufreq.c: In function omap_target:
>
On Friday, November 15, 2013 02:13:26 PM Viresh Kumar wrote:
> On 15 November 2013 11:24, Lan Tianyu wrote:
> > The related code has been changed and the comment is out of data.
> > So remove it.
> >
> > Signed-off-by: Lan Tianyu
> > ---
> > drivers/cpufreq/cpufreq_governor.c | 4
> > 1
On Friday, November 15, 2013 06:20:43 PM Nishanth Menon wrote:
> commit 46a310b ([CPUFREQ] Don't set stat->last_index to -1 if the
> pol->cur has incorrect value.) tries to handle case where policy->cur
> does not match any entry in freq_table.
>
> As indicated in the above commit, the exact
--
Vážení Web - Mail Majitel účtu:
To přišlo na naše upozornění , že vaše e-mailová neprošel ověření /
aktualizace proces, který jsme v současné době pracuje na . V současné
době modernizace naší databázi a e - mailový účet centrum , čímž Smazání
všech starých webový e-mail e-mailový účet
Quoting boris brezillon (2013-11-08 00:54:45)
> Hello Mike,
>
> On 08/11/2013 01:51, Mike Turquette wrote:
> > Quoting Boris BREZILLON (2013-10-13 10:17:10)
> >> +/**
> >> + * clk_get_accuracy - return the accuracy of clk
> >> + * @clk: the clk whose accuracy is being returned
> >> + *
> >> + *
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
dn_insert_route() is legitimate: It is assigning a pointer to an element
From: "Paul E. McKenney"
The rcu_assign_pointer() macro, as with most cpp macros, must not evaluate
its argument more than once. And it in fact does not. But this might
not be obvious to the casual observer, because one of the arguments
appears no less than three times. However, but one
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6_tnl_unlink() is legitimate: It is assigning a pointer to an element
From: Josh Triplett
rcu_assign_pointer needs to use ACCESS_ONCE to make the assignment to
the destination pointer volatile, to protect against compilers too
clever for their own good.
In addition, since rcu_assign_pointer force-casts the source pointer to
add the __rcu address space (overriding
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
bond_alb_handle_active_change() is legitimate: It is assigning a pointer
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ipip6_tunnel_unlink() is legitimate: It is assigning a pointer to an
From: "Paul E. McKenney"
There is currently no way to initialize a global RCU-protected pointer
without either putting up with sparse complaints or open-coding an
obscure cast. This commit therefore creates RCU_INITIALIZER(), which
is intended to be used as follows:
struct foo __rcu *p
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
__br_mdb_del() is legitimate: They are assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
notifier_chain_unregister() is legitimate: It is deleting an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
sta_info_hash_del() are legitimate: They are assigning a pointer to an
From: "Paul E. McKenney"
The --rcu-kvm argument was intended to allow the scripts to live in
an alternate location. Unfortunately, this prevents the kvm.sh script
from using common functions until after it finished parsing arguments,
because it doesn't know where to find them until then.
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
br_multicast_del_pg() and br_multicast_new_port_group() are legitimate:
From: "Paul E. McKenney"
Repeatedly running a given test, for example, by repeating the name
as in "--configs "TREE08 TREE08 TREE08" records the results only of
the last run of this test. This is because the earlier results are
overwritten by the later results.
This commit therefore checks for
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6gre_tunnel_unlink() is legitimate: It is assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
bond_change_active_slave() and __bond_release_one() are legitimate:
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip_ra_control() is legitimate: It is assigning a pointer to an element
Hello!
This series once again attempts to improve rcu_assign_pointer()'s
relationship with sparse.
1. Add a comment indicating that despite appearances,
rcu_assign_pointer() really only evaluates its arguments once,
as a cpp macro should.
2-13. Apply ACCESS_ONCE() to
From: "Paul E. McKenney"
Don't grab the configuration fragment from the configs directory because
it might well have been changed since the test was run. Instead, use
the ConfigFragment file that was placed in the results directory.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
The qemu -name argument doesn't seem to be useful in this environment,
so this commit removes it.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: "Paul E. McKenney"
The TINY_RCU test cases were first put in place many years ago, and have
been incrementally modified rather than being reworked. This commit
therefore completes a long-overdue reworking of the TINY_RCU test cases.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
.../testing/selftests/rcutorture/bin/functions.sh | 24 +
tools/testing/selftests/rcutorture/bin/kvm.sh | 25 +++---
2 files changed, 27 insertions(+), 22 deletions(-)
diff
From: "Paul E. McKenney"
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/rcutorture/bin/kvm.sh
b/tools/testing/selftests/rcutorture/bin/kvm.sh
index
From: "Paul E. McKenney"
This commit expands the checks for what architecture is running to generate
additional qemu-system- commands, then uses the resulting qemu-system-
command name to choose different qemu arguments as needed for different
architectures.
Signed-off-by: Paul E. McKenney
Cc:
From: "Paul E. McKenney"
This commits adds the --qemu-args argument to kvm.sh that is required
to pass boot devices down through to qemu.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm.sh | 16 +++-
1 file changed, 11 insertions(+), 5
From: "Paul E. McKenney"
The output of the rcutorture scripts often requires interpretation, so
this commit simplifies this interpretation by tagging messages as
BUGs (colored red) or WARNINGs (colored yellow).
Reported-by: Ingo Molnar
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
Some Kconfig fragments require rcutorture module parameters to
do optimal testing, for example, a configuration for SRCU would
need rcutorture.torture_type=srcu. This commit therefore adds a
per-Kconfig-fragment boot-parameter capability.
Signed-off-by: Paul E.
From: "Paul E. McKenney"
The commit uses configcheck.sh from within configinit.sh, replacing the
imperfect inline expansion that was there before.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
.../testing/selftests/rcutorture/bin/configinit.sh | 27 +-
1 file changed, 1
From: "Paul E. McKenney"
Use .boot facility to ease inclusion of SRCU into automated testing.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/configs/SRCU-N | 8
tools/testing/selftests/rcutorture/configs/SRCU-N.boot | 1 +
From: "Paul E. McKenney"
This commit adds the --no-initrd argument to kvm.sh, which permits
initrd to be contained in a root partition specified by the --bootargs
argument. Without --no-initrd, the kernel build expects an initrd
directory in the same rcutorture directory that contains bin and
From: "Paul E. McKenney"
This commit adds the --kmake-arg to kvm.sh, which allows passing in
things like "V=1" to see the build commands, as well as enabling the
CROSS_COMPILE= make macro used for cross-building.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
This commit drops no-longer-needed diagnostics from the output. Some of
them are retained in logfiles, in case they are ever needed.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
.../testing/selftests/rcutorture/bin/configinit.sh | 2 --
From: "Paul E. McKenney"
As it stands, the default kernel boot parameters generated from
the Kconfig fragment will override any supplied with the .boot
file that can optionally accompany a Kconfig fragment. Rearrange
ordering to permit the specific .boot arguments to override those
generated by
From: "Paul E. McKenney"
The TREE_RCU test cases were first put in place many years ago, and have
been incrementally modified rather than being reworked. This commit
therefore completes a long-overdue reworking of the TREE_RCU test cases.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
The v3.12 version of the kernel added the CONFIG_NO_HZ_FULL_SYSIDLE
Kconfig parameter, so this commit adds a version transition at that
point.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
.../selftests/rcutorture/configs/v3.12/CFLIST | 17
From: "Paul E. McKenney"
The TREE08 Kconfig fragment does not enable tracing, which is appropriate
for its test case. However, this can be inconvenient in cases where
TREE08 locates RCU bugs. This commit therefore adds a TREE08-T that
differs from TREE08 only in enabling CONFIG_RCU_TRACE.
From: "Paul E. McKenney"
The commit causes kvm.sh to invoke kvm-recheck.sh at the end of each
run, and causes kvm-recheck.sh to print only the name of the test, not
the full path to the corresponding Kconfig file.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
This commit adds --buildonly, which does the builds specified by the
--configs argument, but does not boot or test the resulting kernels.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh | 5 +
From: "Paul E. McKenney"
This commit allows easy specification of trace_event lists, among other
things.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm.sh | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
From: "Paul E. McKenney"
Different Kconfig parameters apply to different kernel versions, as
do different rcutorture module parameters. This commit allows the
rcutorture test scripts to adjust for different kernel versions.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
From: "Paul E. McKenney"
The task of working out which flavor of qemu to use gets more complex
as more types of CPUs are supported. Adding Power makes three in addition
to 32-bit and 64-bit x86, so it is time to pull this out into a function.
This commit therefore creates an identify_qemu
From: "Paul E. McKenney"
Allow datestamp to be specified to allow tests to be broken up and run
in parallel.
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
tools/testing/selftests/rcutorture/bin/kvm.sh | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git
From: "Paul E. McKenney"
Signed-off-by: Paul E. McKenney
Cc: Greg KH
---
.../selftests/rcutorture/bin/kvm-test-1-rcu.sh | 1 +
tools/testing/selftests/rcutorture/bin/kvm.sh | 9 ++-
.../rcutorture/configs/v0.0/N1-S-T-NH-SD-SMP-HP| 19 +++
Hello!
This series contains scripting that I use to test RCU under KVM, including
different Kconfig combinations to test, automated launching and monitoring
of multiple tests scenarios, kernel-version adaptation, and automated
evaluation of test output. This version works on x86 32- and 64-bit,
On Fri, Nov 15, 2013 at 01:58:05PM -0800, Linus Torvalds wrote:
> Ok, I finally got around to the random tree, but your proposed merge
> resolution makes no sense, so I didn't end up applying it.
>
> > - - r->entropy_total += nbits;
> > if (!r->initialized && nbits > 0) {
> > +
On Wed, Nov 13, 2013 at 04:38:06PM +0900, Tejun Heo wrote:
> Hey, guys.
>
> cc'ing people from "workqueue, pci: INFO: possible recursive locking
> detected" thread.
>
> http://thread.gmane.org/gmane.linux.kernel/1525779
>
> So, to resolve that issue, we ripped out lockdep annotation from
>
On Friday, November 15, 2013 04:15:34 PM Lan Tianyu wrote:
> Currently, governor of nonboot cpus will be put to EXIT when system suspend.
> Since all these cpus will be unplugged and the governor usage_count decreases
> to zero. The governor data and its sysfs interfaces will be freed or released.
From: "Signed-off-by: Fengguang Wu"
This commit fixes the following coccinelle warning:
kernel/rcu/tree.c:712:9-10: WARNING: return of 0/1 in function
'rcu_lockdep_current_cpu_online' with return type bool
Return statements in functions returning bool should use
true/false instead of 1/0.
From: Teodora Baluta
Function prototypes don't need to have the "extern" keyword since this
is the default behavior. Its explicit use is redundant. This commit
therefore removes them.
Signed-off-by: Teodora Baluta
Signed-off-by: Paul E. McKenney
---
include/linux/rculist.h | 4 +--
From: "Paul E. McKenney"
When an RCU CPU stall warning occurs, the CPU invokes resched_cpu() on
itself. This can help move the grace period forward in some situations,
but it would be even better to do this -before- the RCU CPU stall warning.
This commit therefore causes resched_cpu() to be
From: "Paul E. McKenney"
The current task-level idle entry/exit code forces an entry/exit on
each call, regardless of the nesting level. This commit therefore
properly accounts for nesting.
Signed-off-by: Paul E. McKenney
Reviewed-by: Frederic Weisbecker
---
kernel/rcu/tree.c | 14
From: Chen Gang
If the rcutorture SRCU output exceeds 4096 bytes, for example, if you
have more than about 75 CPUs, it will overflow the current statically
allocated buffer. This commit therefore replaces this static buffer
with a dynamically buffer whose size is based on the number of CPUs.
On Fri, Nov 15, 2013 at 05:16:31PM -0700, Shuah Khan wrote:
> On 11/15/2013 05:21 PM, Rafael J. Wysocki wrote:
> > On Friday, November 15, 2013 05:03:57 PM Shuah Khan wrote:
> >> device_wakeup_enable() uses dev_name(dev) as the wakeup source name.
> >> When it gets called with a device with its
From: "Paul E. McKenney"
Some RCU bugs have been specific to the layout of the rcu_node tree,
but RCU will silently adjust the tree at boot time if appropriate.
This obscures valuable debugging information, so print a message when
this happens.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
Each element of the rcu_state structure's ->levelspread[] array
is intended to contain the per-level fanout, where the zero-th
element corresponds to the root of the rcu_node tree, and the last
element corresponds to the leaves. In the CONFIG_RCU_FANOUT_EXACT
case, this
From: "Paul E. McKenney"
This commit documents the memory-barrier guarantees provided by
synchronize_srcu() and call_srcu().
Signed-off-by: Paul E. McKenney
---
kernel/rcu/srcu.c | 56 ---
1 file changed, 49 insertions(+), 7 deletions(-)
From: "Paul E. McKenney"
Currently blocking in an RCU callback function will result in
"scheduling while atomic", which could be triggered for any number
of reasons. To aid debugging, this patch introduces a rcu_callback_map
that is used to tie the inappropriate voluntary context switch back
to
From: Teodora Baluta
Function prototypes don't need to have the "extern" keyword since this
is the default behavior. Its explicit use is redundant. This commit
therefore removes them.
Signed-off-by: Teodora Baluta
Signed-off-by: Paul E. McKenney
---
kernel/rcu/rcu.h | 2 +-
1 file changed,
1 - 100 of 1134 matches
Mail list logo
