[PATCH 1/9] scsi: ufs: Allowing power mode change

From: Yaniv Gardi Due to M-PHY issues, moving from HS to any other mode or gear or even Hibern8 causes some un-predicted behavior of the device. This patch fixes this issues. Signed-off-by: Yaniv Gardi Signed-off-by: Subhash Jadavani Signed-off-by: Can Guo Signed-off-by: Asutosh Das ---

[PATCH 3/9] scsi: ufs: fix exception event handling

From: Maya Erez The device can set the exception event bit in one of the response UPIU, for example to notify the need for urgent BKOPs operation. In such a case the host driver calls ufshcd_exception_event_handler to handle this notification. When trying to check the exception event status (for

[PATCH 2/9] scsi: ufs: Add LCC quirk for host and device

From: Subhash Jadavani LCC (Line Control Command) is being used for communication between UFS host and UFS device. But some hosts might have the issue with issuing the LCC commands to UFS device and in this case LCC could be explicitly disabled. But there could be a

[PATCH 2/9] scsi: ufs: Add LCC quirk for host and device

From: Subhash Jadavani LCC (Line Control Command) is being used for communication between UFS host and UFS device. But some hosts might have the issue with issuing the LCC commands to UFS device and in this case LCC could be explicitly disabled. But there could be a need where we don't want to

[PATCH 5/9] scsi: ufs: add reference counting for scsi block requests

From: Subhash Jadavani Currently we call the scsi_block_requests()/scsi_unblock_requests() whenever we want to block/unblock scsi requests but as there is no reference counting, nesting of these calls could leave us in undesired state sometime. Consider following call

[PATCH 5/9] scsi: ufs: add reference counting for scsi block requests

From: Subhash Jadavani Currently we call the scsi_block_requests()/scsi_unblock_requests() whenever we want to block/unblock scsi requests but as there is no reference counting, nesting of these calls could leave us in undesired state sometime. Consider following call flow sequence: 1. func1()

[PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

From: Vijay Viswanath UFS driver can receive a request during memory reclaim by kswapd. So when ufs driver puts the ungate work in queue, and if there are no idle workers, kthreadd is invoked to create a new kworker. Since kswapd task holds a mutex which kthreadd also

[PATCH 4/9] scsi: ufshcd: fix possible unclocked register access

From: Subhash Jadavani vendor specific setup_clocks ops may depend on clocks managed by ufshcd driver so if the vendor specific setup_clocks callback is called when the required clocks are turned off, it results into unclocked register access. This change make sure that

[PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

From: Vijay Viswanath UFS driver can receive a request during memory reclaim by kswapd. So when ufs driver puts the ungate work in queue, and if there are no idle workers, kthreadd is invoked to create a new kworker. Since kswapd task holds a mutex which kthreadd also needs, this can cause a

[PATCH 4/9] scsi: ufshcd: fix possible unclocked register access

From: Subhash Jadavani vendor specific setup_clocks ops may depend on clocks managed by ufshcd driver so if the vendor specific setup_clocks callback is called when the required clocks are turned off, it results into unclocked register access. This change make sure that required clocks are

[PATCH 6/9] scsi: ufs-qcom: remove broken hci version quirk

From: Subhash Jadavani UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION is only applicable for QCOM UFS host controller version 2.x.y and this has been fixed from version 3.x.y onwards, hence this change removes this quirk for version 3.x.y onwards. Signed-off-by: Subhash Jadavani

[PATCH 6/9] scsi: ufs-qcom: remove broken hci version quirk

From: Subhash Jadavani UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION is only applicable for QCOM UFS host controller version 2.x.y and this has been fixed from version 3.x.y onwards, hence this change removes this quirk for version 3.x.y onwards. Signed-off-by: Subhash Jadavani Signed-off-by: Asutosh

[PATCH 7/9] scsi: ufs: make sure all interrupts are processed

From: Venkat Gopalakrishnan As multiple requests are submitted to the ufs host controller in parallel there could be instances where the command completion interrupt arrives later for a request that is already processed earlier as the corresponding doorbell was cleared

[PATCH 7/9] scsi: ufs: make sure all interrupts are processed

From: Venkat Gopalakrishnan As multiple requests are submitted to the ufs host controller in parallel there could be instances where the command completion interrupt arrives later for a request that is already processed earlier as the corresponding doorbell was cleared when handling the previous

Re: [PATCH 11/23] kconfig: add 'shell-stdout' function

2018-02-20 3:01 GMT+09:00 Linus Torvalds : > On Mon, Feb 19, 2018 at 9:44 AM, Linus Torvalds > wrote: >> >> I do like your "success"/"stdout" more than "shell"/"shell-stdout", >> because with that naming I don't get the feeling that

Re: [PATCH 11/23] kconfig: add 'shell-stdout' function

2018-02-20 3:01 GMT+09:00 Linus Torvalds : > On Mon, Feb 19, 2018 at 9:44 AM, Linus Torvalds > wrote: >> >> I do like your "success"/"stdout" more than "shell"/"shell-stdout", >> because with that naming I don't get the feeling that one should >> subsume the other. > > Hmm. Thinking about it some

[PATCH] ocxl: Add get_metadata IOCTL to share OCXL information to userspace

From: Alastair D'Silva Some required information is not exposed to userspace currently (eg. the PASID), pass this information back, along with other information which is currently communicated via sysfs, which saves some parsing effort in userspace. Signed-off-by: Alastair

[PATCH] ocxl: Add get_metadata IOCTL to share OCXL information to userspace

From: Alastair D'Silva Some required information is not exposed to userspace currently (eg. the PASID), pass this information back, along with other information which is currently communicated via sysfs, which saves some parsing effort in userspace. Signed-off-by: Alastair D'Silva ---

Pls assist me to come and establish an industry in your country

Genuine offer How are you today and your family, I am a citizen of Sudan but currently staying in Burkina Faso. My name is Miss Mariam Dim Deng, 25years old originated from Sudan. My late father Dr. Dominic Dim Deng was the former Minister for SPLA Affair and Special Adviser to President Salva

Pls assist me to come and establish an industry in your country

Genuine offer How are you today and your family, I am a citizen of Sudan but currently staying in Burkina Faso. My name is Miss Mariam Dim Deng, 25years old originated from Sudan. My late father Dr. Dominic Dim Deng was the former Minister for SPLA Affair and Special Adviser to President Salva

Re: [PATCH v2 1/1] clk: npcm750: update text with fixed clocks

On Mon, Feb 19, 2018 at 6:49 AM, Rob Herring wrote: > On Thu, Feb 15, 2018 at 02:38:12PM -0800, Brendan Higgins wrote: >> On Thu, Feb 15, 2018 at 5:39 AM, Tali Perry wrote: >> > >> > Signed-off-by: Tali Perry >> > >> >> >> I think

Re: [PATCH v2 1/1] clk: npcm750: update text with fixed clocks

On Mon, Feb 19, 2018 at 6:49 AM, Rob Herring wrote: > On Thu, Feb 15, 2018 at 02:38:12PM -0800, Brendan Higgins wrote: >> On Thu, Feb 15, 2018 at 5:39 AM, Tali Perry wrote: >> > >> > Signed-off-by: Tali Perry >> > >> >> >> I think this should probably be rolled into [PATCH v2 1/1] npcm750:

Re: [PATCH 10/23] stack-protector: test compiler capability in Kconfig and drop AUTO mode

2018-02-17 3:38 GMT+09:00 Masahiro Yamada : > Add CC_HAS_STACKPROTECTOR(_STRONG) to test if the compiler supports > -fstack-protector(-strong) option. > > X86 has additional shell scripts in case the compiler supports the > option, but generates broken code. I added

Re: [PATCH 10/23] stack-protector: test compiler capability in Kconfig and drop AUTO mode

2018-02-17 3:38 GMT+09:00 Masahiro Yamada : > Add CC_HAS_STACKPROTECTOR(_STRONG) to test if the compiler supports > -fstack-protector(-strong) option. > > X86 has additional shell scripts in case the compiler supports the > option, but generates broken code. I added CC_HAS_SANE_STACKPROTECTOR >

[PATCH 2/2] ASoC: support ROHM BD28623 codec

This patch adds support of the ROHM BD28623MUV Class D speaker amplifier for Flat-panel TVs. This IC delivers an output power of 20W + 20W. Signed-off-by: Katsuhiro Suzuki --- sound/soc/codecs/Kconfig | 8 ++ sound/soc/codecs/Makefile | 2 +

[PATCH 2/2] ASoC: support ROHM BD28623 codec

This patch adds support of the ROHM BD28623MUV Class D speaker amplifier for Flat-panel TVs. This IC delivers an output power of 20W + 20W. Signed-off-by: Katsuhiro Suzuki --- sound/soc/codecs/Kconfig | 8 ++ sound/soc/codecs/Makefile | 2 + sound/soc/codecs/bd28623.c | 258

[PATCH 0/2] ASoC: add support for ROHM BD28623 codec

This patch adds support for ROHM BD28623MUV class D speaker amplifier codec driver. This driver only refers information of HW specification document that can be derivered at website of ROHM. http://www.rohm.com/web/global/products/-/product/BD28623MUV Katsuhiro Suzuki (2): ASoC: add DT

[PATCH 0/2] ASoC: add support for ROHM BD28623 codec

This patch adds support for ROHM BD28623MUV class D speaker amplifier codec driver. This driver only refers information of HW specification document that can be derivered at website of ROHM. http://www.rohm.com/web/global/products/-/product/BD28623MUV Katsuhiro Suzuki (2): ASoC: add DT

[PATCH 1/2] ASoC: add DT bindings documentation for ROHM BD28623 codec

This patch adds DT bindings documentation for ROHM BD28623MUV class D speaker amplifier. Signed-off-by: Katsuhiro Suzuki --- .../devicetree/bindings/sound/rohm,bd28623.txt | 26 ++ 1 file changed, 26 insertions(+) create mode 100644

[PATCH 1/2] ASoC: add DT bindings documentation for ROHM BD28623 codec

This patch adds DT bindings documentation for ROHM BD28623MUV class D speaker amplifier. Signed-off-by: Katsuhiro Suzuki --- .../devicetree/bindings/sound/rohm,bd28623.txt | 26 ++ 1 file changed, 26 insertions(+) create mode 100644

[PATCH RFC] kbuild: drop superfluous GCC_PLUGINS_CFLAGS assignment

GCC_PLUGINS_CFLAGS is already in the environment, so it is superfluous to add it in commanline of final build of init/ Signed-off-by: Cao jin --- This is only tested with Randomizing Structure Layout plugin. The test method is not so grace but I think it can prove the

[PATCH RFC] kbuild: drop superfluous GCC_PLUGINS_CFLAGS assignment

GCC_PLUGINS_CFLAGS is already in the environment, so it is superfluous to add it in commanline of final build of init/ Signed-off-by: Cao jin --- This is only tested with Randomizing Structure Layout plugin. The test method is not so grace but I think it can prove the correctness of this patch.

Re: [PATCH 5/6] mm, hugetlb: further simplify hugetlb allocation API

On Wed, Jan 03, 2018 at 10:32:12AM +0100, Michal Hocko wrote: > From: Michal Hocko > > Hugetlb allocator has several layer of allocation functions depending > and the purpose of the allocation. There are two allocators depending > on whether the page can be allocated from the

Re: [PATCH 5/6] mm, hugetlb: further simplify hugetlb allocation API

On Wed, Jan 03, 2018 at 10:32:12AM +0100, Michal Hocko wrote: > From: Michal Hocko > > Hugetlb allocator has several layer of allocation functions depending > and the purpose of the allocation. There are two allocators depending > on whether the page can be allocated from the page allocator or

[PATCH 5/7] sched/isolation: Offload residual 1Hz scheduler tick

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand any interruption at all, or want to minimize them. The usual boot parameters "nohz_full=" or "isolcpus=nohz" will now

[PATCH 5/7] sched/isolation: Offload residual 1Hz scheduler tick

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand any interruption at all, or want to minimize them. The usual boot parameters "nohz_full=" or "isolcpus=nohz" will now

[PATCH 6/7] sched/nohz: Remove the 1 Hz tick code

Now that the 1Hz tick is offloaded to workqueues, we can safely remove the residual code that used to handle it locally. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter

[PATCH 6/7] sched/nohz: Remove the 1 Hz tick code

Now that the 1Hz tick is offloaded to workqueues, we can safely remove the residual code that used to handle it locally. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc:

[PATCH 4/7] sched/isolation: Isolate workqueues when "nohz_full=" is set

As we prepare for offloading the residual 1hz scheduler ticks to workqueue, let's affine those to housekeepers so that they don't interrupt the CPUs that don't want to be disturbed. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc:

[PATCH 7/7] sched/isolation: Update nohz documentation to explain tick offload

Update the documentation to reflect the 1Hz tick offload changes. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E.

[PATCH 4/7] sched/isolation: Isolate workqueues when "nohz_full=" is set

As we prepare for offloading the residual 1hz scheduler ticks to workqueue, let's affine those to housekeepers so that they don't interrupt the CPUs that don't want to be disturbed. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc:

[PATCH 7/7] sched/isolation: Update nohz documentation to explain tick offload

Update the documentation to reflect the 1Hz tick offload changes. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc: Wanpeng Li Cc: Ingo Molnar

[PATCH 2/7] nohz: Convert tick_nohz_tick_stopped() to bool

It makes this function more self-explanatory about what it does and how to use it. Reported-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino

[PATCH 0/7] isolation: 1Hz residual tick offloading v7

This version addresses comments from Thomas: * Convert tick_nohz_tick_stopped[_cpu]() to bool * Add comments to each sched_class::task_tick() to make sure that datas are always fetched from rq and task passed in parameters to allow for remote ticks. * Add reviewed-by tags

[PATCH 1/7] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc:

[PATCH 3/7] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter

[PATCH 2/7] nohz: Convert tick_nohz_tick_stopped() to bool

It makes this function more self-explanatory about what it does and how to use it. Reported-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc:

[PATCH 0/7] isolation: 1Hz residual tick offloading v7

This version addresses comments from Thomas: * Convert tick_nohz_tick_stopped[_cpu]() to bool * Add comments to each sched_class::task_tick() to make sure that datas are always fetched from rq and task passed in parameters to allow for remote ticks. * Add reviewed-by tags

[PATCH 1/7] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc:

[PATCH 3/7] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Reviewed-by: Thomas Gleixner Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra

Re: [PATCH v21 2/4] mailbox: mediatek: Add Mediatek CMDQ driver

Hi, Houlong: I've one inline comment. On Wed, 2018-01-31 at 15:28 +0800, houlong@mediatek.com wrote: > From: "hs.l...@mediatek.com" > > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > CMDQ is used to help write registers with critical time

Re: [PATCH v21 2/4] mailbox: mediatek: Add Mediatek CMDQ driver

Hi, Houlong: I've one inline comment. On Wed, 2018-01-31 at 15:28 +0800, houlong@mediatek.com wrote: > From: "hs.l...@mediatek.com" > > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > CMDQ is used to help write registers with critical time limitation, > such as

Re: [PATCH 2/3] ARM: orion: mark orion_ge00_mvmdio_bus_name as const

On Tue, Feb 20, 2018 at 05:24:51PM +0100, Arnd Bergmann wrote: > A section type mismatch warning shows up when building with LTO, > since orion_ge00_mvmdio_bus_name was put in __initconst but not marked > const itself: > > include/linux/of.h: In function 'spear_setup_of_timer': >

Re: [PATCH 2/3] ARM: orion: mark orion_ge00_mvmdio_bus_name as const

On Tue, Feb 20, 2018 at 05:24:51PM +0100, Arnd Bergmann wrote: > A section type mismatch warning shows up when building with LTO, > since orion_ge00_mvmdio_bus_name was put in __initconst but not marked > const itself: > > include/linux/of.h: In function 'spear_setup_of_timer': >

[PATCH] netlink: put module reference if dump start fails

Before, if cb->start() failed, the module reference would never be put, because cb->cb_running is intentionally false at this point. Users are generally annoyed by this because they can no longer unload modules that leak references. Also, it may be possible to tediously wrap a reference counter

[PATCH] netlink: put module reference if dump start fails

Before, if cb->start() failed, the module reference would never be put, because cb->cb_running is intentionally false at this point. Users are generally annoyed by this because they can no longer unload modules that leak references. Also, it may be possible to tediously wrap a reference counter

Re: [PATCH] cpufreq: scpi: invoke frequency-invariance setter function

On 20-02-18, 11:10, Dietmar Eggemann wrote: > Commit 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency") > changed the cpufreq driver on juno from arm_big_little to scpi. > > The scpi set_target function does not call the frequency-invariance > setter function arch_set_freq_scale()

Re: [PATCH] cpufreq: scpi: invoke frequency-invariance setter function

On 20-02-18, 11:10, Dietmar Eggemann wrote: > Commit 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency") > changed the cpufreq driver on juno from arm_big_little to scpi. > > The scpi set_target function does not call the frequency-invariance > setter function arch_set_freq_scale()

Re: [PATCH] Carrier detect ok, don't turn off negotiation

Hi, David: How  is your thinking about this patch? >From b5902a4dfc709b62b704997ab64f31c9ef69a6db Mon Sep 17 00:00:00 2001 From: Denis Du Date: Mon, 15 Jan 2018 17:26:06 -0500 Subject: [PATCH] netdev: carrier detect ok, don't turn off negotiation Sometimes when

Re: [PATCH] Carrier detect ok, don't turn off negotiation

Hi, David: How  is your thinking about this patch? >From b5902a4dfc709b62b704997ab64f31c9ef69a6db Mon Sep 17 00:00:00 2001 From: Denis Du Date: Mon, 15 Jan 2018 17:26:06 -0500 Subject: [PATCH] netdev: carrier detect ok, don't turn off negotiation Sometimes when physical lines have a just

linux-next: Tree for Feb 21

Hi all, Changes since 20180220: Non-merge commits (relative to Linus' tree): 2620 3067 files changed, 109463 insertions(+), 57328 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm

linux-next: Tree for Feb 21

Hi all, Changes since 20180220: Non-merge commits (relative to Linus' tree): 2620 3067 files changed, 109463 insertions(+), 57328 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm

Re: [PATCH 5/7] ARM: fix __inflate_kernel_data stack warning for LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > Commit ca8b5d97d6bf ("ARM: XIP kernel: store .data compressed in ROM") > moved the decompressor workspace to the stack and added a compiler > flag to avoid the stack size warning. > > With LTO, that warning comes back. Moving the workspace into an

Re: [PATCH 5/7] ARM: fix __inflate_kernel_data stack warning for LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > Commit ca8b5d97d6bf ("ARM: XIP kernel: store .data compressed in ROM") > moved the decompressor workspace to the stack and added a compiler > flag to avoid the stack size warning. > > With LTO, that warning comes back. Moving the workspace into an

Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

On Tue, Feb 20, 2018 at 07:56:35PM +1100, Michael Ellerman wrote: > Vaibhav Jain writes: > > > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > > module gets hung with

Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

On Tue, Feb 20, 2018 at 07:56:35PM +1100, Michael Ellerman wrote: > Vaibhav Jain writes: > > > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > > module gets hung with following backtrace: > > > > Call

Re: why scripts/link-vmlinux.sh has a final build of init/

Sorry for late. On 02/14/2018 07:31 PM, Masahiro Yamada wrote: > 2018-02-13 16:08 GMT+09:00 Cao jin : > >> BTW, I still have 2 questions. >> >> 1. In final build, why need >> >>GCC_PLUGINS_CFLAGS="${GCC_PLUGINS_CFLAGS}" >> >> Doesn't GCC_PLUGINS_CFLAGS already exist

Re: why scripts/link-vmlinux.sh has a final build of init/

Sorry for late. On 02/14/2018 07:31 PM, Masahiro Yamada wrote: > 2018-02-13 16:08 GMT+09:00 Cao jin : > >> BTW, I still have 2 questions. >> >> 1. In final build, why need >> >>GCC_PLUGINS_CFLAGS="${GCC_PLUGINS_CFLAGS}" >> >> Doesn't GCC_PLUGINS_CFLAGS already exist in the environment? >> >>

[PATCH V2] PCI: Add ACS quirk for Ampere root ports

The Ampere Computing PCIe root port does not support ACS at this point. However, the hardware provides isolation and source validation through the SMMU. The stream ID generated by the PCIe ports contain both the bus/device/function number as well as the port ID in its 3 most significant bits. Turn

[PATCH V2] PCI: Add ACS quirk for Ampere root ports

The Ampere Computing PCIe root port does not support ACS at this point. However, the hardware provides isolation and source validation through the SMMU. The stream ID generated by the PCIe ports contain both the bus/device/function number as well as the port ID in its 3 most significant bits. Turn

Re: [PATCH 1/3] seccomp, ptrace: switch get_metadata types to arch independent

On Tue, Feb 20, 2018 at 07:47:45PM -0700, Tycho Andersen wrote: > Commit 26500475ac1b ("ptrace, seccomp: add support for retrieving seccomp > metadata") introduced `struct seccomp_metadata`, which contained unsigned > longs that should be arch independent. The type of the flags member was > chosen

Re: [PATCH 1/3] seccomp, ptrace: switch get_metadata types to arch independent

On Tue, Feb 20, 2018 at 07:47:45PM -0700, Tycho Andersen wrote: > Commit 26500475ac1b ("ptrace, seccomp: add support for retrieving seccomp > metadata") introduced `struct seccomp_metadata`, which contained unsigned > longs that should be arch independent. The type of the flags member was > chosen

Re: [PATCH 3/7] [HACK] pass endianess flag to LTO linker

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > We need some way to pass -mbig-endian to the linker during the > LTO link stage, otherwise we get a waning like > > arm-linux-gnueabi/bin/ld: arch/arm/lib/clearbit.o: compiled for a big endian > system and target is little endian > > for each file we

Re: [PATCH 3/7] [HACK] pass endianess flag to LTO linker

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > We need some way to pass -mbig-endian to the linker during the > LTO link stage, otherwise we get a waning like > > arm-linux-gnueabi/bin/ld: arch/arm/lib/clearbit.o: compiled for a big endian > system and target is little endian > > for each file we

Re: [PATCH 2/7] ARM: LTO: avoid THUMB2_KERNEL+LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > Trying to build an LTO-Enabled kernel with Thumb2 instructions failed > horribly for me, with an endless output of things like > > ccVnNycO.s:2665: Error: thumb conditional instruction should be in IT block > -- `bxne lr' > ccVnNycO.s:7128: Error:

Re: [PATCH 2/7] ARM: LTO: avoid THUMB2_KERNEL+LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > Trying to build an LTO-Enabled kernel with Thumb2 instructions failed > horribly for me, with an endless output of things like > > ccVnNycO.s:2665: Error: thumb conditional instruction should be in IT block > -- `bxne lr' > ccVnNycO.s:7128: Error:

Re: [PATCH] random: always fill buffer in get_random_bytes_wait

Hi Ted, Can you apply this? Thanks, Jason

Re: [PATCH] random: always fill buffer in get_random_bytes_wait

Hi Ted, Can you apply this? Thanks, Jason

[PATCH v2 1/3] mm: memcg: plumbing memcg for kmem cache allocations

Introducing the memcg variant for kmem cache allocation functions. Currently the kernel switches the root kmem cache with the memcg specific kmem cache for __GFP_ACCOUNT allocations to charge those allocations to the memcg. However, the memcg to charge is extracted from the current task_struct.

[PATCH v2 1/3] mm: memcg: plumbing memcg for kmem cache allocations

Introducing the memcg variant for kmem cache allocation functions. Currently the kernel switches the root kmem cache with the memcg specific kmem cache for __GFP_ACCOUNT allocations to charge those allocations to the memcg. However, the memcg to charge is extracted from the current task_struct.

Re: [PATCH 1/7] ARM: disallow combining XIP and LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > This fails during deflate_xip_data.sh > > /home/arnd/cross-gcc/bin/arm-linux-gnueabi-objcopy -O binary -R .comment -S > vmlinux arch/arm/boot/xipImage && /bin/bash -c > '/git/arm-soc/arch/arm/boot/deflate_xip_data.sh vmlinux >

Re: [PATCH 1/7] ARM: disallow combining XIP and LTO

On Tue, 20 Feb 2018, Arnd Bergmann wrote: > This fails during deflate_xip_data.sh > > /home/arnd/cross-gcc/bin/arm-linux-gnueabi-objcopy -O binary -R .comment -S > vmlinux arch/arm/boot/xipImage && /bin/bash -c > '/git/arm-soc/arch/arm/boot/deflate_xip_data.sh vmlinux >

[PATCH v2 2/3] mm: memcg: plumbing memcg for kmalloc allocations

Introducing the memcg variant for kmalloc allocation functions. The kmalloc allocations are underlying served using the kmem caches unless the size of the allocation request is larger than KMALLOC_MAX_CACHE_SIZE, in which case, the kmem caches are bypassed and the request is routed directly to

[PATCH v2 2/3] mm: memcg: plumbing memcg for kmalloc allocations

Introducing the memcg variant for kmalloc allocation functions. The kmalloc allocations are underlying served using the kmem caches unless the size of the allocation request is larger than KMALLOC_MAX_CACHE_SIZE, in which case, the kmem caches are bypassed and the request is routed directly to

[PATCH v2 3/3] fs: fsnotify: account fsnotify metadata to kmemcg

A lot of memory can be consumed by the events generated for the huge or unlimited queues if there is either no or slow listener. This can cause system level memory pressure or OOMs. So, it's better to account the fsnotify kmem caches to the memcg of the listener. There are seven fsnotify kmem

[PATCH v2 3/3] fs: fsnotify: account fsnotify metadata to kmemcg

A lot of memory can be consumed by the events generated for the huge or unlimited queues if there is either no or slow listener. This can cause system level memory pressure or OOMs. So, it's better to account the fsnotify kmem caches to the memcg of the listener. There are seven fsnotify kmem

[PATCH v2 0/3] Directed kmem charging

This patchset introduces memcg variant memory allocation functions. The caller can explicitly pass the memcg to charge for kmem allocations. Currently the kernel, for __GFP_ACCOUNT memory allocation requests, extract the memcg of the current task to charge for the kmem allocation. This patch

[PATCH v2 0/3] Directed kmem charging

This patchset introduces memcg variant memory allocation functions. The caller can explicitly pass the memcg to charge for kmem allocations. Currently the kernel, for __GFP_ACCOUNT memory allocation requests, extract the memcg of the current task to charge for the kmem allocation. This patch

Re: [PATCH v4 2/2] ptrace, seccomp: add support for retrieving seccomp metadata

On Tue, Feb 20, 2018 at 09:13:28PM +0100, Eugene Syromiatnikov wrote: > On Tue, Nov 14, 2017 at 07:00:19PM -0700, Tycho Andersen wrote: > > With the new SECCOMP_FILTER_FLAG_LOG, we need to be able to extract these > > flags for checkpoint restore, since they describe the state of a filter. > > >

Re: [PATCH v4 2/2] ptrace, seccomp: add support for retrieving seccomp metadata

On Tue, Feb 20, 2018 at 09:13:28PM +0100, Eugene Syromiatnikov wrote: > On Tue, Nov 14, 2017 at 07:00:19PM -0700, Tycho Andersen wrote: > > With the new SECCOMP_FILTER_FLAG_LOG, we need to be able to extract these > > flags for checkpoint restore, since they describe the state of a filter. > > >

Re: [PATCH v4 2/2] ptrace, seccomp: add support for retrieving seccomp metadata

On Tue, Feb 20, 2018 at 10:30:52PM +0300, Dmitry V. Levin wrote: > > +struct seccomp_metadata { > > + unsigned long filter_off; /* Input: which filter */ > > + unsigned int flags; /* Output: filter's flags */ > > +}; > > This "unsigned long" field is unacceptable unless you

Re: [PATCH v4 2/2] ptrace, seccomp: add support for retrieving seccomp metadata

On Tue, Feb 20, 2018 at 10:30:52PM +0300, Dmitry V. Levin wrote: > > +struct seccomp_metadata { > > + unsigned long filter_off; /* Input: which filter */ > > + unsigned int flags; /* Output: filter's flags */ > > +}; > > This "unsigned long" field is unacceptable unless you

Re: [PATCH v4 0/6] Add dynamic ftrace support for RISC-V platforms

On Tue, Feb 13, 2018 at 01:13:15PM +0800, Alan Quey-Liang Kao(高魁良) wrote: > This patch set includes the building blocks of dynamic ftrace features > for RISC-V machines. > > Changes in v4: > - Organize code structure according to changes in v3 > - Rebase onto the riscv-linux-4.15 branch at

[PATCH 2/3] ptrace, seccomp: tweak get_metadata behavior slightly

Previously if users passed a small size for the input structure size, they would get get odd behavior. It doesn't make sense to pass a structure smaller than at least filter_off size, so let's just give -EINVAL in this case. This changes userspace visible behavior, but was only introduced in

Re: [PATCH v4 0/6] Add dynamic ftrace support for RISC-V platforms

On Tue, Feb 13, 2018 at 01:13:15PM +0800, Alan Quey-Liang Kao(高魁良) wrote: > This patch set includes the building blocks of dynamic ftrace features > for RISC-V machines. > > Changes in v4: > - Organize code structure according to changes in v3 > - Rebase onto the riscv-linux-4.15 branch at

[PATCH 2/3] ptrace, seccomp: tweak get_metadata behavior slightly

Previously if users passed a small size for the input structure size, they would get get odd behavior. It doesn't make sense to pass a structure smaller than at least filter_off size, so let's just give -EINVAL in this case. This changes userspace visible behavior, but was only introduced in

[PATCH 1/3] seccomp, ptrace: switch get_metadata types to arch independent

Commit 26500475ac1b ("ptrace, seccomp: add support for retrieving seccomp metadata") introduced `struct seccomp_metadata`, which contained unsigned longs that should be arch independent. The type of the flags member was chosen to match the corresponding argument to seccomp(), and so we need

[PATCH 1/3] seccomp, ptrace: switch get_metadata types to arch independent

Commit 26500475ac1b ("ptrace, seccomp: add support for retrieving seccomp metadata") introduced `struct seccomp_metadata`, which contained unsigned longs that should be arch independent. The type of the flags member was chosen to match the corresponding argument to seccomp(), and so we need

[PATCH 0/3] some fixups for PTRACE_SECCOMP_GET_METADATA

Hi Kees, Here are a couple of tweaks/fixes people suggested to the get_metadata functionality, plus a test to ensure that things work the way they're supposed to and stay that way. Cheers, Tycho Tycho Andersen (3): seccomp, ptrace: switch get_metadata types to arch independent ptrace,

[PATCH 0/3] some fixups for PTRACE_SECCOMP_GET_METADATA

Hi Kees, Here are a couple of tweaks/fixes people suggested to the get_metadata functionality, plus a test to ensure that things work the way they're supposed to and stay that way. Cheers, Tycho Tycho Andersen (3): seccomp, ptrace: switch get_metadata types to arch independent ptrace,

<    1   2   3   4   5   6   7   8   9   10   >