Re: Potentially missing "memory" clobbers in bitops.h for x86

On Fri, Mar 29, 2019 at 02:51:26PM -0700, H. Peter Anvin wrote: > On 3/29/19 2:09 PM, Paul E. McKenney wrote: > >> > >> Note: the atomic versions of these functions obviously need to have > >> "volatile" and the clobber anyway, as they are by definition barriers > >> and moving memory operations

Re: [PATCH v5 13/25] m68k: add asm/syscall.h

On Wed, Dec 12, 2018 at 11:55:16AM +0300, Dmitry V. Levin wrote: > On Mon, Dec 10, 2018 at 04:30:25PM +0300, Dmitry V. Levin wrote: > > On Mon, Dec 10, 2018 at 02:06:28PM +0100, Geert Uytterhoeven wrote: > > > On Mon, Dec 10, 2018 at 1:41 PM Dmitry V. Levin wrote: > > > > On Mon, Dec 10, 2018 at

[PATCH] clk: rockchip: Fix video codec clocks on rk3288

It appears that there is a typo in the rk3288 TRM. For GRF_SOC_CON0[7] it says that 0 means "vepu" and 1 means "vdpu". It's the other way around. How do I know? Here's my evidence: 1. Prior to commit 4d3e84f99628 ("clk: rockchip: describe aclk_vcodec using the new muxgrf type on rk3288")

Re: [PATCH] jbd2: do not start commit when t_updates does not back to zero

On Mar 29, 2019, at 3:25 PM, Jan Kara wrote: > > On Sun 24-03-19 11:38:35, Liu Song wrote: >> When t_updates back to zero, it guaranteed wake up process which >> waiting on j_wait_updates. If we triggered a commit start without >> considered t_updates, the commit thread wakes up and find

Re: Potentially missing "memory" clobbers in bitops.h for x86

On 3/29/19 2:09 PM, Paul E. McKenney wrote: >> >> Note: the atomic versions of these functions obviously need to have >> "volatile" and the clobber anyway, as they are by definition barriers >> and moving memory operations around them would be a very serious error. > > The atomic functions that

Re: [GIT PULL] Kbuild fixes for v5.1-rc3

The pull request you sent on Fri, 29 Mar 2019 23:12:30 +0900: > git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git > tags/kbuild-fixes-v5.1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/0e40da3efeb02ab0333d01abae20d421841db30a Thank you! --

Re: [GIT PULL] xfs: bug fixes for 5.1-rc3

The pull request you sent on Fri, 29 Mar 2019 06:33:11 -0700: > git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.1-fixes-1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/c6503f12d135a616b25be99a492765fc9e9fe07e Thank you! -- Deet-doot-dot, I am a bot.

[PATCH 2/3] ASoC: Intel: bytcht_es8316: Add quirk for inverted jack detect

Add a quirk to support boards whose jack detection mechanism is inverted. It will set the 'everest,jack-detect-inverted' boolean device property for the es8316 codec driver. Signed-off-by: Paul Cercueil --- sound/soc/intel/boards/bytcht_es8316.c | 17 + 1 file changed, 17

[PATCH 3/3] ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II

The Teclast X98+ II is a Cherrytrail tablet, which require two quirks: - it has stereo speakers, - its jack detection mechanism is inverted. Signed-off-by: Paul Cercueil --- sound/soc/intel/boards/bytcht_es8316.c | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff

[PATCH 1/3] ASoC: es8316: Add support for inverted jack detect

On some devices (Teclast X98+ II tablet, maybe others), the jack detection has been wired backwards, so when the ES8316 reports headphones being present it means they are actually not plugged. Use a quirk around this incorrect behaviour, which can be enabled through the

Re: [PATCH 01/13] soc/fsl/qman: fixup liodns only on ppc targets

On Fri, Mar 29, 2019 at 9:01 AM wrote: > > From: Laurentiu Tudor > > ARM SoCs use SMMU so the liodn fixup done in the qman driver is no > longer making sense and it also breaks the ICID settings inherited > from u-boot. Do the fixups only for PPC targets. > > Signed-off-by: Laurentiu Tudor >

Re: [GIT PULL] Ceph fixes for 5.1-rc3

The pull request you sent on Fri, 29 Mar 2019 17:32:13 +0100: > https://github.com/ceph/ceph-client.git tags/ceph-for-5.1-rc3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/7376e39ad96583545faefa2e7798bcb6a2a212a7 Thank you! -- Deet-doot-dot, I am a bot.

Re: general protection fault in load_elf_binary

: 1baf02ec Add linux-next specific files for 20190329 git tree: linux-next final crash:https://syzkaller.appspot.com/x/report.txt?x=13d5c23f20 console output: https://syzkaller.appspot.com/x/log.txt?x=15d5c23f20 kernel config: https://syzkaller.appspot.com/x/.config?x=9d8e70f94f3533a7

