Document Amazon's Annapurna Labs Fabric Interrupt Controller SoC binding.
Signed-off-by: Talel Shenhar
---
.../interrupt-controller/amazon,al-fic.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/
This series introduces support for Amazon's Annapurna Labs Fabric Interrupt
Controller.
The Amazon's Annapurna Labs FIC (Fabric Interrupt Controller) has 32
inputs/sources. The output of this interrupt controller can be legacy-wired
output or, in case embedded inside PCIe devices, msi-x message. T
The FIC supports either a (single) wired output, or generation of an MSI-X
interrupt per input (for cases where it is embedded in a PCIe device,
hence, allowing the PCIe drivers to call this API).
This patch introduces the support for allowing the configuration of MSI-X
instead of a wire interrupt.
The Amazon's Annapurna Labs Fabric Interrupt Controller has 32 inputs
lines. A FIC (Fabric Interrupt Controller) may be cascaded into another FIC
or directly to the main CPU Interrupt Controller (e.g. GIC).
This driver introduces support for initialization based on device-tree
compatibility and ru
-next specific files for 20190604
git tree: linux-next
final crash:https://syzkaller.appspot.com/x/report.txt?x=1156fcd2a0
console output: https://syzkaller.appspot.com/x/log.txt?x=1656fcd2a0
kernel config: https://syzkaller.appspot.com/x/.config?x=4248d6bc70076f7d
dashboard link
From: Bai Ping
The system counter (sys_ctr) is a programmable system counter
which provides a shared time base to the Cortex A15, A7, A53 etc cores.
It is intended for use in applications where the counter is always
powered on and supports multiple, unrelated clocks. The sys_ctr hardware
supports
From: Bai Ping
Add the binding doc for nxp system counter timer module.
Signed-off-by: Bai Ping
Reviewed-by: Rob Herring
---
change v1->v2
- remove the blank line at EOF
change v2->v3
- update the binding example based on the driver change
change v3->v4
- no change
change v4->v5
- no chang
On 31. 05. 19, 3:27, Gen Zhang wrote:
> In sg_write(), the opcode of the command is fetched the first time from
> the userspace by __get_user(). Then the whole command, the opcode
> included, is fetched again from userspace by __copy_from_user().
> However, a malicious user can change the opcode
On 31. 05. 19, 3:14, Gen Zhang wrote:
> In clk_cpy_name(), '*dst_p'('parent->name'and 'parent->fw_name') and
> 'dst' are allcoted by kstrdup_const(). According to doc: "Strings
> allocated by kstrdup_const should be freed by kfree_const". So
> 'parent->name', 'parent->fw_name' and 'dst' should b
On Tue, May 28, 2019 at 10:26:33AM +0800, Yuantian Tang wrote:
> Add nxp sa56004 chip node for temperature monitor.
>
> Signed-off-by: Yuantian Tang
> ---
> v2:
> - change the node name and add vcc-supply
>
> arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 15 +++
> arch/a
On Mon, Jun 03, 2019 at 09:04:57PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 04, 2019 at 12:24:12AM +0530, Hariprasad Kelam wrote:
> > Knowing the fact that operator '|' is faster than '+'.
> > Its better we replace + with | in this case.
> >
> > Issue reported by coccicheck
> > drivers/stagi
On Mon, May 27, 2019 at 12:32:09PM +, Pramod Kumar wrote:
> Add "fsl,ls1046a-frwy" bindings for ls1046afrwy board based on ls1046a SoC
>
> Signed-off-by: Vabhav Sharma
> Signed-off-by: Pramod Kumar
> Reviewed-by: Rob Herring
I cannot apply patch from message using 'Content-Transfer-Encodin
On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
[..]
> @@ -373,7 +416,7 @@ static int dwc3_qcom_clk_init(struct dwc3_qcom *qcom, int
> count)
>
> qcom->num_clocks = count;
>
> - if (!count)
> + if (!count |
On 30. 05. 19, 11:39, Gen Zhang wrote:
> In d_parse_params(), 'params_orig' is allocated by kstrdup(). It returns
> NULL when fails. So 'params_orig' should be checked.
>
> Signed-off-by: Gen Zhang
> ---
> diff --git a/include/linux/wimax/debug.h b/include/linux/wimax/debug.h
> index aaf24ba..bac
On 30. 05. 19, 11:04, Gen Zhang wrote:
> In debug_string_to_mask(), 'strsep_fodder' is allocated by kstrdup().
> It returns NULL when fails. So 'strsep_fodder' should be checked.
>
> Signed-off-by: Gen Zhang
> ---
> diff --git a/fs/orangefs/orangefs-debugfs.c b/fs/orangefs/orangefs-debugfs.c
> in
On Tue, 04 Jun 2019, Robert Hancock wrote:
> The logic for setting the of_node on devices created by mfd did not set
> the fwnode pointer to match, which caused fwnode-based APIs to
> malfunction on these devices since the fwnode pointer was null. Fix
> this.
>
> Signed-off-by: Robert Hancock
>
On Tue, 04 Jun 2019, Robert Hancock wrote:
> Previously the MFD core supported assigning OF nodes to created MFD
> devices, but relied solely on matching the of_compatible string. This
> would result in devices being potentially assigned the wrong node if
> there are multiple devices with the same
On 05/06/19 11:46 AM, Lokesh Vutla wrote:
On 05/06/19 11:38 AM, Keerthy wrote:
Add gpio0 node under wakeup domain. This has 56 gpios
and all are capable of generating banked interrupts.
Signed-off-by: Keerthy
---
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++
1 file c
On 25. 05. 19, 4:03, Gen Zhang wrote:
> devm_kmalloc() is used to allocate memory for a driver dev. Comments
> above the definition and doc
> (https://www.kernel.org/doc/Documentation/driver-model/devres.txt) all
> imply that allocated the memory is automatically freed on driver attach,
> no matte
Hi, Guenter
> -Original Message-
> From: Guenter Roeck On Behalf Of Guenter Roeck
> Sent: Sunday, May 12, 2019 9:28 PM
> To: Anson Huang ; robh...@kernel.org;
> mark.rutl...@arm.com; w...@linux-watchdog.org; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gm
On Wed, 5 Jun 2019 at 07:25, Kees Cook wrote:
>
> While the gcc plugin for automatic stack variable initialization (i.e.
> CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL) performs initialization with
> 0x00 bytes, the Clang automatic stack variable initialization (i.e.
> CONFIG_INIT_STACK_ALL) uses variou
Hi Will,
Is this series applicable to arm64 tree?
Thanks.
On Mon, May 27, 2019 at 5:37 PM Masahiro Yamada
wrote:
>
>
> Some in-kernel headers use _BITUL() instead of BIT().
>
> arch/arm64/include/asm/sysreg.h
> arch/s390/include/asm/*.h
>
> I think the reason is because BIT() is currently not
On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> The Qualcomm Geni I2C driver currently probes silently which can be
> confusing when debugging potential issues. Add a low level (INFO)
> print when each I2C controller is successfully initially set-up.
>
> Signed-off-by: Lee Jones
> ---
> drive
On Fri, May 24, 2019 at 03:30:22PM +0800, Peng Ma wrote:
> Change the sata node to enable sata.
>
> Signed-off-by: Peng Ma
Applied, thanks.
> The following patches add the bare minimum tracepoints required to perform EAS
> testing in Lisa[1].
What is EAS? Whhy is "Lisa" not part of the patch submission?
submission.
> It is done in this way because adding new TRACE_EVENTS() is no longer accepted
> AFAIU.
Huh? We keep adding trace e
On 05/06/19 11:38 AM, Keerthy wrote:
> Add gpio0 node under wakeup domain. This has 56 gpios
> and all are capable of generating banked interrupts.
>
> Signed-off-by: Keerthy
> ---
> arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++
> 1 file changed, 15 insertions(+)
>
> diff
On 2019-05-31 23:09, Jens Axboe wrote:
On 5/31/19 1:45 PM, Roman Penyaev wrote:
On 2019-05-31 18:54, Jens Axboe wrote:
On 5/31/19 10:02 AM, Roman Penyaev wrote:
On 2019-05-31 16:48, Jens Axboe wrote:
On 5/16/19 2:57 AM, Roman Penyaev wrote:
Hi all,
This is v3 which introduces pollable epoll
On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> This patch provides basic support for booting with ACPI instead
> of the currently supported Device Tree. When doing so there are a
> couple of differences which we need to taken into consideration.
>
> Firstly, the SDM850 ACPI tables omit informa
On 4/6/19 10:12 pm, Masahiro Yamada wrote:
On Tue, Jun 4, 2019 at 8:54 PM Frederic Barrat wrote:
Le 04/06/2019 à 13:16, Masahiro Yamada a écrit :
Linux kernel tolerates C++ style comments these days. Actually, the
SPDX License tags for .c files start with //.
On the other hand, uapi header
On Fri, May 24, 2019 at 02:39:12PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> Build in CONFIG_NVMEM_IMX_OCOTP_SCU.
>
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc: Shawn Guo
> Cc: Andy Gross
> Cc: Maxime Ripard
> Cc: Olof Johansson
> Cc: Jagan Teki
> Cc: Bjorn Andersson
> Cc: Leo
Hi all,
Changes since 20190604:
The tpmdd tree gained a build failure so I used the version from
next-20190504.
Non-merge commits (relative to Linus' tree): 3901
4307 files changed, 159819 insertions(+), 159401 dele
Enable GPIO_DAVINCI and related configs for TI K3 AM6 platforms.
Signed-off-by: Keerthy
---
arch/arm64/configs/defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index d1b72f99e2f4..57d7a4c207bd 100644
--- a/arch/arm64/con
On Wed, Jun 05, 2019 at 06:09:12AM +, Anson Huang wrote:
> Hi, Shawn
>
> > -Original Message-
> > From: Shawn Guo
> > Sent: Wednesday, June 5, 2019 2:00 PM
> > To: Anson Huang
> > Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@linux-watchdog.org;
> > li...@roeck-us.net; s.ha...@p
Hi, Shawn
> -Original Message-
> From: Shawn Guo
> Sent: Wednesday, June 5, 2019 2:00 PM
> To: Anson Huang
> Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@linux-watchdog.org;
> li...@roeck-us.net; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com; Aisheng Dong ;
>
On Fri, May 24, 2019 at 01:51:00PM +0800, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> of_node_put() is called after of_match_node() successfully called,
> then in the following error handling, of_node_put() is called again
> which is unnecessary, this patch adjusts the location of of_node_
Add gpio0 node under wakeup domain. This has 56 gpios
and all are capable of generating banked interrupts.
Signed-off-by: Keerthy
---
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
b/arch
Add gpio0/1 nodes under main domain. They have 96 and 90 gpios
respectively and all are capable of generating banked interrupts.
Signed-off-by: Keerthy
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/t
K3 AM6 platform has 2 instances of gpio banks on main domain
and 1 instance on wakeup domin. All are capable of generating
banked interrupts.
This series also adds 2 goio_keys nodes connected to SW6 SW5
switches and tested for gpio_keys interrupts.
The series depends on:
https://patchwork.kernel.
There are 2 push buttons: SW5 and SW6 that are basically connected to
WKUP_GPIO0_24 and WKUP_GPIO0_27 respectively. Add the respective
nodes and the pinctrl data to set the mode to GPIO and Input.
Signed-off-by: Keerthy
---
.../arm64/boot/dts/ti/k3-am654-base-board.dts | 27 +++
On 23. 05. 19, 16:44, Gen Zhang wrote:
> In wl1271_probe(), 'glue->core' is allocated by platform_device_alloc(),
> when this allocation fails, ENOMEM is returned. However, 'pdev_data'
> and 'glue' are allocated by devm_kzalloc() before 'glue->core'. When
> platform_device_alloc() returns NULL, we
In __alloc_pages_node, there is a VM_BUG_ON on the condition (nid < 0 ||
nid >= MAX_NUMNODES). Remove this VM_BUG_ON and add a VM_WARN_ON, if the
condition fails and fail the allocation if an invalid NUMA node id is
passed to __alloc_pages_node.
The check (nid < 0 || nid >= MAX_NUMNODES) also cons
On Tue, Jun 04, 2019 at 10:22:05PM -0700, Joe Perches wrote:
> On Wed, 2019-06-05 at 07:10 +0200, Greg KH wrote:
> > On Wed, Jun 05, 2019 at 01:10:41PM +0900, Masahiro Yamada wrote:
> > > On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
> []
> > > This means we cannot reliably use uint{8,16,32,
On Tue 04 Jun 22:50 PDT 2019, Avri Altman wrote:
> Hi,
>
> >
> > On Tue, Jun 4, 2019 at 12:22 AM Bjorn Andersson
> > wrote:
> > >
> > > This series exposes the ufs_reset line as a gpio, adds support for ufshcd
> > > to
> > > acquire and toggle this and then adds this to SDM845 MTP.
> > >
> > >
On Tue, Jun 04, 2019 at 09:06:28AM +, Anson Huang wrote:
> Hi, Shawn
> The driver and binding doc are already reviewed and waiting for DT
> patch, will you help review this DT patch?
I'm fine with it. Should I just pick this patch up, or is there any
dependency we need to handle?
Shaw
On 23. 05. 19, 4:38, Gen Zhang wrote:
> In sg_write(), the opcode of the command is fetched the first time from
> the userspace by __get_user(). Then the whole command, the opcode
> included, is fetched again from userspace by __copy_from_user().
> However, a malicious user can change the opcode
Fix the compiler warning with ARM64 config enabled
as the current mask assumes 32 bit by default.
Signed-off-by: Keerthy
---
drivers/gpio/gpio-davinci.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
index 3bbf5
Add K3 dependencies to enable the driver on K3 platforms.
Signed-off-by: Keerthy
---
drivers/gpio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 62f3fe06cd2f..28dba62e2219 100644
--- a/drivers/gpio/Kconfig
+++ b/drive
K3 AM6 platform has 2 instances of gpio banks on main domain
and 1 instance on wakeup domin. All are capable of generating
banked interrupts.
Keerthy (2):
gpio: davinci: Fix the compiler warning with ARM64 config enabled
gpio: Davinci: Add K3 Specific dependencies
drivers/gpio/Kconfig
-off-by: Randy Dunlap
Cc: Sean Wang
Cc: John Crispin
Cc: Felix Fietkau
Cc: Nelson Chang
---
drivers/net/ethernet/mediatek/Makefile |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20190604.orig/drivers/net/ethernet/mediatek/Makefile
+++ linux-next-20190604/drivers/n
Hi,
>
> On Tue, Jun 4, 2019 at 12:22 AM Bjorn Andersson
> wrote:
> >
> > This series exposes the ufs_reset line as a gpio, adds support for ufshcd to
> > acquire and toggle this and then adds this to SDM845 MTP.
> >
> > Bjorn Andersson (3):
> > pinctrl: qcom: sdm845: Expose ufs_reset as gpio
>
On Mon, May 06, 2019 at 07:52:03PM +0100, Tom Murphy via iommu wrote:
> We can remove the mutex lock from amd_iommu_map and amd_iommu_unmap.
> iommu_map doesn’t lock while mapping and so no two calls should touch
> the same iova range. The AMD driver already handles the page table page
> allocation
From: Nikhil Badola
Set USB_EN bit to select ULPI phy for USB controller version 2.5
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
drivers/usb/host/ehci-fsl.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/host/ehci-fsl.c b/drivers/usb/host/ehci-fsl.c
index
This patch is to add member has_fsl_erratum_a006918 in platform data
Signed-off-by: Yinbo Zhu
---
include/linux/fsl_devices.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/fsl_devices.h b/include/linux/fsl_devices.h
index cb2b46f57af3..5d231ce8709b 100644
--- a/include/linux/
From: Nikhil Badola
Remove USB errata checking code from driver. Applicability of erratum
is retrieved by reading corresponding property in device tree.
This property is written during device tree fixup.
Signed-off-by: Ramneek Mehresh
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
From: Ramneek Mehresh
USB erratum-A006918 workaround tries to start internal PHY inside
uboot (when PLL fails to lock). However, if the workaround also
fails, then USB initialization is also stopped inside Linux.
Erratum-A006918 workaround failure creates "fsl,erratum_a006918"
node in device-tree
From: Suresh Gupta
PHY_CLK_VALID bit for UTMI PHY in USBDR does not set even
if PHY is providing valid clock. Workaround for this
involves resetting of PHY and check PHY_CLK_VALID bit
multiple times. If PHY_CLK_VALID bit is still not set even
after 5 retries, it would be safe to deaclare that PHY
cpu_to_le32/le32_to_cpu is defined in include/linux/byteorder/generic.h,
which is not exported to user-space.
UAPI headers must use the ones prefixed with double-underscore.
Detected by compile-testing exported headers:
./usr/include/linux/nilfs2_ondisk.h: In function
‘nilfs_checkpoint_set_snap
On Tue, May 14, 2019 at 2:39 AM Bjorn Andersson
wrote:
>
> Bring in the Truly display and enable the DSI channels to make the
> mdss/gpu probe, even though we're lacking LABIB, preventing us from
> seeing anything on the screen.
>
> Signed-off-by: Bjorn Andersson
> ---
Looks good to me and work
While the gcc plugin for automatic stack variable initialization (i.e.
CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL) performs initialization with
0x00 bytes, the Clang automatic stack variable initialization (i.e.
CONFIG_INIT_STACK_ALL) uses various type-specific patterns that are
typically 0xAA. Therefo
On Wed, 2019-06-05 at 07:10 +0200, Greg KH wrote:
> On Wed, Jun 05, 2019 at 01:10:41PM +0900, Masahiro Yamada wrote:
> > On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
[]
> > This means we cannot reliably use uint{8,16,32,64}_t in UAPI headers.
>
> We should not be doing that as they are in
On Wed, Jun 05, 2019 at 01:10:41PM +0900, Masahiro Yamada wrote:
> On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
> > > > >
> > > > > There are two ways to define fixed-width type.
> > > > >
> > > > > [1] #include , __u8, __u16, __u32, __u64
> > > > >
> > > > > vs
> > > > >
> > > > > [2
On Tue, Jun 04, 2019 at 07:21:16PM -0400, Sasha Levin wrote:
> From: Venkata Narendra Kumar Gutta
>
> [ Upstream commit edb16da34b084c66763f29bee42b4e6bb33c3d66 ]
>
> Platform core is using pdev->name as the platform device name to do
> the binding of the devices with the drivers. But, when the
On 29. 05. 19, 3:53, Gen Zhang wrote:
> In wcd9335_codec_enable_dec(), 'widget_name' is allocated by kstrndup().
> However, according to doc: "Note: Use kmemdup_nul() instead if the size
> is known exactly."
Except the size is not known exactly. It is at most 15, not 15. Right?
> So we should use
On Wed, Jun 5, 2019 at 4:16 AM Stephen Boyd wrote:
>
> Quoting Bjorn Andersson (2019-06-04 15:37:00)
> > On Tue 04 Jun 15:29 PDT 2019, Stephen Boyd wrote:
> >
> > > The SMMU that sits in front of the QUP needs to be programmed properly
> > > so that the i2c geni driver can allocate DMA descriptors
The powered flag should be set for any other phys anyway. Otherwise,
after we have revised the device tree for the usb phy, the following
warning happened during a second system suspend. So, this patch fixes
the issue.
[ 56.026531] unbalanced disables for USB20_VBUS0
[ 56.031108] WARNING: CPU:
On 2019/6/5 1:24 上午, Bjørn Forsman wrote:
> On Tue, 4 Jun 2019 at 17:41, Coly Li wrote:
>>
>> On 2019/6/4 10:59 下午, Coly Li wrote:
>>> On 2019/6/4 7:00 下午, Bjørn Forsman wrote:
Hi all,
I get a kernel oops from bcache when writing to
/sys/block/bcache0/bcache/writeback_percent a
On Tue, Jun 4, 2019 at 7:45 PM Roman Gushchin wrote:
>
> Johannes noticed that reading the memcg kmem_cache pointer in
> cache_from_memcg_idx() is performed using READ_ONCE() macro,
> which doesn't implement a SMP barrier, which is required
> by the logic.
>
> Add a proper smp_rmb() to be paired w
On Thu 31 Jan 07:41 PST 2019, Xiang Xiao wrote:
> Hi,
> This series enhance the buffer allocation by:
> 1.Support the different buffer number in rx/tx direction
> 2.Get the individual rx/tx buffer size from config space
>
> Here is the related OpenAMP change:
> https://github.com/OpenAMP/open-amp
On Tue, Jun 04, 2019 at 10:42:22AM -0500, Gustavo A. R. Silva wrote:
> Make use of the struct_size() helper instead of an open-coded version
> in order to avoid any potential type mistakes, in particular in the
> context in which this code is being used.
What does "in particular in the context in
On Tue, 4 Jun 2019 19:44:44 -0700 Roman Gushchin wrote:
> So instead of trying to find a maybe non-existing balance, let's do reparent
> the accounted slabs to the parent cgroup on cgroup removal.
s/slabs/slab caches/. Take more care with the terminology, please...
> There is a bonus: currentl
On Wed, Jun 5, 2019 at 3:21 AM Arnd Bergmann wrote:
> > > >
> > > > There are two ways to define fixed-width type.
> > > >
> > > > [1] #include , __u8, __u16, __u32, __u64
> > > >
> > > > vs
> > > >
> > > > [2] #include , uint8_t, uint16_t, uint32_t, uint64_t
> > > >
> > > >
> > > > Both are
On 6/3/19 11:09 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190603:
>
on x86_64:
when GPIOLIB is not set/enabled:
../drivers/staging/iio/addac/adt7316.c: In function ‘adt7316_store_update_DAC’:
../drivers/staging/iio/addac/adt7316.c:947:3: error: implicit declaration of
function
Hi Geert-san,
Thank you very much for your report!
> From: Geert Uytterhoeven, Sent: Wednesday, June 5, 2019 3:06 AM
>
> Hi Shimoda-san,
>
> Using a tree based on renesas-drivers-2019-06-04-v5.2-rc3, I started seeing
> the following warning during a second system suspend (s2idle):
> So far I'v
On 2019.06.04 17:55:32 +0800, Tina Zhang wrote:
> Caps the number of irqs with fixed indexes and uses capability chains
> to chain device specific irqs.
>
> VFIO vGPU leverages this mechanism to trigger primary plane and cursor
> plane page flip event to the user space.
>
> Signed-off-by: Tina Zh
On Wed, Jun 05, 2019 at 10:21:17AM +0800, Herbert Xu wrote:
> On Tue, Jun 04, 2019 at 02:14:49PM -0700, Paul E. McKenney wrote:
> >
> > Yeah, I know, even with the "volatile" keyword, it is not entirely clear
> > how much reordering the compiler is allowed to do. I was relying on
> > https://gcc.g
Hey Andry,
Long time no seeing :-)
On Tue, Jun 04, 2019 at 08:16:11PM +0300, Andy Shevchenko wrote:
> On Thu, May 30, 2019 at 09:33:46PM -0700, Eduardo Valentin wrote:
> > From: Haiyue Wang
> >
> > Some protocols over I2C are designed for bi-directional transferring
> > messages by using I2C Ma
From: Vladimir Oltean
Date: Tue, 4 Jun 2019 20:07:39 +0300
> This patchset adds the following:
>
> - A timecounter/cyclecounter based PHC for the free-running
>timestamping clock of this switch.
>
> - A state machine implemented in the DSA tagger for SJA1105, which
>keeps track of me
Hi Linus,
Please pull these pstore fixes for v5.2-rc4. They've been in linux-next
for a bit now and catch some pstore corner cases found recently.
Thanks!
-Kees
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are availab
On Tue, Jun 4, 2019 at 7:07 PM maowenan wrote:
>
>
>
> On 2019/6/4 23:24, Eric Dumazet wrote:
> > On Tue, Jun 4, 2019 at 7:47 AM Mao Wenan wrote:
> >>
> >> There is one issue about bonding mode BOND_MODE_BROADCAST, and
> >> two slaves with diffierent affinity, so packets will be handled
> >> by d
From: Rasmus Villemoes
Date: Tue, 4 Jun 2019 07:34:22 +
> This adds support for the mv88e6250 chip. Initially based on the
> mv88e6240, this time around, I've been through each ->ops callback and
> checked that it makes sense, either replacing with a 6250 specific
> variant or dropping it if
this patch add SPI_LSB_FIRST feature support.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c | 15 ++-
include/linux/platform_data/spi-mt65xx.h |2 --
2 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/s
From: Ronak Doshi
Date: Mon, 3 Jun 2019 23:58:38 -0700
> Currently, when rx csum is disabled, vmxnet3 driver does not turn
> off lro, which can cause performance issues if user does not turn off
> lro explicitly. This patch adds fix_features support which is used to
> turn off LRO whenever RXCSUM
Dear Sir/Madam,
Invest-Capital, gives you an opportunity to grow your business and bring
happiness to your loved ones through hassle-free loans.
We provide international loan for corporate and private entities around the
world.
Attractive interest rates 4%
For further details please contacts us
From: Miaohe Lin
Date: Tue, 4 Jun 2019 06:07:34 +
> There's some NICs, such as hinic, with NETIF_F_IP_CSUM and NETIF_F_TSO
> on but NETIF_F_HW_CSUM off. And ipvlan device features will be
> NETIF_F_TSO on with NETIF_F_IP_CSUM and NETIF_F_IP_CSUM both off as
> IPVLAN_FEATURES only care about N
On Tue, Jun 04, 2019 at 12:58:01PM -0700, Sean Christopherson wrote:
> On Wed, May 22, 2019 at 03:00:55PM +0800, Yang Weijiang wrote:
> > CET SHSTK and IBT features are introduced here so that
> > CPUID.(EAX=7, ECX=0):ECX[bit 7] and EDX[bit 20] reflect them.
> > CET xsave components for supervisor
Let's separate the page counter modification code out of
__memcg_kmem_uncharge() in a way similar to what
__memcg_kmem_charge() and __memcg_kmem_charge_memcg() work.
This will allow to reuse this code later using a new
memcg_kmem_uncharge_memcg() wrapper, which calls
__memcg_kmem_uncharge_memcg()
The delayed work/rcu deactivation infrastructure of non-root
kmem_caches can be also used for asynchronous release of these
objects. Let's get rid of the word "deactivation" in corresponding
names to make the code look better after generalization.
It's easier to make the renaming first, so that th
Currently the memcg_params.dying flag and the corresponding
workqueue used for the asynchronous deactivation of kmem_caches
is synchronized using the slab_mutex.
It makes impossible to check this flag from the irq context,
which will be required in order to implement asynchronous release
of kmem_c
Currently each charged slab page holds a reference to the cgroup to
which it's charged. Kmem_caches are held by the memcg and are released
all together with the memory cgroup. It means that none of kmem_caches
are released unless at least one reference to the memcg exists, which
is very far from op
Initialize kmem_cache->memcg_params.memcg pointer in
memcg_link_cache() rather than in init_memcg_params().
Once kmem_cache will hold a reference to the memory cgroup,
it will simplify the refcounting.
For non-root kmem_caches memcg_link_cache() is always called
before the kmem_cache becomes visi
Currently the page accounting code is duplicated in SLAB and SLUB
internals. Let's move it into new (un)charge_slab_page helpers
in the slab_common.c file. These helpers will be responsible
for statistics (global and memcg-aware) and memcg charging.
So they are replacing direct memcg_(un)charge_sla
Let's reparent memcg slab memory on memcg offlining. This allows us
to release the memory cgroup without waiting for the last outstanding
kernel object (e.g. dentry used by another application).
So instead of reparenting all accounted slab pages, let's do reparent
a relatively small amount of kmem
Currently SLUB uses a work scheduled after an RCU grace period
to deactivate a non-root kmem_cache. This mechanism can be reused
for kmem_caches release, but requires generalization for SLAB
case.
Introduce kmemcg_cache_deactivate() function, which calls
allocator-specific __kmem_cache_deactivate(
# Why do we need this?
We've noticed that the number of dying cgroups is steadily growing on most
of our hosts in production. The following investigation revealed an issue
in userspace memory reclaim code [1], accounting of kernel stacks [2],
and also the mainreason: slab objects.
The underlying
Johannes noticed that reading the memcg kmem_cache pointer in
cache_from_memcg_idx() is performed using READ_ONCE() macro,
which doesn't implement a SMP barrier, which is required
by the logic.
Add a proper smp_rmb() to be paired with smp_wmb() in
memcg_create_kmem_cache().
The same applies to me
Every slab page charged to a non-root memory cgroup has a pointer
to the memory cgroup and holds a reference to it, which protects
a non-empty memory cgroup from being released. At the same time
the page has a pointer to the corresponding kmem_cache, and also
hold a reference to the kmem_cache. And
On Tue, Jun 4, 2019 at 10:25 PM Arnaud Pouliquen
wrote:
>
> Hello Xiang,
>
> On 5/9/19 3:00 PM, xiang xiao wrote:
> > On Thu, May 9, 2019 at 8:36 PM Arnaud Pouliquen
> > wrote:
> >>
> >> Hello Xiang,
> >>
> >> Similar mechanism has been proposed by Loic 2 years ago (link to the
> >> series here
Nathan,
> clang warns:
>
> drivers/scsi/ibmvscsi/ibmvscsi.c:2126:7: warning: variable 'rc' is used
> uninitialized whenever switch case is taken [-Wsometimes-uninitialized]
> case IBMVSCSI_HOST_ACTION_NONE:
> ^
Applied to 5.3/scsi-queue, thanks!
--
Shakeel Butt 于2019年6月5日周三 上午1:12写道：
>
> On Sun, Jun 2, 2019 at 2:47 AM Hui Zhu wrote:
> >
> > This is the second version that was updated according to the comments
> > from Sergey Senozhatsky in https://lkml.org/lkml/2019/5/29/73
> >
> > zswap compresses swap pages into a dynamically allocated RA
On Tue, Jun 04, 2019 at 07:46:13AM -0700, Sean Christopherson wrote:
> On Wed, May 22, 2019 at 03:00:54PM +0800, Yang Weijiang wrote:
> > CET(Control-flow Enforcement Technology) is an upcoming Intel® processor
> > family feature that blocks return/jump-oriented programming (ROP) attacks.
> > It pr
1 - 100 of 1233 matches
Mail list logo
