Hello!
On 27.05.2020 23:23, Lad Prabhakar wrote:
Enable support for HSUB, USB2.0 and xhci on iWave RZ/G1H carrier board.
HSUSB, xHCI.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
[...]
MBR, Sergei
> On May 27, 2020, at 20:15, Benjamin Tissoires
> wrote:
>
> On Wed, May 27, 2020 at 11:24 AM Benjamin Tissoires
> wrote:
>>
>> On Wed, May 27, 2020 at 8:19 AM Kai-Heng Feng
>> wrote:
>>>
>>>
>>>
On May 26, 2020, at 16:43, Benjamin Tissoires
wrote:
On Tue, May 26,
On Tue, May 12, 2020 at 02:47:09PM -0700, Tony Lindgren wrote:
> Add a binding document for a generic serdev-ngsm driver that can be
> used to bring up TS 27.010 line discipline with Linux n_gsm support
> on a serial port.
>
> As the Motorola Mapphone modems require some custom handling, they
> ar
On 5/28/20 12:55 AM, John Paul Adrian Glaubitz wrote:
> On 5/28/20 7:46 AM, Christoph Hellwig wrote:
>> [adding Linus]
>>
>> On Thu, May 07, 2020 at 07:35:52AM -0700, Christoph Hellwig wrote:
>>> Any progress on this? I plan to resend the sh dma-mapping I've been
>>> trying to get upstream for a y
On Thu 28-05-20 16:56:51, Xiao Yang wrote:
> On 2020/5/28 7:50, Ira Weiny wrote:
> > On Wed, May 27, 2020 at 01:54:54PM +0800, Xiao Yang wrote:
> > > On 2020/5/22 3:13, ira.we...@intel.com wrote:
> > > > From: Ira Weiny
> > > >
> > > > We add 'always', 'never', and 'inode' (default). '-o dax' con
On Thu, May 28, 2020 at 09:05:08AM +0100, Peter Smith wrote:
> I suggest using Arm if you need a frame pointer, and disable the
> frame pointer if you want/need to use Thumb. My understanding is that
> runtime unwinding using the frame pointer in Thumb is already difficult
> due to Arm and Thumb fu
On Thu, 2020-05-28 at 14:40 +0800, Chuhong Yuan wrote:
> [External]
>
> ad8366_probe() forgets to check the return value of devm_gpiod_get().
> Add the missed check to fix it.
>
> Fixes: cee211f4e5a0 ("iio: amplifiers: ad8366: Add support for the
> ADA4961 DGA")
> Signed-off-by: Chuhong Yuan
> -
On Wed, May 27, 2020 at 06:05:55PM +, Nicolas Viennot wrote:
> > > Also in this thread Kamil mentioned that they also need calling prctl
> > > with PR_SET_MM during restore in their production setup.
> >
> > We're using that as well but it really feels like this:
> >
> > prctl_map = (struc
On 5/28/20 11:15 AM, Holger Hoffstätte wrote:
>
> On 5/18/20 8:14 PM, Nitin Gupta wrote:
> [patch v5 :)]
>
> I've been successfully using this in my tree and it works great, but a friend
> who also uses my tree just found a bug (actually an improvement ;) due to the
> change from HUGETLB_PAGE_ORD
On Wed, May 27, 2020 at 01:28:17PM -0600, Rob Herring wrote:
> On Tue, May 12, 2020 at 02:47:10PM -0700, Tony Lindgren wrote:
> > For motorola modem case, we may have a GNSS device on channel 4.
> > Let's add that to the binding and example.
> >
> > Signed-off-by: Tony Lindgren
> > ---
> > .../d
Damian,
damian writes:
> with this patch i got the following build error:
>
> LD .tmp_vmlinux.kallsyms1
> /home/damian/kernel/buildroot/output/host/bin/x86_64-buildroot-linux-uclibc-ld:
> arch/x86/kernel/irq.o: in function `get_irq_regs':
> /home/damian/kernel/buildroot/output/build/linux
Hi,
On 28/05/20 2:28 am, kbuild test robot wrote:
> Hi Vignesh,
>
[...]
>
> In file included from include/linux/err.h:5,
> from include/linux/clk.h:12,
> from drivers/spi/spi-cadence-quadspi.c:9:
> include/linux/scatterlist.h: In function 'sg_set_buf':
> arch/xtensa/include/asm/page.h:193:9: war
On NOMMU kernels without CONFIG_MEMCG_KMEM, we now get a harmless
warning about an unused function:
mm/memcontrol.c:2595:13: error: unused function 'cancel_charge'
[-Werror,-Wunused-function]
Hide this function in a matching #ifdef.
Fixes: 5bd144bf764c ("mm: memcontrol: drop unused try/commit/c
Guys, the patch is wrong. The kfree is harmless when this is called
from destroy_workqueue() and required when it's called from
pwq_unbound_release_workfn(). Lai Jiangshan already explained this
already. Why are we still discussing this?
regards,
dan carpenter
This patch fixes mediatek-cqdma compatible to common.
Signed-off-by: EastL
---
drivers/dma/mediatek/mtk-cqdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/mediatek/mtk-cqdma.c b/drivers/dma/mediatek/mtk-cqdma.c
index 905bbcb..bca7118 100644
--- a/drivers/dma/
Document the devicetree bindings for MediaTek Command-Queue DMA controller
which could be found on MT6779 SoC or other similar Mediatek SoCs.
Signed-off-by: EastL
---
.../devicetree/bindings/dma/mtk-cqdma.yaml | 100 +
1 file changed, 100 insertions(+)
create mode 10
This patch set adds document the devicetree bindings for MediaTek Command-Queue
DMA controller,
and remove redundant queue structure, add dma-channel-mask for DMA capability
and fix compatible.
Changes since v3:
- fix dt_binding_check errors
Changes since v2:
- add devicetree bindings for Media
On Thu, May 28, 2020 at 06:04:48AM +0200, Jann Horn wrote:
> On Wed, May 27, 2020 at 1:19 PM Christian Brauner
> wrote:
> > We've been making heavy use of the seccomp notifier to intercept and
> > handle certain syscalls for containers. This patch allows a syscall
> > supervisor listening on a giv
This patch add dma mask for capability.
Change-Id: I31f4622f9541d769702029532e5f5f185815dda2
Signed-off-by: EastL
---
drivers/dma/mediatek/mtk-cqdma.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/dma/mediatek/mtk-cqdma.c b/drivers/dma/mediatek/mtk-cqdma.c
index bca7
On Thu, May 28, 2020 at 11:39:23AM +0300, Serge Semin wrote:
> On Wed, May 27, 2020 at 08:56:24PM +0300, Andy Shevchenko wrote:
> > On Wed, May 27, 2020 at 08:18:41PM +0300, Serge Semin wrote:
> > > On Wed, May 27, 2020 at 11:12:04AM -0600, Rob Herring wrote:
> > > > On Wed, May 27, 2020 at 03:01:0
On 2020-05-28 11:08, Petr Tesarik wrote:
Hi all,
just a gentle ping.
If the current behaviour (logging the original handle) was intended,
then it was worth mentioning in the commit message for 17cdec960cf77,
which made the change, but since that's no longer an option, I'd be
happy with an exp
The following commit has been merged into the locking/kcsan branch of tip:
Commit-ID: f05e1242fbb2d149ceaa87310cf67d03fe007a25
Gitweb:
https://git.kernel.org/tip/f05e1242fbb2d149ceaa87310cf67d03fe007a25
Author:Marco Elver
AuthorDate:Thu, 28 May 2020 09:43:13 +02:00
Committ
On Wed, May 27, 2020 at 7:36 AM Rob Herring wrote:
>
> On Mon, May 18, 2020 at 09:49:30AM +0900, Steve Lee wrote:
> > Add documentation for DT binding of max98390 amplifier driver.
> >
> > Signed-off-by: Steve Lee
> > ---
> >
> >
> > Changed since V4:
> > * No changes.
> > Changed since V3:
On Wed, May 27, 2020 at 09:51:00PM +0100, Pascal Terjan wrote:
> This driver contains a local version of the rfc1042 header and bridge
> tunnel header constants which are available from cfg80211.h, switch to
> those.
>
> Signed-off-by: Pascal Terjan
> ---
> v2: improve description and drop confus
On Thu, May 28, 2020 at 12:33:18PM +0300, Serge Semin wrote:
> Seeing the DW I2C driver is using flags-based accessors with two
> conditional clauses it would be better to replace them with the regmap
> API IO methods and to initialize the regmap object with read/write
> callbacks specific to the c
On Thu, May 28, 2020 at 12:01:45PM +0200, Pierre Morel wrote:
>
> On 2020-05-28 11:08, Petr Tesarik wrote:
> > Hi all,
> >
> > just a gentle ping.
> >
> > If the current behaviour (logging the original handle) was intended,
> > then it was worth mentioning in the commit message for 17cdec960cf77
On 2020/5/26 下午1:32, Zhu Lingshan wrote:
Standard vhost devices rely on waking up a vhost_worker to kick
a virtquque. However vdpa devices have hardware backends, so it
does not need this waking up routin. In this commit, vdpa device
will kick a virtqueue directly, reduce the performance overhe
On Thu, May 28, 2020 at 12:33:17PM +0300, Serge Semin wrote:
> A PM workaround activated by the flag MODEL_CHERRYTRAIL has been removed
> since commit 9cbeeca05049 ("i2c: designware: Remove Cherry Trail PMIC I2C
> bus pm_disabled workaround"), but the flag most likely by mistake has been
> left in
Hi,
On 27/05/20 4:28 am, Serge Semin wrote:
> Baikal-T1 Boot Controller provides an access to a RO storages, which are
> physically mapped into the MMIO space. In particularly there are the
> Internal ROM embedded into the SoC with a pre-installed firmware,
> externally attached SPI flash (also ac
On Thu, May 28, 2020 at 10:46:56AM +0200, Michael Walle wrote:
> Am 2020-05-28 10:37, schrieb Andy Shevchenko:
> > On Thu, May 28, 2020 at 7:11 AM Michael Walle wrote:
> > > Am 2020-05-28 02:31, schrieb Pierre-Louis Bossart:
> >
> >
> > > I've send a v5 with that fix and your names property.
> >
I'll repost the patch, based on the dir-cache patched dev-tree.
If dir-cache patch will merge into dev-tree, should I wait until then?
I will apply them after testing at once if you send updated 5 patches again.
I resend patches for boot_sector.
However, the dir-cache patch hasn't changed, so I
Hi all,
This should have been the block tree, not the fsinfo tree, of course.
On Thu, 28 May 2020 18:40:17 +1000 Stephen Rothwell
wrote:
>
> After merging the fsinfo tree, today's linux-next build (x86_64
> allnoconfig) produced these warnings:
>
> In file included from kernel/sched/sched.h:39
On Thu, May 28, 2020 at 11:08:18AM +0300, Maxim Uvarov wrote:
> On Wed, 27 May 2020 at 22:42, Jarkko Sakkinen
> wrote:
> >
> > On Mon, 2020-05-25 at 09:50 +0300, Maxim Uvarov wrote:
> > > Jakko,
> > > tee-supplicant application provides state machine over callbacks with
> > > RPC messages.
> > > h
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 4bcffde74b6a2ba992a0617bb6b9be054e7f89a2
Gitweb:
https://git.kernel.org/tip/4bcffde74b6a2ba992a0617bb6b9be054e7f89a2
Author:Wei Liu
AuthorDate:Wed, 27 May 2020 12:09:18
Committer: Thomas
The ghes driver reports errors with 'unknown label' even if the actual
DIMM label is known, e.g.:
EDAC MC0: 1 CE Single-bit ECC on unknown label (node:0 card:0
module:0 rank:1 bank:0 col:13 bit_pos:16 DIMM location:N0 DIMM_A0
page:0x966a9b3 offset:0x0 grain:1 syndrome:0x0 - APEI location:
On Mon, 25 May 2020 at 09:15, Ulf Hansson wrote:
>
> On Fri, 22 May 2020 at 16:45, Pali Rohár wrote:
> >
> > Most SDIO IDs are defined in the common include file linux/mmc/sdio_ids.h.
> > But some drivers define IDs locally or do not use existing macros from the
> > common include file.
> >
> > T
On Mon, 25 May 2020 at 09:41, Vladimir Kondratiev
wrote:
>
> Accordingly to Cadence documentation, PHY write procedure is:
>
> 1. Software sets the PHY Register Address (HRS04[5:0]) and the
>PHY Write Data (HRS04[15:8]) fields.
> 2. Software sets the PHY Write Transaction Request (HRS04[24]) f
On Wed, 27 May 2020 at 13:09, Pali Rohár wrote:
>
> Device/vendor ids from Common CIS (Card Information Structure) may be
> different as device/vendor ids from CIS on particular SDIO function.
>
> Kernel currently exports only device/vendor ids from SDIO functions and not
> "main" device/vendor id
On Tue, 26 May 2020 at 17:51, Ludovic Barre wrote:
>
> Turning on CONFIG_DMA_API_DEBUG_SG results in the following warning:
> WARNING: CPU: 1 PID: 85 at kernel/dma/debug.c:1302
> debug_dma_map_sg+0x2a0/0x3cc
> mmci-pl18x 58005000.sdmmc: DMA-API: mapping sg segment longer than device
> claims to
On Tue, 26 May 2020 at 17:51, Ludovic Barre wrote:
>
> Turning on CONFIG_DMA_API_DEBUG_SG results in the following warning:
> WARNING: CPU: 1 PID: 20 at kernel/dma/debug.c:500 add_dma_entry+0x16c/0x17c
> DMA-API: exceeded 7 overlapping mappings of cacheline 0x031d2645
> Modules linked in:
> CPU: 1
On Wed, 27 May 2020 at 13:09, Pali Rohár wrote:
>
> SDIO non-combo cards are not handled by mmc_block driver and do not have
> accessible CID register which is used for MMC_NAME= construction.
>
> Signed-off-by: Pali Rohár
> Reviewed-by: Marek Behún
Applied for next, thanks!
Kind regards
Uffe
On Wed, 27 May 2020 at 12:57, Eugen Hristev wrote:
>
> When enabling calibration at reset, the CALCR register was completely
> rewritten. This may cause certain bits being deleted unintentedly.
> Fix by issuing a read-modify-write operation.
>
> Fixes: 727d836a375a ("mmc: sdhci-of-at91: add DT pro
Mapping of early shadow area is implemented by using a single static
page table having all entries pointing to the same early shadow page.
The shadow area must therefore occupy full PGD entries.
The shadow area has a size of 128Mbytes starting at 0xf800.
With 4k pages, a PGD entry is 4Mbytes
W
On Thu, 28 May 2020 at 11:24, Marek Szyprowski wrote:
>
> Hi Ulf,
>
> On 28.05.2020 11:14, Ulf Hansson wrote:
> > On Wed, 27 May 2020 at 10:23, Tomi Valkeinen wrote:
> >> Commit 9495b7e92f716ab2bd6814fab5e97ab4a39adfdd ("driver core: platform:
> >> Initialize dma_parms for platform devices") in v
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function
'kfd_sdma_activity_worker':
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:117:2: error: implicit
declaration of function 'us
sta32x_probe() forgets to call undo functions when it fails, add
the missed function calls to fix it.
Signed-off-by: Chuhong Yuan
---
sound/soc/codecs/sta32x.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/sound/soc/codecs/sta32x.c b/sound/soc/codecs/sta32x.c
in
btmtuart_probe() misses several function calls in its error paths,
including hci_free_dev() and clk_disable_unprepare().
Refactor the code and call correct undo functions to fix the error
paths.
Signed-off-by: Chuhong Yuan
---
drivers/bluetooth/btmtkuart.c | 14 --
1 file changed, 8
st21nfca_tm_send_atr_res() misses to call kfree_skb() in an error path.
Add the missed function call to fix it.
Fixes: 1892bf844ea0 ("NFC: st21nfca: Adding P2P support to st21nfca in
Initiator & Target mode")
Signed-off-by: Chuhong Yuan
---
drivers/nfc/st21nfca/dep.c | 4 +++-
1 file changed, 3
On Thu, May 28, 2020 at 5:17 PM Markus Elfring wrote:
>
> > rv3028_probe() misses a check for devm_regmap_init_i2c().
>
> Such information is helpful.
>
>
> > Add the missed check
>
> Thanks for another completion of the exception handling.
>
>
> > to fix it.
>
> I suggest to
sbp_fetch_command() forgets to call kfree() in an error path.
Add the missed call to fix it.
Fixes: a511ce339780 ("sbp-target: Initial merge of firewire/ieee-1394 target
mode support")
Signed-off-by: Chuhong Yuan
---
drivers/target/sbp/sbp_target.c | 4 +++-
1 file changed, 3 insertions(+), 1 d
Dear Friend.
My name is Jillrita Mike Riddering, I am sending this brief letter
to solicit your support and partnership to transfer $5.5 million US
Dollars. This money belongs to my late father Mike Riddering,my father
and my mother were among those that were killed on 2016 terrorist
attack at
From: Anson Huang Sent: Thursday, May 28, 2020 11:13 AM
> In the nvmem yaml schema, it requires the nodename to be one of
> "eeprom|efuse|nvram", so need to change all i.MX/MXS SoCs ocotp/iim node
> name to efuse:
>
> MXS platforms: i.MX23/28;
> i.MX platforms with IIM: i.MX25/27/31/35/51/53.
> i
On Wed, May 27, 2020 at 3:27 PM Rob Herring wrote:
>
> On Wed, May 27, 2020 at 5:26 AM Anders Roxell
> wrote:
> >
> > Make sure that the POWER_RESET_VEXPRESS driver won't have bind/unbind
> > attributes available via the sysfs, so lets be explicit here and use
> > ".suppress_bind_attrs = true" t
On Thursday 21 May 2020 14:34:44 Pali Rohár wrote:
> During initialization of SD8997 wifi chip kernel prints warnings:
>
> mwifiex_sdio mmc0:0001:1: Unknown api_id: 3
> mwifiex_sdio mmc0:0001:1: Unknown api_id: 4
>
> This patch adds support for parsing all api ids provided by SD8997
> firmwar
Don,
Don Porter writes:
> On 5/22/20 8:45 PM, Thomas Gleixner wrote:
> The threat model for Graphene, and most SGX papers, is quite explicit:
> we assume that Intel’s CPU package, the software in the enclave, and
> possibly Intel’s Attestation Service (IAS) are the only trusted
> components.
On Wed, May 27, 2020 at 3:32 PM Rob Herring wrote:
>
> On Wed, May 27, 2020 at 5:26 AM Anders Roxell
> wrote:
> >
> > Today the vexpress power driver can only be builtin. Rework so it's
> > possible for the vexpress power driver to be a module.
>
> This is the same incomplete patch I did[1]. As
Hi,
On 21/05/20 10:56 am, Rayagonda Kokatanur wrote:
> Both w25q64 and s25fl064k nor flash support QUAD and DUAL read
> command, hence update the same in flash_info table.
>
I am guessing both modes were tested on some platform?
Could you add that info here?
> Signed-off-by: Rayagonda Kokatanur
On Saturday 16 May 2020 08:17:17 Ganapathi Bhat wrote:
> Hi Pali,
>
> Thanks for this notice. We will try to push the new firmware and also, fix
> the naming problem.
>
> Regards,
> Ganapathi
Hello Ganapathi!
According to publicly available information, firmware for these W8xxx
Marvell wifi ch
On Wed, May 27, 2020 at 3:35 PM Rob Herring wrote:
>
> On Wed, May 27, 2020 at 5:26 AM Anders Roxell
> wrote:
> >
> > Hi,
> >
> > This patchset contains a bugfixe, a cleanup and fixes allmodconfig build
> > breakages
> > on arm and arm64. Also making the vexpress power reset driver a module.
>
Hi Ben,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: b0c3ba31be3e45a130e13b278cf3b90f69bda6f6
commit: a2bfb50e72aeb139801109e3b4eb73ac53bde314 drm/nouveau/gr/gk20a,gm200-:
use nvkm_firmware_load_blob for sw init
Andi,
Andi Kleen writes:
>> Setting the fs register in userspace is an essential feature for running
>> legacy code in SGX. We have been following LKML discussions on this
>> instruction for years, and hoping this feature would be supported by Linux,
>
> If you need a feature you should comment
On Thu, May 28, 2020 at 12:57:03PM +0300, Dan Carpenter wrote:
> Guys, the patch is wrong. The kfree is harmless when this is called
> from destroy_workqueue() and required when it's called from
> pwq_unbound_release_workfn(). Lai Jiangshan already explained this
> already. Why are we still disc
@dev parameter of qca_suspend()/qca_resume() represents
serdev_device, but it is mistook for hci_dev and causes
succedent unexpected memory access.
Fix by taking @dev as serdev_device.
Signed-off-by: Zijun Hu
---
drivers/bluetooth/hci_qca.c | 12
1 file changed, 8 insertions(+), 4
Add DT binding of max98390 amplifier driver.
Signed-off-by: Steve Lee
---
Changed since V5:
* Change txt to yaml and fix up the examples.
Changed since V4:
* No changes.
Changed since V3:
* No changes.
Changed since V2:
* No changes.
Changed since V1:
* Mod
rv3028_probe() misses a check for devm_regmap_init_i2c().
Add the missed check to fix it.
Fixes: e6e7376cfd7b ("rtc: rv3028: add new driver")
Signed-off-by: Chuhong Yuan
---
Changes in v2:
- Add fixes tag.
drivers/rtc/rtc-rv3028.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/
-s032-20200528 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-240-gf0fe1cd9-dirty
git checkout bbb1658461ac85ef7e0563bb11283f94ea5eb651
# save the attached .config to linux build tree
make W
This is the initial amplifier driver for max98390.
Reported-by: kbuild test robot
Signed-off-by: Steve Lee
---
Changes since V5:
* Fixed warning message reported by kbuild.
* Finalize default register value.
* Update missed AMP_EN register setting during dsm_init.
On Thu, May 28, 2020 at 03:36:55PM +0530, Vignesh Raghavendra wrote:
> Hi,
>
> On 27/05/20 4:28 am, Serge Semin wrote:
> > Baikal-T1 Boot Controller provides an access to a RO storages, which are
> > physically mapped into the MMIO space. In particularly there are the
> > Internal ROM embedded int
system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Ronak-Doshi/vmxnet3-upgrade-to-version-4/20200528-112935
base: https://git.kernel.org/pub
+Mika Westerberg original author of the driver
On 18/05/20 11:29 pm, Daniel Walker wrote:
> From: Bobby Liu
>
> How to use:
> append softwareseq=1 while probe the driver.
> example:
> modprobe intel-spi writeable=1 softwareseq=1
> it will let driver use software sequence to write register for op
Hi Hans,
Thanks for the review.
On 2020-05-26 16:27, Hans Verkuil wrote:
Hi Dikshita,
My apologies for the delay, this was (mostly) due to various vacation
days.
On 08/05/2020 08:21, Dikshita Agarwal wrote:
There are many commercialized video use cases which needs metadata
info
to be circ
On 28/05/20 08:14, Gavin Shan wrote:
>> - for x86 we're also thinking of initiating the page fault from the
>> exception handler, rather than doing so from the hypervisor before
>> injecting the exception. If ARM leads the way here, we would do our
>> best to share code when x86 does the same.
>
On Thu, May 28, 2020 at 04:22:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
>
> between commit:
>
> 3828026c9ec8 ("dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings"
Hi all,
Changes since 20200526:
My fixes tree contains:
cd2b06ec45d6 ("device_cgroup: Fix RCU list debugging warning")
The arm tree gained a conflict against Linus' tree.
The drm-msm tree still had its build failure so I applied a patch.
The rcu tree gained a build failure for which I appli
On 28/05/20 09:03, Marc Zyngier wrote:
> The current state of the architecture doesn't seem to leave much leeway in
> terms of SW creativity here. You just can't allocate your own ISS encoding
> without risking a clash with future revisions of the architecture.
> It isn't even clear whether the val
On Thu, May 28, 2020 at 12:25 AM Guenter Roeck wrote:
>
> On Wed, May 27, 2020 at 11:01:16AM +0200, Rafael J. Wysocki wrote:
> >
> > So Guenter, can you please test the patch below to see if it still
> > introduces
> > the problems seen by you on ARM?
> >
>
> arm64 and arm64be boot tests pass wit
On Thu 2020-05-28 08:33:37, Tetsuo Handa wrote:
> On 2020/05/28 0:55, Petr Mladek wrote:
> >>> Well, it would be possible to call vsprintf() with NULL buffer. It is
> >>> normally used to calculate the length of the message before it is
> >>> printed. But it also does all the accesses without print
On 28/05/20 10:42, Vitaly Kuznetsov wrote:
> How does it work with the patchset: 'page not present' case remains the
> same. 'page ready' case now goes through interrupts so it may not get
> handled immediately. External interrupts will be handled by L0 in host
> mode (when L2 is not running). For
>> Guys, the patch is wrong. The kfree is harmless when this is called
>> from destroy_workqueue() and required when it's called from
>> pwq_unbound_release_workfn(). Lai Jiangshan already explained this
>> already. Why are we still discussing this?
>
> Oops, missed that. Reverting.
Can it matt
As func comments mentioned, few isolated page missing be tolerated.
So why not do further to drop the unlikely double check. That won't
cause more idle pages, but reduce a lock contention.
This is also a preparation for later new page isolation feature.
Signed-off-by: Alex Shi
Cc: Andrew Morton
The compact_deferred is a defer suggestion check, deferring action does in
defer_compaction not here. so, better rename it to avoid confusing.
Signed-off-by: Alex Shi
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Andrew Morton
Cc: Vlastimil Babka
Cc: Mike Kravetz
Cc: linux-kernel@vger.kernel.org
Cc
Combine PageLRU check and ClearPageLRU into a function by new
introduced func TestClearPageLRU. This function will be used as page
isolation precondition to prevent other isolations some where else.
Then there are may non PageLRU page on lru list, need to remove BUG
checking accordingly.
As Andre
We don't have to add a freeable page into lru and then remove from it.
This change saves a couple of actions and makes the moving more clear.
The SetPageLRU needs to be kept here for list intergrity.
Otherwise:
#0 mave_pages_to_lru #1 release_pages
There is no compact_defer_limit. It should be compact_defer_shift in
use. and add compact_order_failed explanation.
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
include/linux/mmzone.h | 1 +
mm/compaction.c| 2 +-
2 files changed,
This patch reorder the isolation steps during munlock, move the lru lock
to guard each pages, unfold __munlock_isolate_lru_page func, to do the
preparation for lru lock change.
__split_huge_page_refcount doesn't exist, but we still have to guard
PageMlocked and PageLRU in __split_huge_page_tail.
On 18/05/20 11:29 pm, Daniel Walker wrote:
> This option currently doesn't work as expected. If the BIOS has this
> flash as read-only there is no way to change this thru the driver.
> There is a parameter which allows the flash to become writable with the
> "writable" option to the module, but
Johannes Weiner has suggested:
"So here is a crazy idea that may be worth exploring:
Right now, pgdat->lru_lock protects both PageLRU *and* the lruvec's
linked list.
Can we make PageLRU atomic and use it to stabilize the lru_lock
instead, and then use the lru_lock only serialize list operations?
From: Hugh Dickins
Use the relock function to replace relocking action. And try to save few
lock times.
Signed-off-by: Hugh Dickins
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Tejun Heo
Cc: Andrey Ryabinin
Cc: Jann Horn
Cc: Mel Gorman
Cc: Johannes Weiner
Cc: Matthew Wilcox
Cc: Hugh Di
From: Hugh Dickins
Since we changed the pgdat->lru_lock to lruvec->lru_lock, it's time to
fix the incorrect comments in code. Also fixed some zone->lru_lock comment
error from ancient time. etc.
Signed-off-by: Hugh Dickins
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Tejun Heo
Cc: Andrey Ry
Use this new function to replace repeated same code.
Signed-off-by: Alex Shi
Cc: Johannes Weiner
Cc: Andrew Morton
Cc: Thomas Gleixner
Cc: Andrey Ryabinin
Cc: Matthew Wilcox
Cc: Mel Gorman
Cc: Konstantin Khlebnikov
Cc: Hugh Dickins
Cc: Tejun Heo
Cc: linux-kernel@vger.kernel.org
Cc: cgro.
The func is only used in huge_memory.c, defining it in other file with a
CONFIG_TRANSPARENT_HUGEPAGE macro restrict just looks weird.
Let's move it THP.
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Johannes Weiner
Cc: Matthew Wilcox
Cc: Hugh Dickins
Cc: linux-kernel@vger.kernel.org
Cc: linu
Now pgdat.lru_lock was replaced by lruvec lock. It's not used anymore.
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Konstantin Khlebnikov
Cc: Hugh Dickins
Cc: Johannes Weiner
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
Cc: cgro...@vger.kernel.org
---
include/linux/mmzone.h | 1 -
This is a new version which bases on linux-next
Johannes Weiner has suggested:
"So here is a crazy idea that may be worth exploring:
Right now, pgdat->lru_lock protects both PageLRU *and* the lruvec's
linked list.
Can we make PageLRU atomic and use it to stabilize the lru_lock
instead, and then
This patch moves per node lru_lock into lruvec, thus bring a lru_lock for
each of memcg per node. So on a large machine, each of memcg don't
have to suffer from per node pgdat->lru_lock competition. They could go
fast with their self lru_lock.
After move memcg charge before lru inserting, page iso
Add a debug checking in lock_page_memcg, then we could get alarm
if anything wrong here.
Suggested-by: Johannes Weiner
Signed-off-by: Alex Shi
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Vladimir Davydov
Cc: Andrew Morton
Cc: cgro...@vger.kernel.org
Cc: linux...@kvack.org
Cc: linux-kernel@vger.
On Thu, May 21, 2020 at 03:21:25PM +0800, Wei Li wrote:
> Currently, 'KDBFLAGS' is an internal variable of kdb, it is combined
> by 'KDBDEBUG' and state flags. It will be shown only when 'KDBDEBUG'
> is set, and the user can define an environment variable named 'KDBFLAGS'
> too. These are puzzling
Since the first parameter is only used by head page, it's better to make
it stright.
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Johannes Weiner
Cc: Matthew Wilcox
Cc: Hugh Dickins
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/huge_memory.c | 12 ++--
1 file change
lru_lock and page cache xa_lock have no reason with current sequence,
put them together isn't necessary. let's narrow the lru locking, but
left the local_irq_disable/preempt_disable to block interrupt
re-entry and statistic update.
Signed-off-by: Alex Shi
Signed-off-by: Wei Yang
Cc: Kirill A. Sh
On 5/27/2020 9:08 PM, Rob Clark wrote:
On Wed, May 27, 2020 at 1:47 AM Sharat Masetty wrote:
+ more folks
On 5/18/2020 9:55 PM, Rob Clark wrote:
On Mon, May 18, 2020 at 7:23 AM Jordan Crouse wrote:
On Thu, May 14, 2020 at 04:24:18PM +0530, Sharat Masetty wrote:
This patches replaces the
Except for [PATCH v4 36/36], which I can't approve for obvious reasons:
Reviewed-by: William Kucharski
201 - 300 of 1820 matches
Mail list logo