[PATCH v3 3/4] x86/fpu: Fix __user annotations

In save_xstate_epilog(), use __user when type-casting userspace pointers. In setup_sigcontext() and x32_setup_rt_frame(), cast the userspace pointers to 'unsigned long __user *' before writing into them. These pointers are originally '__u32 __user *' or '__u64 __user *', causing sparse to

[PATCH v3 1/4] kernel.h: use parentheses around argument in u64_to_user_ptr()

Use parentheses around uses of the argument in u64_to_user_ptr() to ensure that the cast doesn't apply to part of the argument. There are existing uses of the macro of the form `u64_to_user_ptr(A + B)`, which expands to `(void __user *)(uintptr_t)A + B` (the cast applies to the first operand of

[PATCH v3 4/4] x86/uaccess: Fix implicit cast of __user pointer

The first two arguments of __user_atomic_cmpxchg_inatomic() are: - `uval` is a kernel pointer into which the old value should be stored - `ptr` is the user pointer on which the cmpxchg should operate This means that casting `uval` to `__typeof__(ptr)` is wrong. Since `uval` is only used once

[PATCH v3 2/4] x86/microcode: Fix __user annotations around generic_load_microcode()

generic_load_microcode() deals with a pointer that can be either a kernel pointer or a user pointer. Pass it around as a __user pointer so that it can't be dereferenced accidentally while its address space is unknown. Use explicit casts to convert between __user and __kernel to inform the checker

[PATCH] x86/resctrl: Fix typos in mba_sc mount option

With mount option "mba_MBps", we could enable MBA Software Controller (mba_sc) to specify MBA memory bandwidth in unit MBps (Mega Bytes per second). See details in Documentation/x86/resctrl_ui.txt. Commit 23bf1b6be9c2 ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") changes the mount

Re: [PATCH v2 01/11] mm/hmm: select mmu notifier when selecting HMM

On 3/29/19 2:15 PM, Jerome Glisse wrote: [...] >> Yes, this is a good move, given that MMU notifiers are completely, >> indispensably part of the HMM design and implementation. >> >> The alternative would also work, but it's not quite as good. I'm >> listing it in order to forestall any debate:

Fixing the GHES driver vs not causing issues in the first place

The issue of dying inside the GHES driver has popped up a few times before. I've looked into fixing this before, but we didn't quite come to agreement because the verbiage in the ACPI spec is vague:     " When a fatal uncorrected error occurs, the system is       restarted to prevent propagation

Re: [PATCH] rcu: tree_stall: Correctly unlock root node in rcu_check_gp_start_stall

On Fri, Mar 29, 2019 at 07:52:15PM +0530, Neeraj Upadhyay wrote: > > > On 3/29/19 6:58 PM, Mukesh Ojha wrote: > > > >On 3/29/2019 4:57 PM, Neeraj Upadhyay wrote: > >>Only unlock the root node, if current node (rnp) is not > >>root node. > >> > >>Signed-off-by: Neeraj Upadhyay > > > > > > >

Re: [PATCH] rcu: tree_plugin: Dump specified number of blocked tasks

On Fri, Mar 29, 2019 at 03:42:44PM +0530, Mukesh Ojha wrote: > > On 3/29/2019 3:25 PM, Neeraj Upadhyay wrote: > >dump_blkd_tasks() uses 10 as the max number of blocked > >tasks, which are printed. However, it has an argument > >which provides that number. So, use the argument value > >instead. As

Re: [PATCH] jbd2: do not start commit when t_updates does not back to zero

On Sun 24-03-19 11:38:35, Liu Song wrote: > When t_updates back to zero, it guaranteed wake up process which > waiting on j_wait_updates. If we triggered a commit start without > considered t_updates, the commit thread wakes up and find t_updates > is not zero, it have to wait on it once again.

Re: [PATCH] staging: rtl8723bs: core: fix line over 80 characters warning

On 3/26/2019 11:55 PM, Anirudh Rayabharam wrote: Shorten the expression by re-using the part that was already computed to fix the line over 80 characters warning reported by checkpatch.pl. Signed-off-by: Anirudh Rayabharam --- drivers/staging/rtl8723bs/core/rtw_ap.c | 4 ++-- 1 file

Re: [PATCH v2 01/11] mm/hmm: select mmu notifier when selecting HMM

On Thu, Mar 28, 2019 at 01:33:42PM -0700, John Hubbard wrote: > On 3/25/19 7:40 AM, jgli...@redhat.com wrote: > > From: Jérôme Glisse > > > > To avoid random config build issue, select mmu notifier when HMM is > > selected. In any cases when HMM get selected it will be by users that > > will

Re: [PATCHv8 07/10] acpi/hmat: Register processor domain to its memory

