Because expedited CPU stall warnings are contained within the
kernel/rcu/tree_exp.h file, rcu_print_task_exp_stall() should live
there too. This commit carries out the required code motion.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree_exp.h| 32
kerne
Hi Tony,
On 3/26/19 6:13 PM, Tony Lindgren wrote:
> * Tony Lindgren [190325 22:00]:
>> We should not do the reset until the clocks are enabled. Let's only init
>> restctrl in sysc_init_resets() and do the reset later on in sysc_reset().
> ...
>
>> static int sysc_reset(struct sysc *ddata)
>> {
The RCU CPU stall-warning code for normal grace periods is currently
scattered across two files, due to earlier Tiny RCU support for RCU
CPU stall warnings and for old Kconfig options that have long since
been retired. Given that it is hard for the lead RCU maintainer to
find relevant stall-warnin
This commit completes the process of consolidating the code for RCU CPU
stall warnings for normal grace periods by moving the remaining such
code from kernel/rcu/tree.c to kernel/rcu/tree_stall.h.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree.c | 291 -
This commit further consolidates the stall-warning code by moving
print_cpu_stall_info() and its helper functions along with
zero_cpu_stall_ticks() to kernel/rcu/tree_stall.h.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree.h| 1 -
kernel/rcu/tree_plugin.h | 80 -
The RCU CPU stall-warning code for normal grace periods is currently
scattered across three files, due to earlier Tiny RCU support for RCU
CPU stall warnings and for old Kconfig options that have long since
been retired. Given that it is hard for the lead RCU maintainer to
find relevant stall-warn
Hello!
This series is primarily code movement for RCU CPU stall warnings.
If I am having a hard time finding the various scattered pieces of
this code, it is in need of consolidation!
1-3.Move RCU CPU stall-warning code into kernel/rcu/tree_stall.h.
4. Inline RCU task stall-warning help
> On Tue, Mar 26, 2019 at 02:25:52PM -0700, Huang, Kai wrote:
> > >
> > > That being said, this in no way impacts KVM's ability to virtualize SGX,
> > > e.g.
> > > KVM can directly do CPUID and {RD,WR}MSR to probe the capabilities
> > > of the platform as needed.
> >
> > I am not following. KVM ca
On 3/26/19 12:29 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.5 release.
There are 52 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made b
On 3/26/19 12:29 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.32 release.
There are 45 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 3/26/19 12:29 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.166 release.
There are 30 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
If someone fails to drain the corresponding SRCU callbacks (for
example, by failing to invoke srcu_barrier()) before invoking either
cleanup_srcu_struct() or cleanup_srcu_struct_quiesced(), the resulting
diagnostic is an ambiguous use-after-free diagnostic, and even then
only if you are running som
On 3/26/19 12:29 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.109 release.
There are 41 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be mad
The cleanup_srcu_struct_quiesced() function was added because NVME
used WQ_MEM_RECLAIM workqueues and SRCU did not, which meant that
NVME workqueues waiting on SRCU workqueues could result in deadlocks
during low-memory conditions. However, SRCU now also has WQ_MEM_RECLAIM
workqueues, so there is
Currently, the rcu_nocbs= kernel boot parameter requires that a specific
list of CPUs be specified, and has no way to say "all of them".
As noted by user RavFX in a comment to Phoronix topic 1002538, this
is an inconvenient side effect of the removal of the RCU_NOCB_CPU_ALL
Kconfig option. This co
On 3/26/19 3:39 PM, David Ahern wrote:
> On 3/26/19 9:30 AM, Dmitry Safonov wrote:
>> Fib trie has a hard-coded sync_pages limit to call synchronise_rcu().
>> The limit is 128 pages or 512Kb (considering common case with 4Kb
>> pages).
>>
>> Unfortunately, at Arista we have use-scenarios with full
Hello!
This series contains SRCU updates:
1. Check for in-flight callbacks in _cleanup_srcu_struct().
2. Remove cleanup_srcu_struct_quiesced().
Thanx, Paul
This commit changes a rcu_exp_handler() comment from rcu_preempt_defer_qs()
to rcu_preempt_deferred_qs() in order to better match reality.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree_exp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/rcu/tree_exp.h b/kernel/
The rcu_pm_notify() function refuses to switch to/from expedited grace
periods on systems with more than 256 CPUs due to the serialized
initialization of expedited grace periods. However, expedited grace
periods are now initialized in parallel, removing this concern.
This commit therefore removes
From: Akira Yokosawa
As the result of recent addition of "rdp->core_needs_qs = false;" in
the "if" block, now both branches of the if-else have the same
assignment.
Factor it out and reduce line count.
Signed-off-by: Akira Yokosawa
Cc: Joel Fernandes
Signed-off-by: Paul E. McKenney
Acked-by:
This commit prints a console message when cpulist_parse() reports a
bad list of CPUs, and sets all CPUs' bits in that case. The reason for
setting all CPUs' bits is that this is the safe(r) choice for real-time
workloads, which would normally be the ones using the rcu_nocbs= kernel
boot parameter.
From: Zhouyi Zhou
Previously, threads blocked on offlining CPUS were migrated to the
root rcu_node structure, thus requiring RCU priority boosting on this
structure. However, since commit d19fb8d1f3f6 ("rcu: Don't migrate
blocked tasks even if all corresponding CPUs offline"), RCU does not
migra
This commit better documents the jiffies_to_sched_qs default-value
strategy used by adjust_jiffies_till_sched_qs()
Reported-by: Joel Fernandes
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/rcu/tree.c b/kernel/r
From: "Joel Fernandes (Google)"
When there are no callbacks pending on an idle system, I noticed that
RCU softirq is continuously firing. During this the cpu_no_qs is set to
false, and core_needs_qs is set to true indefinitely. This causes
rcu_process_callbacks to be repeatedly called, even thoug
This commit makes r...@vger.kernel.org be the official list for RCU-related
topics.
Signed-off-by: Paul E. McKenney
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index e17ebf70b548..1924b52937a6 100644
--- a/MAINTAINERS
+++ b/
The purpose of exit_rcu() is to handle cases where buggy code causes a
task to exit within an RCU read-side critical section. It currently
does that in the case where said RCU read-side critical section was
preempted at least once, but fails to handle cases where preemption did
not occur. This ca
From: Neeraj Upadhyay
The current code only calls adjust_jiffies_till_sched_qs() if
jiffies_till_sched_qs is left at its default value, so when the
jiffies_till_sched_qs kernel-boot parameter actually is specified,
jiffies_to_sched_qs will be left with the value zero, which
will result in useless
From: Cyrill Gorcunov
The rcu_qs is disabling IRQs by self so no need to do the same in raise_softirq
but instead we can save some cycles using raise_softirq_irqoff directly.
CC: Paul E. McKenney
Signed-off-by: Cyrill Gorcunov
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tiny.c | 2 +-
1 f
From: Neeraj Upadhyay
The rcu_head_after_call_rcu() function reads the rhp->func pointer twice,
which can result in a false-positive WARN_ON_ONCE() if the callback
were passed to call_rcu() between the two reads. Although racing
rcu_head_after_call_rcu() with call_rcu() is to be a dubious use ca
From: Neeraj Upadhyay
The current rcu_gp_kthread_wake() function uses in_interrupt()
and thus does a self-wakeup from all interrupt contexts, including
the pointless case where the GP kthread happens to be running with
bottom halves disabled, along with the impossible case where the GP
kthread is
The task_struct structure's ->rcu_read_unlock_special field is only ever
read or written by the owning task, but it is accessed both at process
and interrupt levels. It may therefore be accessed using plain reads
and writes while interrupts are disabled, but must be accessed using
READ_ONCE() and
From: Liu Song
The rcutree.kthread_prio kernel-boot parameter is used to set the
priority for boost (rcub), per-CPU (rcuc), and grace-period (rcu_preempt
or rcu_sched) kthreads. It is also used by rcutorture to check whether
it is possible to meaningfully test RCU priority boosting. However,
al
Signed-off-by: Paul E. McKenney
---
MAINTAINERS | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1924b52937a6..a9b5270d006e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8983,7 +8983,7 @@ R:Daniel Lustig
L: linux-kernel@
* Tony Lindgren [190325 22:00]:
> We should not do the reset until the clocks are enabled. Let's only init
> restctrl in sysc_init_resets() and do the reset later on in sysc_reset().
...
> static int sysc_reset(struct sysc *ddata)
> {
> int offset = ddata->offsets[SYSC_SYSCONFIG];
> -
Because rcu_wake_cond() checks for a null task_struct pointer, there is
no need for its callers to do so. This commit eliminates the redundant
check.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/tree_plugin.h | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/kernel/rc
Hello!
This series contains miscellaneous fixes.
1. Unconditionally expedite during suspend/hibernate (unless the
real-time guys have disabled expediting altogether, that is).
2. Avoid unnecessary softirq when system is idle, courtesy of
Joel Fernandes.
3. rcu_qs
sparse complains that Yama defines functions and a variable as non-static
even though they don't exist in any header. Fix it by making them static.
Signed-off-by: Jann Horn
---
security/yama/yama_lsm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/security/yama/yama_l
Now that synchronize_rcu_bh, synchronize_rcu_bh_expedited, call_rcu_bh,
rcu_barrier_bh, synchronize_sched, synchronize_sched_expedited,
call_rcu_sched, rcu_barrier_sched, get_state_synchronize_sched,
and cond_synchronize_sched are obsolete, let's remove them from the
documentation aside from a smal
This commit fixes some issues with Documentation/RCU/checklist.txt.
Signed-off-by: Paul E. McKenney
---
Documentation/RCU/checklist.txt | 43 +++--
1 file changed, 25 insertions(+), 18 deletions(-)
diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/chec
From: Tycho Andersen
A diagram in whatisRCU.txt has space character before tabs. This commit
therefore makes this diagram consistent with elsewhere in the document:
Use one leading tab, followed by spaces for any additional whitespace
required.
Signed-off-by: Tycho Andersen
Signed-off-by: Paul
Reported-by: Andrew Morton
Signed-off-by: Paul E. McKenney
---
Documentation/RCU/rcu_dereference.txt | 103 ++
1 file changed, 103 insertions(+)
diff --git a/Documentation/RCU/rcu_dereference.txt
b/Documentation/RCU/rcu_dereference.txt
index ab96227bad42..bf699e8cfc75 1
Hello!
This series contains documentation updates:
1. Remove obsolete RCU update functions from RCU documentation.
2. Repair some whitespace damage, courtesy of Tycho Andersen.
3. Describe choice of rcu_dereference() APIs and __rcu usage.
4. Fix typos and otherwise moderniz
syzbot has bisected this bug to:
commit cf85d89562f39cc7ae73de54639f1915a9195b7a
Author: Finn Thain
Date: Fri May 25 07:34:36 2018 +
m68k/mac: Enable PDMA for PowerBook 500 series
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1226cb8b20
start commit: b0314565 Mer
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/printk.h:330,
from include/linux/kernel.h:15,
from include/linux/clk.h:16,
from sound/soc/fsl/fsl_audm
Hello!
This series contains a few straggling RCU consolidation updates:
1. Update kprobes's documentation of obsolete RCU update functions.
2. Update netfilter comment from call_rcu_bh() to call_rcu()
Thanx, Paul
---
On Tue, 26 Mar 2019, Arnd Bergmann wrote:
> On Tue, Mar 26, 2019 at 1:31 PM Thomas Gleixner wrote:
> >
> > On Tue, 26 Mar 2019, Miroslav Lichvar wrote:
> > > On Sat, Mar 23, 2019 at 11:36:19AM +0100, Thomas Gleixner wrote:
> > > > It is reasonable to force an upper bound for the various methods of
The RCU flavors have been consolidated, so this commit replaces a
comment's mention of call_rcu_bh() with call_rcu().
Signed-off-by: Paul E. McKenney
Cc: Pablo Neira Ayuso
Cc: Florian Westphal
Cc: "David S. Miller"
Cc: Alexey Kuznetsov
Cc: Hideaki YOSHIFUJI
Cc:
Cc:
Cc:
---
net/ipv4/netfi
On Tue, Mar 26, 2019 at 07:15:29PM +, Ghannam, Yazen wrote:
> Just tested on a fully populated system. Everything seems to be okay.
Thanks, queued.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Hi Michal,
On 03/26/19 at 03:31pm, Michal Hocko wrote:
> > > > OK, I am fine to drop it. Or only put the section existence checking
> > > > earlier to avoid unnecessary usemap/memmap allocation?
> > >
> > > DO you have any data on how often that happens? Should basically never
> > > happening, ri
>
> If you want to advocate the more complex design of mixed SWAPGS/FSGSBASE
> then provide numbers and not hand-waving. Numbers of real-world workloads,
> not numbers of artificial test cases which exercise the rare worst case.
Well you're proposing the much more complicated solution, not me.
S
On 3/26/19 12:06 PM, Catalin Marinas wrote:
> I wonder whether we'd be better off to replace the metadata allocator
> with gen_pool. This way we'd also get rid of early logging/replaying of
> the memory allocations since we can populate the gen_pool early with a
> static buffer.
I suppose this is
Commit 9c225f2655 (vfs: atomic f_pos accesses as per POSIX) added locking for
file.f_pos access and in particular made concurrent read and write not possible
- now both those functions take f_pos lock for the whole run, and so if e.g. a
read is blocked waiting for data, write will deadlock waiting
[+cc Catalin, Will, linux-arm-kernel]
On Tue, Mar 26, 2019 at 04:33:55PM +, John Garry wrote:
> On 25/03/2019 23:32, Bjorn Helgaas wrote:
> > On Thu, Mar 21, 2019 at 02:14:08AM +0800, John Garry wrote:
> > > Currently when we request an IO port region, the request is made directly
> > > to the
On Tue, 26 Mar 2019 10:41:23 -0700
Matthew Garrett wrote:
> On Tue, Mar 26, 2019 at 5:30 AM Masami Hiramatsu wrote:
> >
> > On Mon, 25 Mar 2019 15:09:49 -0700
> > Matthew Garrett wrote:
> >
> > > From: David Howells
> > >
> > > Disallow the creation of kprobes when the kernel is locked down by
Hi Nicolas,
This patch looks good except for one comment/question below.
Thanks,
Terry
On Tuesday, March 26, 2019 1:04 PM Nicolas Saenz Julienne
wrote:
>
>As seen on some USB wireless keyboards manufactured by Primax, the HID
>parser was using some assumptions that are not always true. In this
The ACPI specification implies that the IDENTICAL flag should be
set on all non leaf nodes where the children are identical.
This means that we need to be searching for the last node with
the identical flag set rather than the first one.
To achieve this with the existing code we need to pass a
fun
ACPI 6.3 adds additional fields to the MADT GICC
structure to describe SPE PPI's. We pick these out
of the cached reference to the madt_gicc structure
similarly to the core PMU code. We then create a platform
device referring to the IRQ and let the user/module loader
decide whether to load the SPE
This patch series enables the Arm Statistical Profiling
Extension (SPE) on ACPI platforms.
This is possible because ACPI 6.3 uses a previously
reserved field in the MADT to store the SPE interrupt
number, similarly to how the normal PMU is described.
If a consistent valid interrupt exists across a
Lets add the MODULE_TABLE and platform id_table entries so that
the SPE driver can attach to the ACPI platform device created by
the core pmu code.
Signed-off-by: Jeremy Linton
Reviewed-by: Sudeep Holla
---
drivers/perf/arm_spe_pmu.c | 11 +--
1 file changed, 9 insertions(+), 2 deletion
ACPI 6.3 adds a flag to indicate that child nodes are all
identical cores. This is useful to authoritatively determine
if a set of (possibly offline) cores are identical or not.
Since the flag doesn't give us a unique id we can generate
one and use it to create bitmaps of sibling nodes, or simply
On Tue, Mar 26, 2019 at 04:45:34AM +0800, Yang Weijiang wrote:
> Hi, Paolo and Sean,
> Do you have any comments on v4 patches?
My backlog is a bit full at the moment, I'll try to review the series
later this week.
On Fri, Mar 22, 2019 at 6:27 AM Christoph Hellwig wrote:
>
> On Wed, Mar 20, 2019 at 05:04:58PM -0700, Alistair Francis wrote:
> > > Well, it starts at 0x00, but the first one is reserved. If you think
> > > that is too confusing I'd rather throw in a comment explaining this
> > > fact rather tha
Andi.
On Tue, 26 Mar 2019, Andi Kleen wrote:
> On Tue, Mar 26, 2019 at 06:03:59PM +0100, Thomas Gleixner wrote:
> > On Thu, 21 Mar 2019, Andi Kleen wrote:
> >
> > > With gcc 8 toplevel assembler statements that do not mark themselves
> > > as .text may end up in other sections.
> >
> > Which is
> + for (at = base; at < top; at += cpuc->pebs_record_size) {
> + u64 pebs_status;
> +
> + pebs_status = get_pebs_status(at) & cpuc->pebs_enabled;
> + pebs_status &= mask;
> +
> + for_each_set_bit(bit, (unsigned long *)&pebs_status, size)
> +
The pull request you sent on Tue, 26 Mar 2019 20:12:07 +:
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.1-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/14c741de93861749dfb60b4964028541f5c506ca
Thank you!
--
Deet-doot-dot, I am a bot.
From: Andi Kleen
This reverts e864c5ca145e perf stat: Hide internal duration_time counter
but doing it manually since the code has now moved to a different file.
The next patch will properly implement duration_time as a full
event, so no need to hide it anymore.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
Implement printing the correct name for duration_time
Signed-off-by: Andi Kleen
---
tools/perf/util/evsel.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index 7835e05f0c0a..6872394b6f55 100644
From: Andi Kleen
Add support to perf list to output tool internal events, currently
only duration_time.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-list.c | 6 --
tools/perf/util/parse-events.c | 20
tools/perf/util/parse-events.h | 1 +
3 files changed, 25
From: Andi Kleen
The perf metric expression use duration_time internally to normalize
events. Normal perf stat without -x also prints the duration time.
But when using -x, the interval is not output anywhere, which
is inconvenient for any post processing which often wants to
normalize values to t
Currently it's not possible to get the wall clock time of a measurement
in CSV mode output, it's only in the non CSV perf stat output.
Often this is needed to normalize event counts to time.
Add a new duration_time event that can be specified and reports
the wall clock time in ns.
On 3/26/2019 2:09 PM, Yuri Norov wrote:
+ Mike Travis
+ Thomas Gleixner
--
On Tue, Mar 26, 2019 at 12:07:45AM +0300, Yury Norov wrote:
The requirement for this rework is to keep the __bitmap_parselist()
copy-less and singl
On Tue, Mar 26, 2019 at 02:25:52PM -0700, Huang, Kai wrote:
> >
> > That being said, this in no way impacts KVM's ability to virtualize SGX,
> > e.g.
> > KVM can directly do CPUID and {RD,WR}MSR to probe the capabilities of the
> > platform as needed.
>
> I am not following. KVM can do whatever
On Wed, Mar 20, 2019 at 06:49:27PM +, Suzuki K Poulose wrote:
> Switch to using the coresight device instead of the parent
> amba device.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
> drivers/hwtracing/coresight/coresight-tpiu.c | 12 ++--
> 1 file changed, 6 ins
Hi Suzuki,
On Wed, Mar 20, 2019 at 06:49:25PM +, Suzuki K Poulose wrote:
> In preparation to use a consistent device naming scheme,
> clean up the device link tracking in replicator driver.
> Use the "coresight" device instead of the "real" parent device
> for all internal purposes. All other
The rework of the watchdog core to use cpu_stop_work broke the watchdog
cpumask on CPU hotplug.
The watchdog_enable/disable() functions are now called unconditionally from
the hotplug callback, i.e. even on CPUs which are not in the watchdog
cpumask.
Only invoke them when the plugged CPU is in th
On Mon, Mar 4, 2019 at 4:18 AM Chen, Hu wrote:
>
> When the system is woken from S3 by the ACPI fixed power button, send
> KEY_POWER to user space.
>
> I run Android on x86 PC (it's a NUC). Everytime I press the power button
> to wake the system, it suspends right away. After some debug, I find
>
On Tue, 26 Mar 2019 14:29:27 -0700
Linus Torvalds wrote:
> On Tue, Mar 26, 2019 at 11:48 AM Steven Rostedt wrote:
> >
> > Should I work on changing this?
>
> I don't personally much care, but the pr-tracker-bot clearly does.
>
> If you don't care about the automated "it's been pulled" messag
On 2019-03-19 07:31, Shawn Guo wrote:
On Fri, Mar 08, 2019 at 12:02:22PM +, Daniel Baluta wrote:
SDMA1 is part of AIPS-3 region and SDMA2 is part
of AIPS-1 region.
Reviewed-by: Fabio Estevam
Reviewed-by tag should go after your SoB, since that's the sequence of
how they come.
Signed-of
On Tue, Mar 26, 2019 at 06:03:59PM +0100, Thomas Gleixner wrote:
> Andi,
>
> On Thu, 21 Mar 2019, Andi Kleen wrote:
>
> > With gcc 8 toplevel assembler statements that do not mark themselves
> > as .text may end up in other sections.
>
> Which is clearly a change in behaviour. Is that intended o
On Tue, Mar 26, 2019 at 11:48 AM Steven Rostedt wrote:
>
> Should I work on changing this?
I don't personally much care, but the pr-tracker-bot clearly does.
If you don't care about the automated "it's been pulled" message, that
doesn't matter, of course.
That said, I'd almost prefer to get jus
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> + When hpet is specified, the NMI watchdog will be driven
> + by an HPET timer, if available in the system. Otherwise,
> + the perf-based implementation will be used. Specifying
> +
On Tue, Mar 26, 2019 at 7:31 PM Leon Romanovsky wrote:
>
> On Tue, Mar 26, 2019 at 07:08:07PM +0100, Rafael J. Wysocki wrote:
> > On Tue, Mar 26, 2019 at 6:53 PM Leon Romanovsky wrote:
> > >
> > > On Tue, Mar 26, 2019 at 05:30:22PM +0100, Rafael J. Wysocki wrote:
> > > > On Tue, Mar 26, 2019 at 4
From: Thor Thayer
The FIFO memory and ECC initialization doesn't need to be
done as a separate operation early in the startup.
Improve the Arria10 and Stratix10 peripheral FIFO init
by initializing memory and enabling ECC as part of the
device driver initialization.
Signed-off-by: Thor Thayer
From: Thor Thayer
Improve the Arria10 and Stratix10 error injection routine
by reading the data and changing just 1 bit before writing
back out. Previous routine would overwrite the first bytes
to 0 then change 1 bit but this method is less intrusive.
Signed-off-by: Thor Thayer
---
drivers/eda
>
> On Tue, Mar 26, 2019 at 05:17:40AM -0700, Huang, Kai wrote:
> > On Wed, 2019-03-20 at 18:21 +0200, Jarkko Sakkinen wrote:
> > > From: Sean Christopherson
> > >
> > > Similar to other large Intel features such as VMX and TXT, SGX must
> > > be explicitly enabled in IA32_FEATURE_CONTROL MSR to
On Tue, 2019-03-26 at 14:33 -0500, Alan Tull wrote:
> On Mon, Mar 25, 2019 at 5:58 PM Scott Wood wrote:
>
> Hi Scott,
>
> > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote:
> > > On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> > > > +#if defined(CONFIG_X86) && defined(CONFIG_AS_AVX512)
>
On Tue, 26 Mar 2019 13:55:39 -0700
Andy Lutomirski wrote:
> On Tue, Mar 26, 2019 at 11:28 AM Matthew Garrett
> wrote:
> >
> > From: Matthew Garrett
> >
> > Any hardware that can potentially generate DMA has to be locked down in
> > order to avoid it being possible for an attacker to modify kern
Tested-by: Jett Rink
On Sun, Mar 24, 2019 at 9:36 AM Srinivas Pandruvada
wrote:
>
> On Sat, 2019-03-23 at 16:46 +0530, Rushikesh S Kadam wrote:
> > This driver adds support for loading Intel Integrated
> > Sensor Hub (ISH) firmware from host file system to ISH
> > SRAM and start execution.
> >
This commit adds the TmFifo platform driver for Mellanox BlueField
Soc. TmFifo is a shared FIFO which enables external host machine
to exchange data with the SoC via USB or PCIe. The driver is based
on virtio framework and has console and network access enabled.
Reviewed-by: Vadim Pasternak
Signe
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> +#ifdef CONFIG_X86_HARDLOCKUP_DETECTOR_HPET
> +struct hpet_hld_data *hpet_hardlockup_detector_assign_timer(void)
> +{
> + struct hpet_hld_data *hdata;
> + unsigned int cfg;
> +
> + cfg = hpet_readl(HPET_Tn_CFG(HPET_WD_TIMER_NR));
> +
> + if
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> Users of HPET timers (such as the hardlockup detector) need the definitions
> of these flags to interpret the configuration of a timer as passed by
> platform code.
Which platform code?
> +#define HPET_DEV_USED_BIT2
> +#define HPET_DEV_USED
+ Mike Travis
+ Thomas Gleixner
--
On Tue, Mar 26, 2019 at 12:07:45AM +0300, Yury Norov wrote:
>> The requirement for this rework is to keep the __bitmap_parselist()
>> copy-less and single-pass but make it more readable and mai
> On Tue, Mar 26, 2019 at 01:40:57PM +0100, Thomas Gleixner wrote:
> > On Tue, 26 Mar 2019, Huang, Kai wrote:
> > > On Wed, 2019-03-20 at 18:21 +0200, Jarkko Sakkinen wrote:
> > > > 13 files changed, 1657 insertions(+), 2 deletions(-) create mode
> > > > 100644 arch/x86/include/uapi/asm/sgx.h cr
Hello Guenter,
On Tue, 26 Mar 2019 13:03:02 -0700
Guenter Roeck wrote:
> > I'll have a look. In the mean time, I'm fine with the patch being
> > reverted.
>
> The problem is still seen in the latest kernel as of last night, and
> I did not see any further activities. Should I send a revert requ
Hi David,
I've been testing gfs2 on top of this patch and it seems...
On 19/03/2019 16:23, David Howells wrote:
Create a function, vfs_get_block_super(), that is fs_context-aware and a
replacement for mount_bdev(). It caches the block device pointer and file
open mode in the fs_context struct
On 3/26/19 4:18 PM, Joao Moreira wrote:
On 3/18/19 4:18 PM, Joe Lawrence wrote:
On Fri, Mar 01, 2019 at 11:13:05AM -0300, Joao Moreira wrote:
Livepatches may use symbols which are not contained in its own scope,
and, because of that, may end up compiled with relocations that will
only be reso
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> int hpet_alloc(struct hpet_data *hdp)
> {
> u64 cap, mcfg;
> @@ -845,7 +868,6 @@ int hpet_alloc(struct hpet_data *hdp)
> size_t siz;
> struct hpet __iomem *hpet;
> static struct hpets *last;
> - unsigned long period;
> u
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> struct irq_data;
> @@ -109,6 +114,11 @@ extern void hpet_unregister_irq_handler(rtc_irq_handler
> handler);
> static inline int hpet_enable(void) { return 0; }
> static inline int is_hpet_enabled(void) { return 0; }
> #define hpet_readl(a) 0
> +#defin
On Tue, Mar 26, 2019 at 11:28 AM Matthew Garrett
wrote:
>
> From: Matthew Garrett
>
> IO port access would permit users to gain access to PCI configuration
> registers, which in turn (on a lot of hardware) give access to MMIO
> register space. This would potentially permit root to trigger arbitra
On Wed, 27 Feb 2019, Ricardo Neri wrote:
> @@ -62,7 +67,18 @@ static inline void set_comparator(struct hpet_hld_data
> *hdata,
> static void kick_timer(struct hpet_hld_data *hdata, bool force)
> {
> bool kick_needed = force || !(hdata->flags & HPET_DEV_PERI_CAP);
> - unsigned long new_
201 - 300 of 962 matches
Mail list logo
