On Tue 04-09-18 10:00:36, Jerome Glisse wrote:
> On Mon, Sep 03, 2018 at 07:56:54AM +0200, Michal Hocko wrote:
[...]
> > And THP migration is still a problem with 4.4 AFAICS. All other cases
> > simply split the huge page but THP migration keeps it in one piece and
> > as such it is theoretically b
On 5 September 2018 at 10:43, Baolin Wang wrote:
> Hi Jacek,
>
> On 5 September 2018 at 04:19, Jacek Anaszewski
> wrote:
>> Hi Baolin,
>>
>> On 09/04/2018 01:01 PM, Baolin Wang wrote:
>>> This patch implements the 'pattern_set'and 'pattern_clear'
>>> interfaces to support SC27XX LED breathing mod
From: Tobias Wolf
Set the PCI controller of_node such that PCI devices can be
instantiated via device tree.
Signed-off-by: Tobias Wolf
Signed-off-by: Mathias Kresin
---
arch/mips/pci/pci-rt2880.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/mips/pci/pci-rt2880.c b/arch/mips/pci/
Hi Janusz,
Janusz Krzysztofik wrote on Mon, 20 Aug 2018
23:39:01 +0200:
> This series consist of possibly ready to apply patches extracted from
> a former one titled "mtd: rawnand: ams-delta: Use GPIO API for data I/O".
> Remaining patches implementing conversion of data I/O to GPIO have been
>
On Tue 04-09-18 15:59:34, Shuah Khan wrote:
[...]
> This will support the following workload requirements:
>
> - reserving one or more NUMA memory nodes for class of critical tasks that
> require
> guaranteed memory availability.
> - isolate memory blocks with a guaranteed exclusive access.
Ho
This Patch Adds reset API's to support release, assert
and status functionalities by using firmware interface.
Signed-off-by: Nava kishore Manne
---
Changes for v2:
-New Patch.
drivers/firmware/xilinx/zynqmp.c | 40 +++
include/linux/firmware/xlnx-zynqmp.h | 136 +++
This series of patches are created On top of the
below series of patches.
https://lkml.org/lkml/2018/8/3/687
Nava kishore Manne (3):
firmware: xilinx: Add reset API's
dt-bindings: fpga: Add bindings for ZynqMP reset driver
reset: reset-zynqmp: Adding support for Xilinx zynqmp reset
cont
Add a reset controller driver for Xilinx Zynq UltraScale+ MPSoC.
The zynqmp reset-controller has the ability to reset lines
connected to different blocks and peripheral in the Soc.
Signed-off-by: Nava kishore Manne
---
Changes for v2:
-Moved eemi_ops into a priv struct as suggeste
Add documentation to describe Xilinx ZynqMP reset driver
bindings.
Signed-off-by: Nava kishore Manne
---
Changes for v2:
-Moved reset node as a child to firwmare
node.
.../firmware/xilinx/xlnx,zynqmp-firmware.txt | 142 +
1 file changed
On Tue, Sep 04, 2018 at 05:28:13PM -0400, Daniel Jordan wrote:
> Pavel Tatashin, Ying Huang, and I are excited to be organizing a performance
> and scalability microconference this year at Plumbers[*], which is happening
> in Vancouver this year. The microconference is scheduled for the morning
On 4 September 2018 at 14:54, Johan Hovold wrote:
> On Mon, Aug 27, 2018 at 04:44:44PM +0200, Ulf Hansson wrote:
>> On 27 August 2018 at 10:21, Johan Hovold wrote:
>> > Use the new of_get_compatible_child() helper to lookup the slot child
>> > node instead of using of_find_compatible_node(), whic
On Tue 04-09-18 11:33:45, Alexander Duyck wrote:
> From: Alexander Duyck
>
> It doesn't make much sense to use the atomic SetPageReserved at init time
> when we are using memset to clear the memory and manipulating the page
> flags via simple "&=" and "|=" operations in __init_single_page.
>
> T
On Tue, 4 Sep 2018, Tim Chen wrote:
> I think STIBP should be an opt in option as it will have significant
> impact on performance. The attack from neighbor thread is pretty
> difficult to pull off considering you have to know what the sibling
> thread is running and its address allocation.
In m
Hi Reinette,
Thanks for looking at this.
On Tue, Sep 04, 2018 at 03:36:01PM -0700, Reinette Chatre wrote:
> Hi Chen Yu,
>
> On 9/4/2018 1:24 PM, Reinette Chatre wrote:
> > On 9/4/2018 10:46 AM, Chen Yu wrote:
> >> On a platform with MB resource enabled, a divided-by-zero
> >> exception is triggere
On Tue 04-09-18 11:33:39, Alexander Duyck wrote:
> From: Alexander Duyck
>
> On systems with a large amount of memory it can take a significant amount
> of time to initialize all of the page structs with the PAGE_POISON_PATTERN
> value. I have seen it take over 2 minutes to initialize a system wi
On Wed, Sep 5, 2018 at 12:27 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:13PM +0530, Anup Patel wrote:
>> Few advantages of this new driver over previous one are:
>> 1. It registers all local interrupts as per-CPU interrupts
>
> Please explain why this is an advantage.
Previously
Good day,
My name is Richard Jeffery I have a client, who died as a result of
heart-related condition on the 10th of December, 2015. I have contacted
you to assist in distributing the estate left behind by my client, who
shares the same last name as yours. Would discuss more when I hear from
y
Use DRM_FORMAT_HOST_XRGB, so we are using the correct format code
on bigendian machines. Also set the quirk_addfb_prefer_host_byte_order
mode_config bit so drm_mode_addfb() asks for the correct format code.
Both DRM_FORMAT_* and VIRTIO_GPU_FORMAT_* are defined to be little
endian, so using a
On Fri, Aug 31, 2018 at 10:24:18PM +0300, Igor Stoppa wrote:
> Typically the assert is expected to not fail.
This whole assert can be removed.
>
> Signed-off-by: Igor Stoppa
> Acked-by: Doug Ledford
Most probably that I missed discussion, but anyway, does this
"Acked-by" come from internal or
[...]
> > >
> > > This patch causes a number of statistically significant
> > > regressions
> > > (with significance of 1%) on the two systems I've tested it
> > > on. On
> > > my
> >
> > Sure. These patches are targeted to Atom clients where some of
> > these
> > server like workload may hav
On Tue, 4 Sep 2018 17:16:31 -0700
Kees Cook wrote:
> On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
> wrote:
> > Harald Freudenberger (5):
> > s390/zcrypt: hex string mask improvements for apmask and aqmask.
>
> This (and an earlier 2017 commit) adds VLAs, which are being
> removed[
Hello,
On Wed, Sep 05, 2018 at 09:24:26AM +0800, Anson Huang wrote:
> In noirq suspend/resume stage with no_console_suspend enabled,
> imx_uart_console_write() may be called to print out log_buf
> message by printk(), so there will be race condition between
> imx_uart_console_write() and imx_uart_
On Wed, Sep 05, 2018 at 09:24:27AM +0800, Anson Huang wrote:
> On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
> state retention), UART iomux settings will be lost, need to add
> pinctrl sleep/default mode switch during suspend/resume to make
> sure UART iomux settings are correc
The smp_mb() in cpuhp_thread_fun() appears to be misplaced, and
need to be after the load of st->should_run, to prevent
reordering of the later load/stores w.r.t. the load of
st->should_run.
Signed-off-by: Neeraj Upadhyay
---
kernel/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(
On (09/05/18 14:36), Sergey Senozhatsky wrote:
>
> OK, thanks for the report!
> So I think that your case is CON_PRINTBUFFER related as well. We have
> a number of logbuf messages before we parse quiet and console_loglevel.
> Those messages pass the suppress_message() test. Then when we finally
>
Fix a compile warning "SAVE_FLAGS redefined" introduced recently by
tip.git commit: 6da63eb241a05b0e676d6 ("x86/paravirt: Move the
pv_irq_ops under the PARAVIRT_XXL umbrella").
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/paravirt.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On (09/05/18 06:53), Hans de Goede wrote:
> >
> > Do you use earlycon?
>
> No, I'm seeing this with the regular/normal console stuff.
OK, thanks for the report!
So I think that your case is CON_PRINTBUFFER related as well. We have
a number of logbuf messages before we parse quiet and console_log
On 29.08.2018 08:22, Gustavo A. R. Silva wrote:
> There is a NULL pointer dereference in case memory resources
> for *parse* are not successfully allocated.
>
> Fix this by adding a new goto label and make the execution
> path jump to it in case vzalloc() fails.
>
> Addresses-Coverity-ID: 1473081
On 05/09/18 02:55, Frank Rowand wrote:
> On 08/30/18 12:05, Rob Herring wrote:
>> Only some old OpenFirmware implementations rely on default sizes. Any
>> FDT and modern implementation should have explicit properties. Make the
>> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any out
Hi,
On 05-09-18 04:35, Sergey Senozhatsky wrote:
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
Commit 375899cddcbb ("printk: make sure to print log on console."), moved
the checking of the loglevel of messages from flush time to the actual
log time.
This introduces one problem, some early boo
On Wed, Sep 5, 2018 at 12:26 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:12PM +0530, Anup Patel wrote:
>> This patch selects following GENERIC_IRQ kconfig options:
>> GENERIC_IRQ_MULTI_HANDLER
>
> This is already selected by arch/riscv/Kconfig.
>
>> GENERIC_IRQ_PROBE
>
> This is s
On Wed, Sep 5, 2018 at 12:20 AM, Christoph Hellwig wrote:
> On Tue, Sep 04, 2018 at 06:15:10PM +0530, Anup Patel wrote:
>> The mechanism to trigger IPI is generally part of interrupt-controller
>> driver for various architectures. On RISC-V, we have an option to trigger
>> IPI using SBI or SOC ven
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove direct access to device_node.type, add
> of_node_is_type() and of_node_get_device_type() helpers to check and
> retrieve the device type.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> include/linux/of.h | 12 ++
On Fri, 31 Aug 2018 15:17:44 +
Matteo Croce wrote:
> On Fri, Aug 31, 2018 at 3:49 AM Nicholas Piggin wrote:
> >
> > On Tue, 28 Aug 2018 15:00:14 +
> > Matteo Croce wrote:
> >
> > > On Tue, Aug 28, 2018 at 2:35 PM Nicholas Piggin
> > > wrote:
> > > >
> > > > On Tue, 28 Aug 2018 12:
Hi all,
Changes since 20180904:
Dropped trees: xarray, ida (temporarily)
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 1853
2252 files ch
Hi Linus,
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-4.19-tag1
for you to fe
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove device_node.name pointer, add helper functions
> for node name comparisons which are a common pattern throughout the kernel.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/base.c | 22 ++
add config file
Signed-off-by: Lei Yang
---
tools/testing/selftests/efivarfs/config | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/efivarfs/config
diff --git a/tools/testing/selftests/efivarfs/config
b/tools/testing/selftests/efivarfs/config
new file mode 100
sorry, the title should be :"cgroup: kselftests: add test_core to
.gitignore"
Lei
On 2018年09月05日 10:39, Lei Yang wrote:
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selfte
Hi Jacek,
On 5 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/04/2018 01:01 PM, Baolin Wang wrote:
>> This patch implements the 'pattern_set'and 'pattern_clear'
>> interfaces to support SC27XX LED breathing mode.
>>
>> Signed-off-by: Baolin Wang
>> ---
>> Changes from v7
On Wed, Sep 05, 2018 at 01:00:37AM +, Schaufler, Casey wrote:
> Sorry, I've been working in security too long for my
> optimistic streak to be very wide.
Eheh. So I was simply trying to follow in context, but it wasn't
entirely clear, so I tried to take it out of context and then it was
even l
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/cgroup/.gitignore
b/tools/testing/selftests/cgroup/.gitignore
index 95eb3a5..adacda5 100644
--- a/tools/testing/selftests/cg
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
> Commit 375899cddcbb ("printk: make sure to print log on console."), moved
> the checking of the loglevel of messages from flush time to the actual
> log time.
>
> This introduces one problem, some early boot messages are printed before
> parse_early
Some leds on our board are active low leds, which means these leds
are lighted when the corresponding gpio line is low, while the
original leds-gpio driver default all leds are active high leds.
This patch adds a devicetree node "light-state", whose value should
be "high" for active high leds and "
This series adds PCIe host controller driver for Socionext UniPhier SoCs.
This controller is based on the DesignWare PCIe core. This driver
supports LD20 and PXs3 SoCs.
Kunihiko Hayashi (2):
dt-bindings: pci: add UniPhier PCIe host controller description
pci: dwc: add UniPhier PCIe host contro
This introduces specific glue layer for UniPhier platform to support
PCIe host controller that is based on the Designware PCIe Core, and
this driver supports Root Complex (host) mode.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/Kconfig | 9 +
drivers/pci/controller/d
Add DT bindings for PCIe controller implemented in UniPhier SoCs when
configured in Root Complex (host) mode. This controller is based on
the Designware PCIe Core.
Signed-off-by: Kunihiko Hayashi
---
.../devicetree/bindings/pci/uniphier-pcie.txt | 78 ++
1 file changed,
It uses modprobe $TEST_DRIVER in sysctl.sh, so update
config to use "m" instead
Signed-off-by: Lei Yang
---
tools/testing/selftests/sysctl/config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/sysctl/config
b/tools/testing/selftests/sysctl/config
ind
On 08/30/18 12:05, Rob Herring wrote:
> This is a small restructuring and clean-up of handling root node
> #size-cells and #address-cells (or lack of). As only Sparc needs a
> different default value and only for #address-cells, we can handle that
> locally and remove one more dependency on asm/p
Srinivas Pandruvada writes:
> On Mon, 2018-09-03 at 23:53 -0700, Francisco Jerez wrote:
>> Eero Tamminen writes:
>>
>> > Hi,
>> >
>> > On 31.08.2018 20:28, Srinivas Pandruvada wrote:
>> > ...
>> > > As per testing Eero Tamminen, the results are comparable to the
>> > > patchset
>> > > https://
On 08/30/18 12:05, Rob Herring wrote:
> Only some old OpenFirmware implementations rely on default sizes. Any
> FDT and modern implementation should have explicit properties. Make the
> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any outside
> users.
>
> This also gets us one step
Hi all,
On Wed, 5 Sep 2018 10:39:06 +1000 Stephen Rothwell
wrote:
>
> After merging the devicetree tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
> function of_fdt_limit_memory() to
On 08/30/18 12:05, Rob Herring wrote:
> Now that we initialize dt_root_addr_cells and dt_root_size_cells earlier,
> use them and simplify of_fdt_limit_memory.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/fdt.c | 23 +--
> 1 file changed, 1 insertion(+
On 08/30/18 12:05, Rob Herring wrote:
> Scan the root node properties (#{size,address}-cells) earlier,
^^^
before mdesc->dt_fixup() is called
> so that
> the dt_root_addr_cells and dt_root_size_cells variabl
On Thu, Aug 30, 2018 at 12:47:27PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> This simplifies the code. No change in behavior.
>
> Signed-off-by: Eric Biggers
> ---
> lib/parser.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/lib/parser.c b/lib/parser.
In resctrl filesystem, we have some mount options to enable
L3/L2 CDP and MBA Software Controller features if platform supports them:
mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps]] /sys/fs/resctrl
But currently only "cdp" option can be displayed. "cdpl2" and "mba_MBps"
options are not s
On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
state retention), UART iomux settings will be lost, need to add
pinctrl sleep/default mode switch during suspend/resume to make
sure UART iomux settings are correct after resume.
Signed-off-by: Anson Huang
---
drivers/tty/serial/
In noirq suspend/resume stage with no_console_suspend enabled,
imx_uart_console_write() may be called to print out log_buf
message by printk(), so there will be race condition between
imx_uart_console_write() and imx_uart_save/restore_context(),
need to add lock to protect the registers save/restor
Hi, Uwe
Anson Huang
Best Regards!
> -Original Message-
> From: Uwe Kleine-König
> Sent: Wednesday, September 5, 2018 4:32 AM
> To: Anson Huang
> Cc: gre...@linuxfoundation.org; jsl...@suse.com;
> linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; dl-linux-imx
>
> Subject: Re:
Hi Shuah,
I wrote some tests for the new memory.oom.group feature in cgroups 2.
In the process, I discovered a few small bugs in the cgroups tests, which
I have fixed as well in a separate commit.
This is my first ever patch to Linux, so let me know if you see any issues or
improvements that can
From: Jay Kamat
Add tests for memory.oom.group for the following cases:
- Killing all processes in a leaf cgroup, but leaving the
parent untouched
- Killing all processes in a parent and leaf cgroup
- Keeping processes marked by OOM_SCORE_ADJ_MIN alive when considered
for being killed by the
From: Jay Kamat
Fix a couple issues with cg_read_strcmp(), to improve correctness of
cgroup tests
- Fix cg_read_strcmp() always returning 0 for empty "needle" strings
- Fix a memory leak in cg_read_strcmp()
Fixes: 84092dbcf901 ("selftests: cgroup: add memory controller self-tests")
Signed-off-b
> -Original Message-
> From: Andrea Arcangeli [mailto:aarca...@redhat.com]
> Sent: Tuesday, September 04, 2018 4:37 PM
> To: Schaufler, Casey
> Cc: Jiri Kosina ; Tim Chen ;
> Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Woodhouse, David ; Oleg
> Nesterov ; linux-ke
On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> On Tue, Sep 04, 2018 at 04:18:18PM -0400, Jeff Layton wrote:
> > On Tue, 2018-09-04 at 14:54 -0400, J. Bruce Fields wrote:
> > > On Tue, Sep 04, 2018 at 06:23:48PM +0200, Rogier Wolff wrote:
> > > > On Tue, Sep 04, 2018 at 12:12:03PM -0
On 08/31/2018 09:09 AM, Steven Sistare wrote:
On 8/30/2018 4:24 PM, subhra mazumdar wrote:
Introduce pipe_ll_usec field for pipes that indicates the amount of micro
seconds a thread should spin if pipe is empty or full before sleeping. This
is similar to network sockets. Workloads like hackbe
Hi Rob,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
function of_fdt_limit_memory() to the variable .init.data:dt_root_addr_cells
The function of_fdt_limit_mem
On 09/04/2018 02:54 PM, Thomas Gleixner wrote:
On Thu, 30 Aug 2018, subhra mazumdar wrote:
+void pipe_busy_wait(struct pipe_inode_info *pipe)
+{
+ unsigned long wait_flag = pipe->pipe_wait_flag;
+ unsigned long start_time = pipe_busy_loop_current_time();
+
+ pipe_unlock(p
On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
wrote:
> Harald Freudenberger (5):
> s390/zcrypt: hex string mask improvements for apmask and aqmask.
This (and an earlier 2017 commit) adds VLAs, which are being
removed[1] from the kernel:
drivers/s390/crypto/ap_bus.c:980:3: warning: I
Hi Stefan,
On Tue, 4 Sep 2018 22:07:15 +0200 (CEST) Stefan Wahren
wrote:
>
> > Eric Anholt hat am 4. September 2018 um 19:41 geschrieben:
> >
> > Stephen Rothwell writes:
> >
> > > Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> > > produces this error:
> > >
> > >
Hi,
On Mon, Sep 3, 2018 at 1:34 PM, Bjorn Andersson
wrote:
> On Tue 28 Aug 06:38 PDT 2018, Amit Kucheria wrote:
>
>> Instead of showing up as thermal-sensor@, the nodes will show up as
>> tsens0_tm, tsen1_tm, tsens1_srot, etc. in /proc/iomem making it easier to
>> read.
>>
>> IOW,
>>
>> 0c222000-
Hello,
On Tue, Sep 04, 2018 at 06:10:47PM +, Schaufler, Casey wrote:
> The real reason to use an LSM based approach is that overloading ptrace
> checks is a Really Bad Idea. Ptrace is a user interface. Side-channel is a
> processor interface. Even if ptrace_may_access() does exactly what you
Hi all,
On Tue, 4 Sep 2018 15:54:27 +0530 Amit Kucheria
wrote:
>
> I'm currently reviewing this patchset (long overdue), but considering
> that we haven't added any major new features to the framework for the
> last couple of revisions, can you get this patchset merged into
> linux-next to see h
On 09/04/2018 11:48 AM, Jiri Kosina wrote:
> On Tue, 4 Sep 2018, Schaufler, Casey wrote:
>
>>> So if this should be done in LSM, it'd probably have to be written by
>>> someone else than me :) who actually understands how the "sidechannel LSM"
>>> idea works.
>>
>> Yes. That would be me.
>
> Ok,
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last Level Cache Controller (LLCC) of Tag RAM and Data RAM. Interrupts
are triggered when the errors happen in the cache, the driver ha
This series implements EDAC driver for QCOM SoCs. As of now, this driver
supports EDAC for Last Level Cache Controller (LLCC). LLCC EDAC driver is
to detect and report single and double bit errors on Last Level Cache
Controller (LLCC) cache. Interrupts are triggered when the errors happen
in the ca
Currently, broadcast base is set to end of the LLCC banks, which may
not be correct always. As the number of banks may vary for each chipset
and the broadcast base could be at a different address as well. This info
depends on the chipset, so get the broadcast base info from the device
tree (DT). Ad
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by: Venkata Narendra Kumar Gutta
Reviewed-by: Rob Herring
---
.../devicetree/bindings/arm/msm/qcom,llcc.txt
Cache error reporting controller detects and reports single and
double bit errors on Last Level Cache Controller (LLCC) cache.
Add required support to register LLCC EDAC driver as platform driver,
from LLCC driver.
Signed-off-by: Venkata Narendra Kumar Gutta
Reviewed-by: Evan Green
---
drivers/
On 2018-08-30 05:11, Borislav Petkov wrote:
On Tue, Aug 28, 2018 at 05:42:26PM -0700, Venkata Narendra Kumar Gutta
wrote:
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last Level
The mm-of-the-moment snapshot 2018-09-04-16-03 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Tue, Sep 04, 2018 at 11:23:12AM -0700, Eduardo Valentin wrote:
> Hello,
>
> On Thu, Aug 23, 2018 at 08:07:32AM -0700, Eduardo Valentin wrote:
> > On a system with X86_FEATURE_ARCH_PERFMON disabled
> > and with a model not known by family PMU drivers,
> > user gets a kernel message log like the
On 09/03/2018 09:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.6 release.
There are 123 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 m
On 09/03/2018 09:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.68 release.
There are 165 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
On 09/03/2018 09:48 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.154 release.
There are 80 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 m
On 09/03/2018 09:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.125 release.
There are 107 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
On 09/03/2018 09:48 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.121 release.
There are 56 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
Commit 9092c71bb724 ("mm: use sc->priority for slab shrink targets")
changed the way how the target slab pressure is calculated and
made it priority-based:
delta = freeable >> priority;
delta *= 4;
do_div(delta, shrinker->seeks);
The problem is that on a default priority (which is 12)
On Wed, Sep 05, 2018 at 12:38:22AM +0200, Dominique Martinet wrote:
> The 'm' kcore_list item could point to kclist_head, and it is incorrect to
> look at m->addr / m->size in this case.
> There is no choice but to run through the list of entries for every address
> if we did not find any entry in
The 'm' kcore_list item could point to kclist_head, and it is incorrect to
look at m->addr / m->size in this case.
There is no choice but to run through the list of entries for every address
if we did not find any entry in the previous iteration
Reset 'm' to NULL in that case at Omar Sandoval's su
Hi Chen Yu,
On 9/4/2018 1:24 PM, Reinette Chatre wrote:
> On 9/4/2018 10:46 AM, Chen Yu wrote:
>> On a platform with MB resource enabled, a divided-by-zero
>> exception is triggered when accessing 'size':
>>
>> [ 151.193447] divide error: [#1] SMP PTI
>> [ 151.197743] CPU: 93 PID: 1929 Comm
From: Dominique Martinet
The 'm' kcore_list item could point to kclist_head, and it is incorrect to
look at m->addr / m->size in this case.
There is no choice but to run through the list of entries for every address
if we did not find any entry in the previous iteration
Reset 'm' to NULL in that
On Mon, Sep 03, 2018 at 08:29:42PM -0500, Brijesh Singh wrote:
> Commit: 368a540e0232 (x86/kvmclock: Remove memblock dependency)
> caused SEV guest regression. When SEV is active, we map the shared
> variables (wall_clock and hv_clock_boot) with C=0 to ensure that both
> the guest and the hyperviso
On 09/04/2018 01:32 PM, Greg Kroah-Hartman wrote:
> On Tue, Sep 04, 2018 at 09:49:43AM +0530, Naresh Kamboju wrote:
>> On 3 September 2018 at 22:24, Greg Kroah-Hartman
>> wrote:
>>> This is the start of the stable review cycle for the 4.14.68 release.
>>> There are 165 patches in this series, all
Omar Sandoval wrote on Tue, Sep 04, 2018:
> On Wed, Aug 29, 2018 at 06:04:07AM +0200, Dominique Martinet wrote:
> > The 'm' kcore_list item can point to kclist_head, and it is incorrect to
> > look at m->addr / m->size in this case.
> > There is no choice but to run through the list of entries for
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Sean Christopherson
> Sent: Wednesday, September 5, 2018 4:36 AM
> To: Jarkko Sakkinen
> Cc: Huang, Kai ; platform-driver-...@vger.kernel.org;
> x...@
Quoting Lina Iyer (2018-09-04 14:09:34)
> On Mon, Aug 27 2018 at 14:01 -0600, Stephen Boyd wrote:
> >
> >Can't we just configure a different chained IRQ handler with
> >irq_set_chained_handler_and_data() for each of the GPIO IRQs that are
> >handled by PDC to be the interrupts provide by the PDC ir
Hi Michal,
Sorry for the delay in responding. I was traveling last week.
On 08/29/2018 05:08 AM, Michal Hocko wrote:
> On Tue 28-08-18 12:09:53, Shuah Khan wrote:
> [...]
>> The main intent is to use numa emulation in conjunction with cpusets for
>> coarse
>> memory management similar to x86_64
Hi Rob,
Rob Herring wrote on Mon, 27 Aug 2018 20:52:34 -0500:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Boris Brezillon
> Cc: Miquel Raynal
> Cc: Richard Weinberger
> Cc: David Woodhouse
> Cc:
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Thu, 23 Aug
2018 20:09:38 -0500:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Thu, 23 Aug
2018 14:33:32 -0500:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
1 - 100 of 582 matches
Mail list logo