On Mon, Mar 11, 2019 at 1:55 PM Keith Busch wrote: > > If the HMAT Subsystem Address Range provides a valid processor proximity > domain for a memory domain, or a processor domain matches the performance > access of the valid processor proximity domain, register the memory > target with that

[GIT PULL][UPDATED] security: yama and LSM config fixes

Please pull these fixes for v5.1. The following changes since commit 8c7ae38d1ce12a0eaeba655df8562552b3596c7f: afs: Fix StoreData op marshalling (2019-03-28 08:54:20 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git

Re: Potentially missing "memory" clobbers in bitops.h for x86

On Fri, Mar 29, 2019 at 01:52:33PM -0700, H. Peter Anvin wrote: > On 3/29/19 8:54 AM, Alexander Potapenko wrote: > > > >> Of course, this would force the compiler to actually compute the > >> offset, which would slow things down. I have no idea whether this > >> would be better or worse than

Re: [PATCH] i2c: imx: don't leak the i2c adapter on error

On Fri, Mar 29, 2019 at 02:48:17PM +0200, laurentiu.tu...@nxp.com wrote: > From: Laurentiu Tudor > > Make sure to free the i2c adapter on the error exit path. > > Signed-off-by: Laurentiu Tudor > drivers/i2c/busses/i2c-imx.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > >

Re: [PATCH v2 2/2] MAINTAINERS: Add maintainer and replacing reviewer ARM/NUVOTON NPCM

On 3/29/2019 11:02 PM, Benjamin Fair wrote: On Thu, Mar 28, 2019 at 4:58 PM Tomer Maimon wrote: Adding Tali Perry as Nuvoton NPCM maintainer Replacing Brendan Higgins Nuvoton NPCM reviewer with Benjamin Fair. Signed-off-by: Tomer Maimon Reviewed-by: Brendan Higgins Reviewed-by: Benjamin

Re: [PATCH 1/1] ARM: multi_v7_defconfig: enable the Amlogic Meson ADC and eFuse drivers

Martin Blumenstingl writes: > With the SAR ADC driver ADC measurements can be taken though the IIO > framework. Additionally the SAR ADC has a channel which is connected to > an internal temperature sensor. The calibration data for this internal > temperature sensor is stored in the eFuse. > >

slow write performance with software RAID on nvme storage

Hi All, We've been testing a 24 drive NVME software RAID and getting far lower write speeds than expected.  The drives are connected with PLX chips such that 12 drives are on 1 x16 connection and the other 12 drives use another x16 link  The system is a Supermicro 2029U-TN24R4T.  The drives are

Re: [PATCH] arm64: meson-g12a: Add CMA reserved memory

Neil Armstrong writes: > In order to handle Video Output and later on Video decoding, > add a reserved CMA pool with a similar 256MiB size as other SoCs. > > Signed-off-by: Neil Armstrong Queued for v5.2, Thanks, Kevin

[PATCH 1/2] lib/bitmap.c: remove unused EXPORT_SYMBOLs

AFAICT, there have never been any callers of these functions outside mm/mempolicy.c (via their nodemask.h wrappers). In particular, no modular code has ever used them, and given their somewhat exotic semantics, I highly doubt they will ever find such a use. In any case, no need to export them

[PATCH 2/2] lib/bitmap.c: guard exotic bitmap functions by CONFIG_NUMA

The bitmap_remap, _bitremap, _onto and _fold functions are only used, via their node_ wrappers, in mm/mempolicy.c, which is only built for CONFIG_NUMA. The helper bitmap_ord_to_pos used by these functions is global, but its only external caller is node_random() in lib/nodemask.c, which is also

Re: [PATCH v2] gcov: fix when CONFIG_MODULES is not set

On 3/29/19 11:18 AM, Nick Desaulniers wrote: > Fixes commit 8c3d220cb6b5 ("gcov: clang support") There is a certain format for Fixes: and that's not quite it. :( > Cc: Greg Hackmann > Cc: Tri Vo > Cc: Peter Oberparleiter > Cc: linux...@kvack.org > Cc: kbuild-...@01.org > Reported-by: Randy

Re: [PATCH 09/10] PCI: tegra: Add Tegra194 PCIe support

Hi Vidya, Wow, there's a lot of nice work here! Thanks for that! On Tue, Mar 26, 2019 at 08:43:26PM +0530, Vidya Sagar wrote: > Add support for Synopsys DesignWare core IP based PCIe host controller > present in Tegra194 SoC. General comments: - There are a few multi-line comments that

Re: Potentially missing "memory" clobbers in bitops.h for x86

On 3/29/19 8:54 AM, Alexander Potapenko wrote: > >> Of course, this would force the compiler to actually compute the >> offset, which would slow things down. I have no idea whether this >> would be better or worse than just using the "memory" clobber. > Just adding the "memory" clobber to

Re: [PATCH v3 0/6] arm64: dts: g12a: Add boards peripherals

Neil Armstrong writes: > Following [1], add regulators, bluetooth and ADC keys on : > - meson-g12a-x96-max > - meson-g12a-u200 > - meson-g12a-sei510 > > Dependencies : > - Patch 1, 2: None Queued for v5.2 (branch v5.2/dt64) > - Patch 3: SAR ADC node at [2] > - Patches 4, 5, & 6: USB nodes at

[tip:perf/urgent] perf pmu: Fix parser error for uncore event alias

Commit-ID: e94d6b7f615e6dfbaf9fba7db6011db561461d0c Gitweb: https://git.kernel.org/tip/e94d6b7f615e6dfbaf9fba7db6011db561461d0c Author: Kan Liang AuthorDate: Fri, 15 Mar 2019 11:00:14 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 15:53:27 -0300 perf pmu: Fix

Re: [PATCH] bonding: show full hw address in sysfs for slave entries

Konstantin Khorenko wrote: >Bond expects ethernet hwaddr for its slave, but it can be longer than 6 >bytes - infiniband interface for example. > > # cat /sys/devices//net/ib0/address > 80:00:02:08:fe:80:00:00:00:00:00:00:7c:fe:90:03:00:be:5d:e1 > > # cat

Re: [PATCH] ARM: remove unused

On 3/29/2019 9:14 PM, Masahiro Yamada wrote: No one includes this. Signed-off-by: Masahiro Yamada --- Reviewed-by: Mukesh Ojha Cheers, -Mukesh Version: 5.1-rc2 arch/arm/include/asm/limits.h | 12 1 file changed, 12 deletions(-) delete mode 100644

[tip:perf/urgent] perf scripts python: exported-sql-viewer.py: Fix python3 support

Commit-ID: 606bd60ab6fbcb7f73deeef4fa37cfd5e447a200 Gitweb: https://git.kernel.org/tip/606bd60ab6fbcb7f73deeef4fa37cfd5e447a200 Author: Adrian Hunter AuthorDate: Wed, 27 Mar 2019 09:28:26 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 15:53:16 -0300 perf

[tip:perf/urgent] perf scripts python: exported-sql-viewer.py: Fix never-ending loop

Commit-ID: 8453c936db20489dbf0957187dca9a2656a2a7b6 Gitweb: https://git.kernel.org/tip/8453c936db20489dbf0957187dca9a2656a2a7b6 Author: Adrian Hunter AuthorDate: Wed, 27 Mar 2019 09:28:25 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:41:21 -0300 perf

[tip:perf/urgent] perf machine: Update kernel map address and re-order properly

Commit-ID: 977c7a6d1e263ff1d755f28595b99e4bc0c48a9f Gitweb: https://git.kernel.org/tip/977c7a6d1e263ff1d755f28595b99e4bc0c48a9f Author: Wei Li AuthorDate: Thu, 28 Feb 2019 17:20:03 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:41:21 -0300 perf machine:

[tip:perf/urgent] tools headers: Update x86's syscall_64.tbl and uapi/asm-generic/unistd

Commit-ID: 8142bd82a59e452fefea7b21113101d6a87d9fa8 Gitweb: https://git.kernel.org/tip/8142bd82a59e452fefea7b21113101d6a87d9fa8 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 25 Mar 2019 11:34:04 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:41:11 -0300

[tip:perf/urgent] tools headers uapi: Sync powerpc's asm/kvm.h copy with the kernel sources

Commit-ID: 707c373c846cf6e27a47a2c093d243a35c691b62 Gitweb: https://git.kernel.org/tip/707c373c846cf6e27a47a2c093d243a35c691b62 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 26 Mar 2019 13:45:58 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:41:21 -0300

[tip:perf/urgent] tools headers uapi: Update drm/i915_drm.h

Commit-ID: 82392516e9e0818cd2227cf9a16205c90a6cacfa Gitweb: https://git.kernel.org/tip/82392516e9e0818cd2227cf9a16205c90a6cacfa Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 25 Mar 2019 14:28:20 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:56 -0300

Re: [PATCH v2] writeback: use exact memcg dirty counts

On Fri, Mar 29, 2019 at 10:46:09AM -0700, Greg Thelen wrote: > Since commit a983b5ebee57 ("mm: memcontrol: fix excessive complexity in > memory.stat reporting") memcg dirty and writeback counters are managed > as: > 1) per-memcg per-cpu values in range of [-32..32] > 2) per-memcg atomic counter >

