It makes sense to contain all the ACPI IRQ handling in a single helper
function.
Reviewed-by: Andy Shevchenko
Signed-off-by: Charles Keepax
---
No change since v7.
Thanks,
Charles
drivers/i2c/i2c-core-acpi.c | 3 +++
drivers/i2c/i2c-core-base.c | 3 ---
2 files changed, 3 insertions(+), 3 de
Remove the static from i2c_dev_irq_from _resources so that other parts
of the core code can use this helper function.
Reviewed-by: Mika Westerberg
Reviewed-by: Andy Shevchenko
Signed-off-by: Charles Keepax
---
No change since v7.
Thanks,
Charles
drivers/i2c/i2c-core-base.c | 4 ++--
drivers
On Fri, 21 Jun 2019, Daniel Thompson wrote:
> On 13/06/2019 20:43, Matthias Kaehlcke wrote:
> > For backlight curves calculated with the CIE 1931 algorithm set
> > the brightness scale type property accordingly. This makes the
> > scale type available to userspace via the 'scale' sysfs attribute.
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus
to receive the following fixes for HID subsystem:
=
- fix for one corner case in HID++ protocol with respect to handling very
long reports, from Hans de Goede
- power management fix in Intel-ISH
ksize() has been unconditionally unpoisoning the whole shadow memory region
associated with an allocation. This can lead to various undetected bugs,
for example, double-kzfree().
Specifically, kzfree() uses ksize() to determine the actual allocation
size, and subsequently zeroes the memory. Since
This version only changes use of BUG_ON to WARN_ON_ONCE in
mm/slab_common.c.
Previous version:
http://lkml.kernel.org/r/20190626142014.141844-1-el...@google.com
Marco Elver (5):
mm/kasan: Introduce __kasan_check_{read,write}
mm/kasan: Change kasan_check_{read,write} to return boolean
lib/te
This introduces __kasan_check_{read,write}. __kasan_check functions may
be used from anywhere, even compilation units that disable
instrumentation selectively.
This change eliminates the need for the __KASAN_INTERNAL definition.
Signed-off-by: Marco Elver
Cc: Andrey Ryabinin
Cc: Dmitry Vyukov
This refactors common code of ksize() between the various allocators
into slab_common.c: __ksize() is the allocator-specific implementation
without instrumentation, whereas ksize() includes the required KASAN
logic.
Signed-off-by: Marco Elver
Cc: Andrey Ryabinin
Cc: Dmitry Vyukov
Cc: Alexander
This changes {,__}kasan_check_{read,write} functions to return a boolean
denoting if the access was valid or not.
Signed-off-by: Marco Elver
Cc: Andrey Ryabinin
Cc: Dmitry Vyukov
Cc: Alexander Potapenko
Cc: Andrey Konovalov
Cc: Christoph Lameter
Cc: Pekka Enberg
Cc: David Rientjes
Cc: Joon
Adds a simple test that checks if double-kzfree is being detected
correctly.
Signed-off-by: Marco Elver
Cc: Andrey Ryabinin
Cc: Dmitry Vyukov
Cc: Alexander Potapenko
Cc: Andrey Konovalov
Cc: Christoph Lameter
Cc: Pekka Enberg
Cc: David Rientjes
Cc: Joonsoo Kim
Cc: Andrew Morton
Cc: Mark
The callback functions use a signed int type, but the callers have
only verified the value as an unsigned type. This should be only
a cosmetic change because if the value wraps around, this error
check catches it:
if (reclen > buf->count)
return -EINVAL;
But it should be
The WiFi tx power of RTL8723BU is extremely low after booting. So
the WiFi scan gives very limited AP list and it always fails to
connect to the selected AP. This module only supports 1x1 antenna
and the antenna is switched to bluetooth due to some incorrect
register settings.
This commit hand ove
On Thu, Jun 27, 2019 at 7:00 AM Viresh Kumar wrote:
>
> On 20-06-19, 08:35, Viresh Kumar wrote:
> > > CPUFREQ_CONST_LOOPS was introduced in a very old commit from pre-2.6
> > > kernel release commit 6a4a93f9c0d5 ("[CPUFREQ] Fix 'out of sync'
> > > issue").
> > >
> > > Probably the initial idea was
Mans Rullgard writes:
> In order for devicetree nodes to be correctly associated with attached
> devices, the controller node needs to be propagated to the glue device.
>
> Signed-off-by: Mans Rullgard
> ---
> This depends on 2c1ea6abde88 ("platform: set of_node in
> platform_device_register_ful
On Wed, Jun 26, 2019 at 08:01:58PM +0100, Vincenzo Frascino wrote:
[...]
> On 6/26/19 5:14 PM, Dave Martin wrote:
> > On Wed, Jun 26, 2019 at 02:27:59PM +0100, Vincenzo Frascino wrote:
> >> Hi Dave,
> >>
> >> On 25/06/2019 16:33, Dave Martin wrote:
> >>> On Fri, Jun 21, 2019 at 10:52:31AM +0100,
On 5/25/19 9:07 AM, zhong jiang wrote:
> We bind an different node to different vma, Unluckily,
> it will bind different vma to same node by checking the /proc/pid/numa_maps.
>
> Commit 213980c0f23b ("mm, mempolicy: simplify rebinding mempolicies when
> updating cpusets")
> has introduced the
On Mon, Jun 10, 2019 at 02:09:45PM +0100, Stefan Hajnoczi wrote:
> On Tue, May 28, 2019 at 12:56:19PM +0200, Stefano Garzarella wrote:
> > During the review of "[PATCH] vsock/virtio: Initialize core virtio vsock
> > before registering the driver", Stefan pointed out some possible issues
> > in the
Device pointer stored in umem regardless of zero-copy mode,
so we heed to hold the device in all cases.
Fixes: c9b47cc1fabc ("xsk: fix bug when trying to use both copy and zero-copy
on one queue id")
Signed-off-by: Ilya Maximets
---
net/xdp/xdp_umem.c | 11 ++-
1 file changed, 6 inserti
Version 5:
* Fixed incorrect handling of rtnl_lock.
Version 4:
* 'xdp_umem_clear_dev' exposed to be used while unregistering.
* Added XDP socket state to track if resources already unbinded.
* Splitted in two fixes.
Version 3:
* Declaration lines ordered from longest to sho
Device that bound to XDP socket will not have zero refcount until the
userspace application will not close it. This leads to hang inside
'netdev_wait_allrefs()' if device unregistering requested:
# ip link del p1
< hang on recvmsg on netlink socket >
# ps -x | grep ip
5126 pts/0D+
'probe libc's inet_pton & backtrace it with ping' testcase sometimes
fails on powerpc because distro ping binary does not have symbol
information and thus it prints "[unknown]" function name in the
backtrace.
Accept "[unknown]" as valid function name for powerpc as well.
# perf test -v "probe li
Use for_each_ancestor macro to iterate a cgroup's ancestors for clarity.
Signed-off-by: Peng Wang
---
include/linux/cgroup.h | 11 +++
kernel/cgroup/cgroup.c | 7 +++
kernel/cgroup/freezer.c | 2 +-
kernel/cgroup/rstat.c | 4 ++--
4 files changed, 17 insertions(+), 7 deletions
On Thu, Jun 27, 2019 at 08:55:21AM +, Zhang, Tina wrote:
>
>
> > -Original Message-
> > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> > Behalf Of Gerd Hoffmann
> > Sent: Thursday, June 27, 2019 2:20 PM
> > To: Zhang, Tina
> > Cc: Tian, Kevin ; k...@vge
On 26.06.2019 21:36, Stephen Boyd wrote:
> Quoting claudiu.bez...@microchip.com (2019-05-21 03:11:33)
>> From: Claudiu Beznea
>>
>> Add support for SAM9X60's slow clock.
>>
>> Signed-off-by: Claudiu Beznea
>> Acked-by: Alexandre Belloni
>> ---
>
> FYI, this patch is base64 encoded and causes
On Thu, Jun 27, 2019 at 12:08:01AM +0530, Naveen N. Rao wrote:
> The recent change enabling HAVE_C_RECORDMCOUNT on powerpc started
> showing the following issue:
>
> # modprobe kprobe_example
>ftrace-powerpc: Not expected bl: opcode is 3c4c0001
>WARNING: CPU: 0 PID: 227 at kernel/trace/f
On Thu, Jun 13, 2019 at 04:57:15PM +0800, Jason Wang wrote:
>
> On 2019/6/6 下午4:11, Stefano Garzarella wrote:
> > On Fri, May 31, 2019 at 05:56:39PM +0800, Jason Wang wrote:
> > > On 2019/5/31 下午4:18, Stefano Garzarella wrote:
> > > > On Thu, May 30, 2019 at 07:59:14PM +0800, Jason Wang wrote:
> >
Hi Anson,
On 27/06/2019 10:11, Anson Huang wrote:
> Hi, Daniel
>
>> On 27/06/2019 02:43, Anson Huang wrote:
>>> Hi, Daniel
>>>
On 26/06/2019 03:42, Anson Huang wrote:
> Hi, Daniel
>
>> On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
>>> From: Anson Huang
>>>
>>> Sy
Hi Chanwoo,
On 6/27/19 3:11 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 6. 26. 오후 11:17, Lukasz Luba wrote:
>> Hi Krzysztof,
>>
>> On 6/26/19 4:03 PM, Krzysztof Kozlowski wrote:
>>> On Wed, 26 Jun 2019 at 15:58, Lukasz Luba
>>> wrote:
Hi Chanwoo,
On 6/26/19 10:23 AM, Cha
> > Hi,
> >
> > > Instead of delivering page flip events, we choose to post display
> > > vblank event. Handling page flip events for both primary plane and
> > > cursor plane may make user space quite busy, although we have the
> > > mask/unmask mechansim for mitigation. Besides, there are some
On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Systems which use platform driver model for clock driver require the
> clock frequency to be supplied via device tree when system counter
> driver is enabled.
>
> This is necessary as in the platform driver model the of_clk
Am Freitag, 14. Juni 2019, 18:54:50 CEST schrieb Heiko Stuebner:
> The hdmiphy needs its clock reparented to the actual hdmiphy-pll
> that gets generated in the hdmiphy itself.
>
> This incorporates adapted versions of Justin's original patches
> and also the needed clock adaptions to make it poss
Use mfd_add_hotplug_devices() helper to register the subdevices.
Signed-off-by: Enric Balletbo i Serra
---
Changes in v4: None
Changes in v3:
- Add a new patch to use mfd_add_hoplug_devices to register subdevices
Changes in v2: None
drivers/mfd/cros_ec_dev.c | 18 ++
1 file ch
The CrOS EC is gaining lots of subdevices that are autodetectable by
sending the EC_FEATURE_GET_CMD, it takes fair amount of boiler plate
code to add those devices. So, add a struct that can be used to quickly
add new subdevices without having to duplicate code.
Signed-off-by: Enric Balletbo i Ser
That's a driver to talk with the ChromeOS Embedded Controller via a
miscellaneous character device, it creates an entry in /dev for every
instance and implements basic file operations for communicating with the
Embedded Controller with an userspace application. The API is moved to
the uapi folder,
This patch makes use of cros_ec_cmd_xfer_status() instead of
cros_ec_cmd_xfer() so we can remove some redundant code. It also uses
kzalloc instead of kmalloc so we can remove more redundant code.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Tested-by: Gwendal Grignou
---
Cha
There is a bit of mess between cros-ec mfd includes and platform
includes. For example, we have a linux/mfd/cros_ec.h include that
exports the interface implemented in platform/chrome/cros_ec_proto.c. Or
we have a linux/mfd/cros_ec_commands.h file that is non related to the
multifunction device (in
Am Samstag, 15. Juni 2019, 17:30:30 CEST schrieb Heiko Stuebner:
> Needed to export that added clock.
>
> Signed-off-by: Heiko Stuebner
applied all 3 patches to relevant branches for 5.3
Cheers
Heiko
With the increasing use of dedicated CrOS EC MCUs, it takes a fair amount
of boiler plate code to add those devices, add a struct that can be used
to specify a dedicated CrOS EC MCU so we can just add a new item to it to
define a new dedicated MCU.
Signed-off-by: Enric Balletbo i Serra
Acked-by:
With the purpose of remove the things that far extends the bounds of
what a MFD was designed to do, instantiate the new platform misc
cros-ec-chardev driver and get rid of all the unneeded code. After this
patch the misc chardev driver is a sub-device of the MFD, and all the
new file operations sho
Recently we refactored the CrOS EC drivers moving part of the code from
the MFD subsystem to the platform chrome subsystem. During this change
we needed to rename some config options, so, update the defconfigs
accordingly.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Krzysztof Kozlowski
Teste
An MFD is a device that contains several sub-devices (cells). For instance,
the ChromeOS EC fits in this description as usually contains a charger and
can have other devices with different functions like a Real-Time Clock,
an Audio codec, a Real-Time Clock, ...
If you look at the driver, though, w
Now, the ChromeOS EC core driver has nothing related to an MFD device, so
move that driver from the MFD subsystem to the platform/chrome subsystem.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Acked-by: Thierry Reding
Acked-by: Mark Brown
Acked-by: Wolfram Sang
Acked-by: Ne
The cros-ec-dev is a multifunction device that now doesn't implement any
chardev communication interface. MFD_CROS_EC_CHARDEV doesn't look
a good name to describe that device and can cause confusion. Hence
rename it to CROS_EC_DEV.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Hi,
This is another attempt to clean up a bit more the cros-ec driver
to have a better separation on what is part of the MFD subsystem and
what is part of platform/chrome.
It'd be really nice have some reviews, acks and tested on different
platforms from the chromiumos people before merge all thi
On 2019/6/27 18:19, Peng Wang wrot:
Use for_each_ancestor macro to iterate a cgroup's ancestors for clarity.>
This patch doesn't make much sense to me. Because it does not reduce lines of
code,
and I don't think it will reduce the size of the kernel, and the original code
is
not bad in readab
Hi all,
this series cleans up the xfs writepage code and then lifts it to
fs/iomap.c so that it could be use by other file system. I've been
wanting to this for a while so that I could eventually convert gfs2
over to it, but I never got to it. Now Damien has a new zonefs
file system for semi-raw
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/xfs/xfs_aops.h b/fs/xfs/xfs_aops.h
index f62b03186c62..45a1ea240cbb 100644
--- a/fs/xfs/xfs_aops.h
+++ b/fs/xfs/xfs_aops.h
@@ -28,7 +28,6 @@ extern const struct address_space_operations xf
In preparation for moving the writeback code to iomap.c, replace the
XFS-specific COW fork concept with the iomap IOMAP_F_SHARED flag.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 42 ++
fs/xfs/xfs_aops.h | 2 +-
Takes the xfs writeback code and move it to iomap.c. A new structure
with three methods is added as the abstraction from the generic
writeback code to the file system. These methods are used to map
blocks, submit an ioend, and cancel a page that encountered an error
before it was added to an ioen
Compare the block layer status directly instead of converting it to
an errno first.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index
The fail argument is long gone, update the comment.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index 73c291aeae17..8f7b2d91d9a4 100644
--- a/fs/xfs/
There is no real problem merging ioends that go beyond i_size into an
ioend that doesn't. We just need to move the append transaction to the
base ioend. Also use the opportunity to use a real error code instead
of the magic 1 to cancel the transactions, and write a comment
explaining the scheme.
Introduce two nicely abstracted helper, which can be moved to the
iomap code later. Also use list_pop_entry and list_first_entry_or_null
to simplify the code a bit.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 70 +---
We have a very common pattern where we want to delete the first entry
from a list and return it as the properly typed container structure.
Add two helpers to implement this behavior.
Signed-off-by: Christoph Hellwig
---
include/linux/list.h | 33 +
1 file changed
Lift the xfs code for tracing address space operations to the iomap
layer.
Signed-off-by: Christoph Hellwig
---
fs/iomap.c | 13 +-
fs/xfs/xfs_aops.c| 27 ++--
fs/xfs/xfs_trace.h | 65 ---
include/trace/events/iomap.h |
In preparation for moving the ioend structure to common code we need
to get rid of the xfs-specific xfs_trans type. Just make it a file
system private void pointer instead.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 26 +-
fs/xfs/xfs_aops.h | 2 +-
2 files
In preparation for moving the XFS writeback code to fs/iomap.c, switch
it to use struct iomap instead of the XFS-specific struct xfs_bmbt_irec.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
---
fs/xfs/libxfs/xfs_bmap.c | 14 +--
fs/xfs/libxfs/xfs_bmap.h | 3 +-
fs/xfs/xfs_a
Instead of a magic flag for xfs_trans_alloc, just ensure all callers
that can't relclaim through the file system use memalloc_nofs_save to
set the per-task nofs flag.
Signed-off-by: Christoph Hellwig
---
fs/xfs/libxfs/xfs_shared.h | 1 -
fs/xfs/xfs_aops.c | 35 ++---
Currently we don't overwrite the flags field in the iomap in
xfs_bmbt_to_iomap. This works fine with 0-initialized iomaps on stack,
but is harmful once we want to be able to reuse an iomap in the
writeback code. Replace the shared paramter with a set of initial
flags an thus ensures the flags fie
Hi Dave,
Overall, I want to thank you for bringing out the topic. It helped me to
question some decisions and make sure that we have no holes left in the
approach.
[...]
>>
>> vDSO library is a shared object not compiled with LTO as far as I can
>> see, hence if this involved LTO should not app
syzbot has bisected this bug to:
commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650
Author: John Fastabend
Date: Sat Jun 30 13:17:47 2018 +
bpf: sockhash fix omitted bucket lock in sock_close
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13dd1b79a0
start commit: abf
Hi Rob,
On Wed, 26 Jun 2019 15:58:50 -0600
Rob Herring wrote:
> On Fri, Jun 21, 2019 at 10:18 AM Masami Hiramatsu wrote:
> >
> > Hi,
> >
> > Here is an RFC series of patches to add boot-time tracing using
> > devicetree.
> >
> > Currently, kernel support boot-time tracing using kernel command-l
On Thu, Jun 27, 2019 at 10:52:26AM +0200, Maxime Chevallier wrote:
> When parsing an ethtool_rx_flow_spec, users can specify an ethernet flow
> which could contain matches based on the ethernet header, such as the
> MAC address, the VLAN tag or the ethertype.
>
> ETHER_FLOW uses the src and dst et
Dear Linux folks,
On a Dell OptiPlex 5040 with Linux 5.2-rc6 plugging in a
head phone into the front case connector, it is detected
just fine and Xfce shows a notification.
Then logging out, turning off the monitor connected over
DisplayPort at the end of the day, and turning the monitor
back on
Hi all,
Changes since 20190626:
The arm64 tree gained a conflict aginst the arm64-fixes tree.
The fbdev tree lost its build failure.
The net-next tree still had its build failure for which I reverted a commit.
It also gained a conflict against the net tree.
The mlx5-next tree gained conflicts
Em Wed, Jun 26, 2019 at 09:49:06PM -0400, Theodore Ts'o escreveu:
> On Wed, Jun 26, 2019 at 06:16:13PM -0300, Arnaldo Carvalho de Melo wrote:
> > The v1.14 release of pahole and its friends is out, available at
> > the usual places
>
> Looks like you forgot to update the version number.
Sigh,
It seems like this is the xlog_alloc_log error path. We didn't
really change anything in the circular ioclogs queue handling, so
maybe thish has been there before, but xfs_buf wasn't wired up to
kasan to catch it?
Either way I suspect the right thing to do is to replace the list
with an array bas
Enable GPIO_DAVINCI and related configs for TI K3 AM6 platforms.
Signed-off-by: Keerthy
---
Changes in v2:
* Enabling configs in Kconfig.platforms file instead of defconfig.
* Removed GPIO_DEBUG config.
arch/arm64/Kconfig.platforms | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arc
On Wed, Jun 26, 2019 at 11:37 PM Jeremy Linton wrote:
>
> The ACPI specification implies that the IDENTICAL flag should be
> set on all non leaf nodes where the children are identical.
> This means that we need to be searching for the last node with
> the identical flag set rather than the first o
On Wed, Jun 26, 2019 at 11:37 PM Jeremy Linton wrote:
>
> ACPI 6.3 adds a flag to indicate that child nodes are all
> identical cores. This is useful to authoritatively determine
> if a set of (possibly offline) cores are identical or not.
>
> Since the flag doesn't give us a unique id we can gene
On Jun 26 08:28, Linus Torvalds wrote:
> This is not a comment on the patch series itself, it is a comment on the
> emails.
>
> Your email is mis-configured and ends up all being marked as spam for
> me, because you go through the wrong smtp server (or maybe your smtp
> server itself is miconfigu
On Wed, Jun 26, 2019 at 4:54 AM Nicolas Boichat wrote:
> During suspend/resume, mtk_eint_mask may be called while
> wake_mask is active. For example, this happens if a wake-source
> with an active interrupt handler wakes the system:
> irq/pm.c:irq_pm_check_wakeup would disable the interrupt, so
>
With -mprofile-kernel, gcc emits 'mflr r0', followed by 'bl _mcount' to
enable function tracing and profiling. So far, with dynamic ftrace, we
used to only patch out the branch to _mcount(). However, mflr is
executed by the branch unit that can only execute one per cycle on
POWER9 and shared with b
While over-riding ftrace_replace_code(), we still want to reuse the
existing __ftrace_replace_code() function. Rename the function and
make it available for other kernel code.
Signed-off-by: Naveen N. Rao
---
include/linux/ftrace.h | 1 +
kernel/trace/ftrace.c | 8
2 files changed, 5 i
Ftrace location could include more than a single instruction in case of
some architectures (powerpc64, for now). In this case, kprobe is
permitted on any of those instructions, and uses ftrace infrastructure
for functioning.
However, [dis]arm_kprobe_ftrace() uses the kprobe address when setting
up
Now that we are patching the preceding 'mflr r0' instruction with
-mprofile-kernel, we need to update ftrace_location() to recognise that
as being part of ftrace.
To do this, we introduce FTRACE_IP_EXTENSION to denote the length (in
bytes) of the mcount caller. By default, this is set to 0. For po
In commit a0572f687fb3c ("ftrace: Allow ftrace_replace_code() to be
schedulable), the generic ftrace_replace_code() function was modified to
accept a flags argument in place of a single 'enable' flag. However, the
x86 version of this function was not updated. Fix the same.
Fixes: a0572f687fb3c ("f
Changes since v1
(https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=114556):
- Patches 1,2,3 and 6: No changes
- Patch 4: Add smp_call_function() to flush icache on all cpus after
patching in the 'mflr r0' instruction.
- Patch 5: Changes as per Steven Rostedt's suggestions.
- Patch
Since ftrace_replace_code() is a __weak function and can be overridden,
we need to expose the flags that can be set. So, move the flags enum to
the header file.
Reviewed-by: Steven Rostedt (VMware)
Signed-off-by: Naveen N. Rao
---
include/linux/ftrace.h | 5 +
kernel/trace/ftrace.c | 5 ---
With KPROBES_ON_FTRACE, kprobe is allowed to be inserted on instructions
that branch to _mcount (referred to as ftrace location). With
-mprofile-kernel, we now include the preceding 'mflr r0' as being part
of the ftrace location.
However, by default, probing on an instruction that is not actually
/kernel/git/brauner/linux
tags/for-linus-20190627
for you to fetch changes up to 30d158b143b6575261ab610ae7b1b4f7fe3830b3:
proc: remove useless d_is_dir() check (2019-06-27 12:25:09 +0200)
/* Remove check for pidfd == 0 with CLONE_PIDFD */
Userspace tools and libraries such as strace or glibc need
On Tue, Jun 25, 2019 at 02:52:36PM +0530, Vidya Sagar wrote:
> Add an API to group all the tasks to be done to de-initialize host which
> can then be called by any DesignWare core based driver implementations
> while adding .remove() support in their respective drivers.
>
> Signed-off-by: Vidya Sa
On Thu, Jun 27, 2019 at 10:24:07AM +0100, Charles Keepax wrote:
> Use the available IRQ helper functions, most of the functions have
> additional helpful side affects like configuring the trigger type of the
> IRQ.
>
> Reviewed-by: Andy Shevchenko
> Signed-off-by: Charles Keepax
Reviewed-by: Mi
On Thu, Jun 27, 2019 at 4:32 AM Joel Stanley wrote:
> I think we can use this as an opportunity to drop the unused g4-scu
> compatible from the bindings. Similarly for the g5.
>
> Acked-by: Joel Stanley
I assume I should wait for a new version of the patches that does
this?
Yours,
Linus Wallei
On Thu, Jun 27, 2019 at 10:24:08AM +0100, Charles Keepax wrote:
> In preparation for future refactoring factor out the fetch of the IRQ
> into its own helper function. Whilst we are at it update the handling
> to return the actual error code returned from acpi_dev_get_resources
> as well.
>
> Revi
On Thu, Jun 27, 2019 at 11:57:36AM +0100, Vincenzo Frascino wrote:
> Hi Dave,
>
> Overall, I want to thank you for bringing out the topic. It helped me to
> question some decisions and make sure that we have no holes left in
> the approach.
Fair enough.
This is really just a nasty compiler corne
Naveen N. Rao wrote:
In commit a0572f687fb3c ("ftrace: Allow ftrace_replace_code() to be
schedulable), the generic ftrace_replace_code() function was modified to
accept a flags argument in place of a single 'enable' flag. However, the
x86 version of this function was not updated. Fix the same.
F
On Thu, Jun 27, 2019 at 10:24:09AM +0100, Charles Keepax wrote:
> Bring the ACPI path in sync with the device tree path and handle all the
> IRQ fetching at probe time. This leaves the only IRQ handling at device
> registration time being that which is passed directly through the board
> info as ei
On Thu, Jun 27, 2019 at 10:24:10AM +0100, Charles Keepax wrote:
> It makes sense to contain all the ACPI IRQ handling in a single helper
> function.
>
> Reviewed-by: Andy Shevchenko
> Signed-off-by: Charles Keepax
Reviewed-by: Mika Westerberg
On 26-06-19 23:24, Stephen Boyd wrote:
> Sorry, I'm getting through my inbox pile and saw this one.
>
> Quoting Mike Looijmans (2019-04-30 22:46:55)
>> On 30-04-19 02:17, Stephen Boyd wrote:
>>>
>>> Why can't that driver call clk_prepare_enable()? Is there some sort of
>>> assumption that this clk
* Faiz Abbas [190619 03:25]:
> If UHS speed modes are enabled, a compatible SD card switches down to
> 1.8V during enumeration. If after this a software reboot/crash takes
> place and on-chip ROM tries to enumerate the SD card, the difference in
> IO voltages (host @ 3.3V and card @ 1.8V) may end
If tracing_err_log_open() call seq_open(), allocated memory is not freed.
kmemleak report:
unreferenced object 0x92c0781d1100 (size 128):
comm "tail", pid 15116, jiffies 4295163855 (age 22.704s)
hex dump (first 32 bytes):
00 f0 08 e5 c0 92 ff ff 00 10 00 00 00 00 00 00 ..
When a process expects no accesses to a certain memory range
for a long time, it could hint kernel that the pages can be
reclaimed instantly but data should be preserved for future use.
This could reduce workingset eviction so it ends up increasing
performance.
This patch introduces the new MADV_P
When a process expects no accesses to a certain memory range, it could
give a hint to kernel that the pages can be reclaimed when memory pressure
happens but data should be preserved for future use. This could reduce
workingset eviction so it ends up increasing performance.
This patch introduces
The local variable references in shrink_page_list is PAGEREF_RECLAIM_CLEAN
as default. It is for preventing to reclaim dirty pages when CMA try to
migrate pages. Strictly speaking, we don't need it because CMA didn't allow
to write out by .may_writepage = 0 in reclaim_clean_pages_from_list.
Moreov
This patch is part of previous series:
https://lore.kernel.org/lkml/20190531064313.193437-1-minc...@kernel.org/T/#u
Originally, it was created for external madvise hinting feature.
https://lkml.org/lkml/2019/5/31/463
Michal wanted to separte the discussion from external hinting interface
so this p
Now, there are common part among MADV_COLD|PAGEOUT|FREE to reset
access/dirty bit resetting or split the THP page to handle part
of subpages in the THP page. This patch factor out the common part.
Signed-off-by: Minchan Kim
---
include/linux/huge_mm.h | 3 -
mm/huge_memory.c| 74 -
The isolate counting is pecpu counter so it would be not huge gain
to work them by batch. Rather than complicating to make them batch,
let's make it more stright-foward via adding the counting logic
into [isolate|putback]_lru_page API.
* v1
* fix accounting bug - Hillf
Link: http://lkml.kernel.o
On 6/27/19 12:27 PM, Dave Martin wrote:
> On Thu, Jun 27, 2019 at 11:57:36AM +0100, Vincenzo Frascino wrote:
>> Hi Dave,
>>
>> Overall, I want to thank you for bringing out the topic. It helped me to
>> question some decisions and make sure that we have no holes left in
>> the approach.
>
> Fair e
Hello Thomas!
On 24/06/2019 11:40, Thomas Gleixner wrote:
>>> The alternative solution for this is what Vincenzo has in his unified VDSO
>>> patch series:
>>>
>>> https://lkml.kernel.org/r/20190621095252.32307-1-vincenzo.frasc...@arm.com
>>>
>>> It leaves the data struct unmodified and has a sep
101 - 200 of 1043 matches
Mail list logo