[tip:perf/urgent] tools arch x86: Sync asm/cpufeatures.h with the kernel sources

Commit-ID: 949af89af02c2d66db973c5bca01b7858e1ce0ba Gitweb: https://git.kernel.org/tip/949af89af02c2d66db973c5bca01b7858e1ce0ba Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 25 Mar 2019 14:25:33 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:56 -0300

[tip:perf/urgent] tools headers uapi: Sync linux/fcntl.h to get the F_SEAL_FUTURE_WRITE addition

Commit-ID: e33ff03da16041d0a23eef93d39918e1758175fb Gitweb: https://git.kernel.org/tip/e33ff03da16041d0a23eef93d39918e1758175fb Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 25 Mar 2019 14:22:47 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:56 -0300

[tip:perf/urgent] tools headers uapi: Sync asm-generic/mman-common.h and linux/mman.h

Commit-ID: be709d48329a500621d2a05835283150ae137b45 Gitweb: https://git.kernel.org/tip/be709d48329a500621d2a05835283150ae137b45 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 25 Mar 2019 14:06:07 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:56 -0300

[tip:perf/urgent] perf evsel: Fix max perf_event_attr.precise_ip detection

Commit-ID: 4e8a5c1551370ebc0fbdb8f5c33dad13e45bdc99 Gitweb: https://git.kernel.org/tip/4e8a5c1551370ebc0fbdb8f5c33dad13e45bdc99 Author: Jiri Olsa AuthorDate: Thu, 14 Mar 2019 15:00:10 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:56 -0300 perf evsel: Fix

[tip:perf/urgent] perf intel-pt: Fix TSC slip

Commit-ID: f3b4e06b3bda759afd042d3d5fa86bea8f1fe278 Gitweb: https://git.kernel.org/tip/f3b4e06b3bda759afd042d3d5fa86bea8f1fe278 Author: Adrian Hunter AuthorDate: Mon, 25 Mar 2019 15:51:35 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:55 -0300 perf

[tip:perf/urgent] perf cs-etm: Add missing case value

Commit-ID: c8fa7a807f3c5f946bd92076fbaf7826edb650dc Gitweb: https://git.kernel.org/tip/c8fa7a807f3c5f946bd92076fbaf7826edb650dc Author: Solomon Tan AuthorDate: Fri, 22 Mar 2019 13:22:55 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 28 Mar 2019 14:31:55 -0300 perf cs-etm:

Re: [PATCH] riscv: fix syscall_get_arguments() and syscall_set_arguments()

On Fri, 29 Mar 2019 21:16:19 +0300 "Dmitry V. Levin" wrote: > This is fine with me. If you are adding the fix for riscv, > please consider adding the fix for csky, too. Yes of course. I mentioned both of these fixes in my reply to Linus. -- Steve

Re: [PATCH] vfio: Use dev_printk() when possible

On Fri, 29 Mar 2019 12:03:11 -0500 Bjorn Helgaas wrote: > On Mon, Mar 25, 2019 at 3:49 PM Joe Perches wrote: > > > > On Mon, 2019-03-25 at 14:42 -0500, Bjorn Helgaas wrote: > > > Use dev_printk() when possible to make messages consistent with other > > > device-related messages. > > > >

Re: [PATCH] riscv: fix syscall_get_arguments() and syscall_set_arguments()

On Fri, 29 Mar 2019 21:11:09 +0300 "Dmitry V. Levin" wrote: > On Fri, Mar 29, 2019 at 01:56:35PM -0400, Steven Rostedt wrote: > > On Fri, 29 Mar 2019 18:52:18 +0100 > > David Abdurachmanov wrote: > > > > > I have alternative version posted in December part of SECCOMP > > > patchset which is

Re: [PATCH v2 4/4] x86/uaccess: Fix implicit cast of __user pointer

On 3/29/2019 10:00 PM, Jann Horn wrote: The first two arguments of __user_atomic_cmpxchg_inatomic() are: - `uval` is a kernel pointer into which the old value should be stored - `ptr` is the user pointer on which the cmpxchg should operate This means that casting `uval` to

Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller

On Fri, Mar 29, 2019 at 02:41:05PM -0500, Rob Herring wrote: > DT dictates aligning with what the h/w looks like which has little to > do with OS driver design. Ok, then, where does this goal for doing a driver or compilation unit per IP block come from? Because everytime an ARM EDAC driver pops

Re: [PATCH v5] iio: cros_ec: Add lid angle driver

On Fri, Mar 29, 2019 at 1:08 PM Gwendal Grignou wrote: > > Add a IIO driver that reports the angle between the lid and the base for > ChromeOS convertible device. > > Tested on eve with ToT EC firmware. > Check driver is loaded and lid angle is correct. > > Signed-off-by: Gwendal Grignou > --- >

RE: [PATCH 5/6] acpi/cppc: Add support for optional CPPC registers

> -Original Message- > From: linux-acpi-ow...@vger.kernel.org On > Behalf Of Pandruvada, Srinivas > Sent: Wednesday, March 27, 2019 10:48 AM > To: linux-kernel@vger.kernel.org; de...@acpica.org; Natarajan, Janakarajan > ; linux- > a...@vger.kernel.org; linux...@vger.kernel.org > Cc:

[PATCH v5] iio: cros_ec: Add lid angle driver

Add a IIO driver that reports the angle between the lid and the base for ChromeOS convertible device. Tested on eve with ToT EC firmware. Check driver is loaded and lid angle is correct. Signed-off-by: Gwendal Grignou --- Changes in v5: - Remove unnecessary define. - v4 was the wrong patch file

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On 3/28/19 7:25 PM, Jerome Glisse wrote: [...] >> The input value is not the problem. The problem is in the naming. >> >> obj = get_obj( various parameters ); >> put_obj(obj); >> >> >> The problem is that the function is named hmm_register() either "gets" a >> reference to _or_ creates and gets a

[PATCH v3] HID: intel-ish-hid: ISH firmware loader client driver

This driver adds support for loading Intel Integrated Sensor Hub (ISH) firmware from host file system to ISH SRAM and start execution. At power-on, the ISH subsystem shall boot to an interim Shim loader-firmware, which shall expose an ISHTP loader device. The driver implements an ISHTP client

Re: [PATCH v2] HID: intel-ish-hid: ISH firmware loader client driver

Hi Nick Please see my comments inline below, On Thu, Mar 28, 2019 at 11:02:52PM -0700, Nick Crews wrote: > This is so close! There are just one or two tiny things. > > On Thu, Mar 28, 2019 at 1:20 PM Rushikesh S Kadam > wrote: > > +/** > > + * loader_cl_send()Send message from host to

Re: linux-next: Fixes tag needs some work in the tty.current tree

On Thu, Mar 28, 2019 at 07:27:34AM +1100, Stephen Rothwell wrote: > Hi all, > > In commit > > 69646d7a3689 ("tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is > stopped") > > Fixes tag > > Fixes: b389f173aaa1 ("tty/serial: atmel: RS485 half duplex w/DMA: enable > > has these

Re: [PATCH v8 1/2] dt-bindings: misc: aspeed-p2a-ctrl: add support

On Fri, Mar 29, 2019 at 10:11 AM Patrick Venture wrote: > > On Fri, Mar 29, 2019 at 7:59 AM Patrick Venture wrote: > > > > On Fri, Mar 29, 2019 at 7:56 AM Patrick Venture wrote: > > > > > > On Fri, Mar 29, 2019 at 6:38 AM Rob Herring wrote: > > > > > > > > On Thu, Mar 28, 2019 at 12:03 PM

Re: [PATCH 2/2] edac: sifive: Add EDAC driver for SiFive FU540-C000 chip

On Wed, 20 Mar 2019, Yash Shah wrote: > This EDAC driver supports: > - Initial configuration reporting on bootup via debug logs > - ECC event monitoring and reporting through the EDAC framework > - ECC event injection > > This driver is partially based on pnd2_edac.c and altera_edac.c > >

Re: [PATCH] Convert struct pid count to refcount_t

On Fri, 29 Mar 2019, Oleg Nesterov wrote: > On 03/28, Paul E. McKenney wrote: > > > > On Thu, Mar 28, 2019 at 05:26:42PM +0100, Oleg Nesterov wrote: > > > > > > Since you added Paul let me add more confusion to this thread ;) > > > > Woo-hoo!!! More confusion! Bring it on!!! ;-) > > OK,

Re: [PATCH v2 3/4] x86/fpu: Fix __user annotations

On Fri, Mar 29, 2019 at 08:25:25PM +0100, Jann Horn wrote: > Oooh, it's a sparse bug. It's *not* a bug. > Apparently it's significant that the user pointer is stored as a > __u64, and __u64 is defined as unsigned long long. Yes, it is. Casts to uintptr_t (== unsigned long on all targets) are

Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller

On Fri, Mar 29, 2019 at 9:27 AM Borislav Petkov wrote: > > On Fri, Mar 29, 2019 at 09:11:24AM -0500, Rob Herring wrote: > > I honestly don't understand the issue with EDAC is here. > > The EDAC core supports only one driver and if you need to load more, you > need to dance around that. > > Also,

[GIT PULL] Driver core fixes for 5.1-rc3

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.1-rc3 for you to fetch changes up to

Re: [PATCH 1/3] clk: meson: mpll: properly handle spread spectrum

Hi Jerome, On Fri, Mar 29, 2019 at 4:34 PM Jerome Brunet wrote: > > The bit 'SSEN' available on some MPLL DSS outputs is not related to the > fractional part of the divider but to the function called > 'Spread Spectrum'. > > This function might be used to solve EM issues by adding a jitter on >

[GIT PULL] Char/Misc driver fixes for 5.1-rc3

The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00: Linux 5.1-rc2 (2019-03-24 14:02:26 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.1-rc3 for you to fetch changes up to

[PATCH] LSM: Revive CONFIG_DEFAULT_SECURITY_* for "make oldconfig"

Commit 70b62c25665f636c ("LoadPin: Initialize as ordered LSM") removed CONFIG_DEFAULT_SECURITY_{SELINUX,SMACK,TOMOYO,APPARMOR,DAC} from security/Kconfig and changed CONFIG_LSM to provide a fixed ordering as a default value. That commit expected that existing users (upgrading from Linux 5.0 and

Re: [PATCH v2 3/4] x86/fpu: Fix __user annotations

+sparse list On Fri, Mar 29, 2019 at 7:03 PM Luc Van Oostenryck wrote: > > On Fri, Mar 29, 2019 at 05:30:46PM +0100, Jann Horn wrote: > > In save_xstate_epilog(), use __user when type-casting userspace pointers. > > > > In setup_sigcontext() and x32_setup_rt_frame(), perform explicit __force > >

Re: [RFC][PATCH 0/4 v2] sycalls: Remove args i and n from syscall_get_arguments()

On Fri, Mar 29, 2019 at 11:12:18AM -0700, Linus Torvalds wrote: > On Fri, Mar 29, 2019 at 10:40 AM Steven Rostedt wrote: > > > > I'll keep it around for now, but this should go as a warning to Dmitry, > > to get something using it soon, or they may be dropped. > > I don't think _that_ is the

Re: [PATCH 24/25] coresight: Support for ACPI bindings

On Wed, Mar 20, 2019 at 06:49:41PM +, Suzuki K Poulose wrote: > Add support for parsing the ACPI platform description > for CoreSight. The connections are encoded in a DSD graph > property with CoreSight specific variation of the property. > > The ETMs are listed as the children device of the

Re: [PATCH v10 02/12] perf record: implement --mmap-flush= option

Em Mon, Mar 18, 2019 at 08:40:26PM +0300, Alexey Budankov escreveu: > > Implemented --mmap-flush option that specifies minimal number of bytes > that is extracted from mmaped kernel buffer to store into a trace. The > default option value is 1 byte what means every time trace writing > thread

[GIT PULL] arm64 fixes for 5.1-rc3

Hi Linus, Please pull the arm64 fix below. Thanks. The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00: Linux 5.1-rc2 (2019-03-24 14:02:26 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes for

Re: [PATCH] habanalabs: improve error messages

On Fri, Mar 29, 2019 at 08:29:08PM +0300, Oded Gabbay wrote: > On Fri, Mar 29, 2019 at 7:29 PM Greg KH wrote: > > > > On Thu, Mar 28, 2019 at 09:13:13AM +0200, Oded Gabbay wrote: > > > This patch improves two error messages to help the user to > > > better understand what error occurred. > > > >

Re: [PATCH 04/13] tools headers uapi: Sync asm-generic/mman-common.h and linux/mman.h

Em Fri, Mar 29, 2019 at 10:20:06AM -0400, Michael S. Tsirkin escreveu: > On Fri, Mar 29, 2019 at 10:37:52AM -0300, Arnaldo Carvalho de Melo wrote: > > From: Arnaldo Carvalho de Melo > > > > To deal with the move of some defines from asm-generic/mmap-common.h to > > linux/mman.h done in: > > > >

Re: [GIT PULL] tpmdd fixes for Linux v5.1

On Fri, 29 Mar 2019, Jarkko Sakkinen wrote: > Hi James, > > These are critical fixes for v5.1. Contains also couple of new selftests for > v5.1 features (partial reads in /dev/tpm0). I hope these could still reach > the release. Thanks. Applied to

Re: [PATCH] regulator: vctrl: Remove unneeded continue statement

Hi Axel, On Fri, Mar 29, 2019 at 09:46:31AM +0800, Axel Lin wrote: As Mukesh already mentioned, there should be a short description. > Signed-off-by: Axel Lin > --- > drivers/regulator/vctrl-regulator.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git

[PATCH tip/core/rcu 2/2] rcu: Check for wakeup-safe conditions in rcu_read_unlock_special()

When RCU core processing is offloaded from RCU_SOFTIRQ to the rcuc kthreads, a full and unconditional wakeup is required to initiate RCU core processing. In contrast, when RCU core processing is carried out by RCU_SOFTIRQ, a raise_softirq() suffices. Of course, there are situations where

[PATCH tip/core/rcu 1/2] rcu: Enable elimination of Tree-RCU softirq processing

From: Sebastian Andrzej Siewior Some workloads need to change kthread priority for RCU core processing without affecting other softirq work. This commit therefore introduces the rcutree.use_softirq kernel boot parameter, which moves the RCU core work from softirq to a per-CPU SCHED_OTHER

[PATCH RFC tip/core/rcu 0/2] Real-time elimination of RCU_SOFTIRQ

Hello! This series is an early posting of code to add a boot-time option to move RCU's softirq processing to per-CPU kthreads. This is not done by default for performance reasons, nor are these reasons theoretical. In fact, earlier attempts to do just this were not met with silence. The patches

Re: [PATCH v2] tty/serial: Add a serial port simulator

On 2019-03-29, Corey Minyard wrote: > On Thu, Mar 28, 2019 at 12:39:12PM -0700, H. Peter Anvin wrote: > >> Dumb question: this is basically a pty on steroids. Wouldn't this be >> better done by enhancing the pty devices? I proposed doing that several years ago, and offered to start working on it

Re: [PATCH] ELAN touchpad i2c_hid bugs fix

On Fri, Mar 29, 2019 at 5:18 AM Hans de Goede wrote: > > Hi, > > On 3/25/19 5:56 PM, Dmitry Torokhov wrote: > > Hi Hans, > > > > On Mon, Mar 25, 2019 at 9:38 AM Hans de Goede wrote: > >> > >> Hi Dmitry, > >> > >> On 25-03-19 17:02, Dmitry Torokhov wrote: > >>> Hi Vladislav, > >>> > >>> On Mon,

[tip:x86/asm] x86/cpufeature: Remove __pure attribute to _static_cpu_has()

Commit-ID: ae37a8cd9b0ad3416d71e54cfaeb3744178189a8 Gitweb: https://git.kernel.org/tip/ae37a8cd9b0ad3416d71e54cfaeb3744178189a8 Author: Borislav Petkov AuthorDate: Thu, 7 Mar 2019 15:54:51 +0100 Committer: Borislav Petkov CommitDate: Fri, 29 Mar 2019 19:13:48 +0100 x86/cpufeature:

Re: [RFC][PATCH 0/4 v2] sycalls: Remove args i and n from syscall_get_arguments()

On Fri, Mar 29, 2019 at 10:40 AM Steven Rostedt wrote: > > I'll keep it around for now, but this should go as a warning to Dmitry, > to get something using it soon, or they may be dropped. I don't think _that_ is the argument. Quite the reverse: nobody has ever used it, why have it around, and

[PATCH v2] gcov: fix when CONFIG_MODULES is not set

Fixes commit 8c3d220cb6b5 ("gcov: clang support") Cc: Greg Hackmann Cc: Tri Vo Cc: Peter Oberparleiter Cc: linux...@kvack.org Cc: kbuild-...@01.org Reported-by: Randy Dunlap Reported-by: kbuild test robot Link: https://marc.info/?l=linux-mm=155384681109231=2 Signed-off-by: Nick Desaulniers

Re: [PATCH] riscv: fix syscall_get_arguments() and syscall_set_arguments()

On Fri, Mar 29, 2019 at 01:15:14PM -0400, Steven Rostedt wrote: > On Fri, 29 Mar 2019 20:12:21 +0300 > "Dmitry V. Levin" wrote: > > > RISC-V syscall arguments are located in orig_a0,a1..a5 fields > > of struct pt_regs. > > > > Due to an off-by-one bug and a bug in pointer arithmetic > >

[PATCH 3/4] ARM: dts: imx6qdl: Use new CODEC reset pin name

The correct DT property for specifying a GPIO used for reset is "reset-gpios", the driver now accepts this name, use it here. Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-var-dart.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] ARM: dts: omap2420-n810: Use new CODEC reset pin name

The correct DT property for specifying a GPIO used for reset is "reset-gpios", the driver now accepts this name, use it here. Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/omap2420-n810.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/4] ARM: dts: imx: Use new CODEC reset pin name

The correct DT property for specifying a GPIO used for reset is "reset-gpios", the driver now accepts this name, use it here. Signed-off-by: Andrew F. Davis --- arch/arm/boot/dts/imx6qdl-gw5903.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/4] ARM: dts: imx6: RDU2: Use new CODEC reset pin name

The correct DT property for specifying a GPIO used for reset is "reset-gpios", the driver now accepts this name, use it here. Note the GPIO polarity in the driver was ignored before and always assumed to be active low, when all the DTs are fixed we will start respecting the specified polarity.

Re: [PATCH] riscv: fix syscall_get_arguments() and syscall_set_arguments()

On Fri, Mar 29, 2019 at 01:56:35PM -0400, Steven Rostedt wrote: > On Fri, 29 Mar 2019 18:52:18 +0100 > David Abdurachmanov wrote: > > > I have alternative version posted in December part of SECCOMP > > patchset which is based on arm64 implementation. > > > >

Re: [PATCH] gcov: include linux/module.h for within_module

On 3/29/19 11:09 AM, Nick Desaulniers wrote: > On Fri, Mar 29, 2019 at 11:01 AM Randy Dunlap wrote: >> >> On 3/29/19 10:45 AM, Nick Desaulniers wrote: >>> Fixes commit 8c3d220cb6b5 ("gcov: clang support") >>> >>> Cc: Greg Hackmann >>> Cc: Tri Vo >>> Cc: Peter Oberparleiter >>> Cc:

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