Add Alok Chauhan and myself as maintainers for Qualcomm GENI I2C master
controller driver.
Signed-off-by: Karthikeyan Ramasubramanian
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32fbc6f..6e33b29 100644
--- a/MAINTAINERS
+++ b/MAINTA
This bus driver supports the GENI based i2c hardware controller in the
Qualcomm SOCs. The Qualcomm Generic Interface (GENI) is a programmable
module supporting a wide range of serial interfaces including I2C. The
driver supports FIFO mode and DMA mode of transfer and switches modes
dynamically depe
On Mon, Jul 30, 2018 at 10:32:10AM +0200, Lukas Wunner wrote:
> On Fri, Jul 27, 2018 at 03:26:19PM -0500, Bjorn Helgaas wrote:
> > The question is where those sysfs files should be. Currently they are
> > associated with the device at the *upstream* end of the link. In the
> > example above, they
On Mon 2018-07-30 16:33:15, David Howells wrote:
> Pavel Machek wrote:
>
> > Well, I guess errors should have numbers, and catalog explaining what
> > error means what. That way userspace can translate, and it is what we
> > do with errno.
> >
> > I believe numbers are best. If you hate numbers,
Xunlei Pang writes:
> Hi Cong,
>
> On 7/28/18 8:24 AM, Cong Wang wrote:
>> Each time we sync cfs_rq->runtime_expires with cfs_b->runtime_expires,
>> we should sync its ->expires_seq too. However it is missing
>> for distribute_cfs_runtime(), especially the slack timer call path.
>
> I don't think
On Mon, Jul 30, 2018 at 6:01 AM Kirill A. Shutemov wrote:
>
> I think I missed vma_set_anonymous() somewhere, but I fail to see where.
Honestly, by now we just need to revert that commit.
It's not even clear that it was a good idea to begin with. The rest of
the commits were cleanups, this one w
On Mon, Jul 30, 2018 at 05:26:45PM +0200, Hans de Goede wrote:
> Hi,
>
> On 30-07-18 17:22, Tejun Heo wrote:
> >On Mon, Jul 30, 2018 at 08:15:47AM -0700, Srinivas Pandruvada wrote:
> >>Hi Tejan,
> >>
> >>On Mon, 2018-07-02 at 12:01 -0700, Srinivas Pandruvada wrote:
> >>>Some minor fixes to be able
Commit-ID: 684ad537abff987886d63fb3c573eeca40d7f2db
Gitweb: https://git.kernel.org/tip/684ad537abff987886d63fb3c573eeca40d7f2db
Author: Pavel Tatashin
AuthorDate: Wed, 25 Jul 2018 16:00:18 -0400
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:32:29 +0200
timekeeping: Prevent
Hi Quentin,
On Wed, Jul 25, 2018 at 02:26:20PM +0200, Quentin Schulz wrote:
> The GPIO controller also serves as an interrupt controller for events
> on the GPIO it handles.
>
> An interrupt occurs whenever a GPIO line has changed.
>
> Signed-off-by: Quentin Schulz
> ---
> arch/mips/boot/dts/m
Commit-ID: bd9f943e5d2a42d864f9692477a25034c9d47dcc
Gitweb: https://git.kernel.org/tip/bd9f943e5d2a42d864f9692477a25034c9d47dcc
Author: Pavel Tatashin
AuthorDate: Mon, 30 Jul 2018 09:52:52 -0400
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:33:35 +0200
sched/clock: Disable
Commit-ID: 1088c6eef261939bda8346ec35b513790a2111d5
Gitweb: https://git.kernel.org/tip/1088c6eef261939bda8346ec35b513790a2111d5
Author: Dou Liyang
AuthorDate: Mon, 30 Jul 2018 15:54:21 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:33:35 +0200
x86/kvmclock: Mark kvm_g
On 2018-07-30 16:07, Mark Brown wrote:
On Mon, Jul 30, 2018 at 03:04:46PM +0100, Jon Hunter wrote:
On 30/07/18 11:18, Mark Brown wrote:
> DSP modes only care about the rising edge of the LRCLK, the pulse can be
> any width without causing interoperability problems.
OK, thanks I was not a
On Sat, 2018-07-28 at 14:18 -0700, David Miller wrote:
> From: Dmitry Safonov
> Date: Sat, 28 Jul 2018 17:26:55 +0100
>
> > Well, I think, I'll rework my patches set according to critics and
> > separate compat xfrm layer. I've already a selftest to check that
> 32/64
> > bit xfrm works - so the
On Mon 2018-07-30 11:40:35, Johannes Weiner wrote:
> On Sat, Jul 28, 2018 at 12:01:23AM +0200, Pavel Machek wrote:
> > > How do you use this feature?
> > >
> > > A kernel with CONFIG_PSI=y will create a /proc/pressure directory with
> > > 3 files: cpu, memory, and io. If using cgroup2, c
Commit-ID: 608008a45798fe9e2aee04f99b5270ea57c1376f
Gitweb: https://git.kernel.org/tip/608008a45798fe9e2aee04f99b5270ea57c1376f
Author: Dou Liyang
AuthorDate: Mon, 30 Jul 2018 15:54:20 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:33:35 +0200
x86/tsc: Consolidate ini
On 07/30/2018 01:02 PM, Boris Ostrovsky wrote:
> On 07/30/2018 05:02 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Today's linux-next merge of the akpm-current tree got a conflict in:
>>
>> drivers/xen/gntdev.c
>>
>> between commit:
>>
>> 1d3145675538 ("xen/gntdev: Make private routines/structur
Commit-ID: 5db1b1e1ee34871b1965b3f890e3ccbdb185fa52
Gitweb: https://git.kernel.org/tip/5db1b1e1ee34871b1965b3f890e3ccbdb185fa52
Author: zhong jiang
AuthorDate: Mon, 30 Jul 2018 21:44:33 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:46:03 +0200
x86/boot/KASLR: Make lo
Linus,
Please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
# HEAD: c0dc373a780f4ec63e45a573b9551763abd8cd1a locking/pvqspinlock/x86:
Use LOCK_PREFIX in __pv_queued_spin_unlock() assembly code
A
On systems where a runtime microcode update has occurred the microcode
version output in a MCE log record is wrong because
boot_cpu_data.microcode is not updated during runtime.
Update boot_cpu_data.microcode when the BSP's microcode is updated.
Fixes: fa94d0c6e0f3 ("x86/MCE: Save microcode revis
Hello,
On Mon, Jul 30, 2018 at 07:39:40PM +0200, Pavel Machek wrote:
> > I'd rather have the internal config symbol match the naming scheme in
> > the code, where psi is a shorter, unique token as copmared to e.g.
> > pressure, press, prsr, etc.
>
> I'd do "pressure", really. Yes, psi is shorter,
On 07/30/2018 01:49 PM, Prarit Bhargava wrote:
> On systems where a runtime microcode update has occurred the microcode
> version output in a MCE log record is wrong because
> boot_cpu_data.microcode is not updated during runtime.
>
> Update boot_cpu_data.microcode when the BSP's microcode is u
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 7f635ff187ab6be0b350b3ec06791e376af238ab perf/core: Fix crash when
using HW tracing kernel filters
Misc fixes:
- AMD IBS data corr
On 07/30/2018 10:51 AM, Tejun Heo wrote:
> Hello,
>
> On Mon, Jul 30, 2018 at 07:39:40PM +0200, Pavel Machek wrote:
>>> I'd rather have the internal config symbol match the naming scheme in
>>> the code, where psi is a shorter, unique token as copmared to e.g.
>>> pressure, press, prsr, etc.
>>
>>
On Mon, Jul 30, 2018 at 10:30 AM Pavel Machek wrote:
>
> Still userland needs a way to understand the errors.
Not really.
We don't internationalize kernel strings. We never have. Yes, some
people tried to do some database of kernel messages for translation
purposes, but I absolutely refused to m
On Sun, Jul 29, 2018 at 10:29 PM Xunlei Pang wrote:
>
> Hi Cong,
>
> On 7/28/18 8:24 AM, Cong Wang wrote:
> > Each time we sync cfs_rq->runtime_expires with cfs_b->runtime_expires,
> > we should sync its ->expires_seq too. However it is missing
> > for distribute_cfs_runtime(), especially the slac
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: f3d133ee0a17d5694c6f21873eec9863e11fa423 sched/rt: Restore
rt_runtime after disabling RT_RUNTIME_SHARE
Misc fixes:
- a deadline
On 07/26/2018 04:14 AM, Jiri Kosina wrote:
> From: Jiri Kosina
>
> The article "Spectre Returns! Speculation Attacks using the Return Stack
> Buffer" [1] describes two new (sub-)variants of spectrev2-like attack,
> making use solely of the RSB contents even on CPUs that don't fallback to
> BTB
Hi Todd,
On Sun, Jul 29, 2018 at 12:37 PM Todd Poynor wrote:
> @@ -1064,7 +1067,8 @@ static int gasket_open(struct inode *inode, struct file
> *filp)
> char task_name[TASK_COMM_LEN];
> struct gasket_cdev_info *dev_info =
> container_of(inode->i_cdev, struct gasket_cde
Commit-ID: 24cfd8ca1d28331b9dad3b88d1958c976b2cfab6
Gitweb: https://git.kernel.org/tip/24cfd8ca1d28331b9dad3b88d1958c976b2cfab6
Author: Dou Liyang
AuthorDate: Mon, 30 Jul 2018 15:59:47 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:53:58 +0200
x86/platform/UV: Mark me
On Mon 2018-07-30 10:51:20, Tejun Heo wrote:
> Hello,
>
> On Mon, Jul 30, 2018 at 07:39:40PM +0200, Pavel Machek wrote:
> > > I'd rather have the internal config symbol match the naming scheme in
> > > the code, where psi is a shorter, unique token as copmared to e.g.
> > > pressure, press, prsr,
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 92a4728608a8fd228c572bc8ff50dd98aa0ddf2a x86/boot: Fix if_changed
build flip/flop bug
Misc fixes:
- a build race fix
- a Xen entry
On 07/25/2018 10:11 AM, Josh Poimboeuf wrote:
> On Wed, Jul 25, 2018 at 03:50:44PM +0200, Jiri Kosina wrote:
>> On Wed, 25 Jul 2018, Josh Poimboeuf wrote:
>>
The article "Spectre Returns! Speculation Attacks using the Return Stack
Buffer" [1] describes two new (sub-)variants of spectrev2-
Commit-ID: 843c408905010fbc44a564d2de6a3cd68d986abf
Gitweb: https://git.kernel.org/tip/843c408905010fbc44a564d2de6a3cd68d986abf
Author: Yi Wang
AuthorDate: Fri, 27 Jul 2018 14:15:03 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 19:56:30 +0200
x86/apic: Trivial coding st
This is a tiny implementation of cgroup-aware OOM killer,
which adds an ability to kill a cgroup as a single unit
and so guarantee the integrity of the workload.
Although it has only a limited functionality in comparison
to what now resides in the mm tree (it doesn't change
the victim task selecti
oom_kill_process() consists of two logical parts: the first one is
responsible for considering task's children as a potential victim and
printing the debug information. The second half is responsible for
sending SIGKILL to all tasks sharing the mm struct with the given victim.
This commit splits
Introduce the mem_cgroup_put() helper, which helps to eliminate guarding
memcg css release with "#ifdef CONFIG_MEMCG" in multiple places.
Link: http://lkml.kernel.org/r/20180623000600.5818-2-g...@fb.com
Signed-off-by: Roman Gushchin
Reviewed-by: Shakeel Butt
Reviewed-by: Andrew Morton
Cc: Shake
For some workloads an intervention from the OOM killer
can be painful. Killing a random task can bring
the workload into an inconsistent state.
Historically, there are two common solutions for this
problem:
1) enabling panic_on_oom,
2) using a userspace daemon to monitor OOMs and kill
all outst
Hi Dmitry,
On Mon, Jul 30, 2018 at 10:57 AM Dmitry Torokhov wrote:
>
> Hi Todd,
>
> On Sun, Jul 29, 2018 at 12:37 PM Todd Poynor wrote:
> > @@ -1064,7 +1067,8 @@ static int gasket_open(struct inode *inode, struct
> > file *filp)
> > char task_name[TASK_COMM_LEN];
> > struct gaske
Hello,
On Mon, Jul 30, 2018 at 10:54:05AM -0700, Randy Dunlap wrote:
> I'd say he's trying to make something that is readable and easier to
> understand for users.
Sure, it's perfectly fine to make those suggestions and discuss but
the counter points have already been discussed (e.g. PSI is a kno
Hi Sean,
> All suggestions seem reasonable for me in order to make code style aligned
> with the other drivers and code better to read,
> and it looks like no any big problem, so I'll start to work on the next
> version immediately.
no rush, but if you can get this back to me quickly, we might
On Mon, Jul 30, 2018 at 07:59:36PM +0200, Pavel Machek wrote:
> Its true I have no interest in psi. But I'm trying to use same kernel
> you are trying to "improve" and I was confused enough by seing
> "CONFIG_PSI". And yes, my association was "pounds per square inch" and
> "what is it doing here".
On Mon, Jul 30, 2018 at 04:31:04PM +0200, Pavel Machek wrote:
> Well, I guess errors should have numbers, and catalog explaining what
> error means what. That way userspace can translate, and it is what we
> do with errno.
>
> I believe numbers are best. If you hate numbers, you can still use
> st
'ac->ac_g_ex.fe_len' is a user-controlled value which is used in the
derivation of 'ac->ac_2order'. 'ac->ac_2order', in turn, is used to
index arrays which makes it a potential spectre gadget. Fix this by
sanitizing the value assigned to 'ac->ac2_order'. This covers the
following accesses found wi
Hello,
syzbot found the following crash on:
HEAD commit:acb1872577b3 Linux 4.18-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ab932c40
kernel config: https://syzkaller.appspot.com/x/.config?x=2dc0cd7c2eefb46f
dashboard link: https://syzkaller.a
Hello,
syzbot found the following crash on:
HEAD commit:acb1872577b3 Linux 4.18-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14eb932c40
kernel config: https://syzkaller.appspot.com/x/.config?x=2dc0cd7c2eefb46f
dashboard link: https://syzkaller.a
On Mon 2018-07-30 10:54:19, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 10:30 AM Pavel Machek wrote:
> >
> > Still userland needs a way to understand the errors.
>
> Not really.
>
> We don't internationalize kernel strings. We never have. Yes, some
> people tried to do some database of kerne
On Mon 2018-07-30 11:08:42, Matthew Wilcox wrote:
> On Mon, Jul 30, 2018 at 04:31:04PM +0200, Pavel Machek wrote:
> > Well, I guess errors should have numbers, and catalog explaining what
> > error means what. That way userspace can translate, and it is what we
> > do with errno.
> >
> > I believe
On Mon, Jul 30, 2018 at 11:08 AM Matthew Wilcox wrote:
>
> Have you looked at how gettext() works? It uses the english text as
> a search string and replaces it with the localised string. This is
> a very common design!
I absolutely refuse to have anything to do with gettext in the kernel.
get
arm64 uses the full KBUILD_CFLAGS for building libstub as opposed
to x86 which doesn't. This means that x86 doesn't pick up
the gcc-plugins. We need to disable the stackleak plugin but
doing this unconditionally breaks x86 build since it doesn't
have any plugins. Switch to disabling the stackleak p
Hey Jeremy,
I think you are also going to be changing the 1/3 patch from the
original patch series that this was part of. That's correct, right?
It would be easier for me if you could simply make all of the
revisions you plan to make for the patch series, and then upload a
full v2 of the entire
On Fri, Jul 27, 2018 at 07:43:16PM +0530, Balakrishna Godavarthi wrote:
> From: Balakrishna Godavarthi
>
> Redefinition of qca_uart_setup will help future Qualcomm Bluetooth
> SoC, to use the same function instead of duplicating the function.
> Added new arguments soc_type and soc_ver to the func
On Mon, Jul 30, 2018 at 11:18:53AM -0700, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 11:08 AM Matthew Wilcox wrote:
> >
> > Have you looked at how gettext() works? It uses the english text as
> > a search string and replaces it with the localised string. This is
> > a very common design!
>
On Mon, Jul 30, 2018 at 10:06:20AM -0700, Nick Desaulniers wrote:
> Starting with Clang-7.0, _THIS_IP_ generates -Wreturn-stack-address
> warnings for almost every translation unit. In general, I'd prefer to
> leave this on (returning the address of a stack allocated variable is in
> general a bad
- On Jul 28, 2018, at 10:13 AM, Pavel Machek pa...@ucw.cz wrote:
> Hi!
>
>> Documentation-wise, I have posted a rseq man page rfc here:
>>
>> https://lkml.kernel.org/r/20180616195803.29877-1-mathieu.desnoy...@efficios.com
>>
>> comments are welcome!
>
> Thanks for pointer.
>
> +Restartabl
On Mon, Jul 30, 2018 at 11:11:38AM +0200, Greg KH wrote:
> On Sun, Jul 29, 2018 at 10:07:33PM +0100, John Whitmore wrote:
> > Remove the typedef of the structure cmpk_txfb_t. This clears the
> > checkpatch issue with defining new types.
> >
> > Additionally the type is renamed from cmpk_txfb_t to
Hi Ted,
On 07/30/2018 02:36 PM, Theodore Y. Ts'o wrote:
> Hey Jeremy,
>
> I think you are also going to be changing the 1/3 patch from the
> original patch series that this was part of. That's correct, right?
>
> It would be easier for me if you could simply make all of the
> revisions you plan
On Mon, Jul 16, 2018 at 05:20:19PM -0400, Don Zickus wrote:
> On Fri, Jul 13, 2018 at 05:11:58PM -0700, Joe Perches wrote:
> > On Fri, 2018-07-13 at 14:51 -0400, Don Zickus wrote:
> > > On Fri, Jul 06, 2018 at 03:14:28PM -0700, Joe Perches wrote:
> > > > On Fri, 2018-07-06 at 15:09 -0700, Joe Perch
Mel Gorman writes:
> On Sat, Jul 28, 2018 at 01:21:51PM -0700, Francisco Jerez wrote:
>> >> Please revert this series, it led to significant energy usage and
>> >> graphics performance regressions [1]. The reasons are roughly the ones
>> >> we discussed by e-mail off-list last April: This causes
On Mon 30-07-18 08:44:24, Tejun Heo wrote:
> Hello,
>
> On Tue, Jul 31, 2018 at 12:25:04AM +0900, Tetsuo Handa wrote:
> > WQ_MEM_RECLAIM guarantees that "struct task_struct" is preallocated. But
> > WQ_MEM_RECLAIM does not guarantee that the pending work is started as soon
> > as an item was queue
On Mon, Jul 30, 2018 at 06:07:47PM +, Jeremy Cline wrote:
> 'ac->ac_g_ex.fe_len' is a user-controlled value which is used in the
> derivation of 'ac->ac_2order'. 'ac->ac_2order', in turn, is used to
> index arrays which makes it a potential spectre gadget. Fix this by
> sanitizing the value ass
On 2018-07-29 03:52, Rafael J. Wysocki wrote:
On Sat, Jul 28, 2018 at 5:56 AM, Saravana Kannan
wrote:
Many CPU architectures have caches that can scale independent of the
CPUs.
Frequency scaling of the caches is necessary to make sure the cache is
not
a performance bottleneck that leads to poo
On Mon, Jul 30, 2018 at 11:38 AM Matthew Wilcox wrote:
>
> I wasn't proposing putting gettext in the kernel. I was reacting to
> Pavel saying "You can't return English strings from the kernel, you have
> to translate numbers into any language's strings".
The problem with gettext() is that if you
On Mon, 30 Jul 2018 17:02:05 +0300
Mircea Caprioru wrote:
> The AD5770R is a 6-channel, 14-bit resolution, low noise, programmable
> current output digital-to-analog converter (DAC) for photonics control
> applications.
>
> It contains five 14-bit resolution current sourcing DAC channels and one
Hi!
> > Thanks for pointer.
> >
> > +Restartable sequences are atomic with respect to preemption (making
> > it
> > +atomic with respect to other threads running on the same CPU), as
> > well
> > +as signal delivery (user-space execution contexts nested over the
> > same
> > +thread).
> >
> > So
Hi Paul,
Just want to know what's your plan on stable branches regarding this issue.
Do you intend to backport the ->nocb_lock? Or are you going with just the
memory barrier change?
Thanks,
David
From: Paul E. McKenney
Sent: Saturday, July 28, 2018 1:29 AM
To: David Chen
Cc: linux-kernel@vger.
On Mon, 30 Jul 2018 13:59:18 +0100
Colin King wrote:
> From: Colin Ian King
>
> The current check on val always results in true and so the
> call to sii1133_update_adcsens never gets called. Fix this check
> so it returns with -EINVAL only when val is not zero and not one.
>
> Detected by Cove
Reducing the verbosity level to debug for people that are interested in
debugging watchdog issues.
[0.152492] NMI watchdog: Perf event create on CPU 0 failed with -2
[0.156002] NMI watchdog: Perf NMI watchdog permanently disabled
Signed-off-by: Sinan Kaya
---
kernel/watchdog_hld.c | 4 +
> +Response contents:
> +
> +ETHA_SETTINGS_LINK (u32) link state
> + [ETHA_SETTINGS_LINK]= { .type = NLA_FLAG },
Is this correct?
The link is either up or down. So a u32 seems a bit big.
Andrew
On Mon, Jul 30, 2018 at 11:31 AM, Laura Abbott wrote:
> arm64 uses the full KBUILD_CFLAGS for building libstub as opposed
> to x86 which doesn't. This means that x86 doesn't pick up
> the gcc-plugins. We need to disable the stackleak plugin but
> doing this unconditionally breaks x86 build since i
This change has been posted several times with some concerns about the
changelog. Originally I thought it is more of a "nice to have" thing
rather than a bug fix, later Tetsuo has taken over it but the changelog
was not really comprehensible so I reworded it. Let's see if this is
better.
>From 9b
On Sat, Jul 28, 2018 at 4:10 PM, Paolo Bonzini wrote:
> The shadow vmcs12 cannot be flushed on KVM_GET_NESTED_STATE,
> because at that point guest memory is assumed by userspace to
> be immutable. Capture the cache in vmx_get_nested_state, adding
> another page at the end if there is an active sh
On Mon, Jul 30, 2018 at 10:56:55AM -0700, Tim Chen wrote:
> On 07/26/2018 04:14 AM, Jiri Kosina wrote:
> > From: Jiri Kosina
> >
> > The article "Spectre Returns! Speculation Attacks using the Return Stack
> > Buffer" [1] describes two new (sub-)variants of spectrev2-like attack,
> > making use
Hello, Michal.
On Mon, Jul 30, 2018 at 08:51:10PM +0200, Michal Hocko wrote:
> > Yeah, workqueue can choke on things like that and kthread indefinitely
> > busy looping doesn't do anybody any good.
>
> Yeah, I do agree. But this is much easier said than done ;) Sure
> we have that hack that does
On Mon, 2018-07-30 at 18:26 +0200, Peter Zijlstra wrote:
> On Mon, Jul 30, 2018 at 10:30:11AM -0400, Rik van Riel wrote:
>
> > > What happened to the rework I did there? That not only avoided
> > > fiddling
> > > with active_mm, but also avoids grab/drop cycles for the other
> > > architectures wh
On Mon, Jul 30, 2018 at 10:58:13AM +0200, Peter Zijlstra wrote:
> On Thu, Jul 26, 2018 at 04:50:44PM -0700, Joel Fernandes wrote:
> > One note, I have to check for lockdep recursion in the code that calls
> > the trace events API and bail out if we're in lockdep recursion
> > protection to prevent
From: Sai Praneeth
Some future Intel processors may support "Enhanced IBRS" which is an
"always on" mode i.e. IBRS bit in SPEC_CTRL MSR is enabled once and
never disabled.
[With enhanced IBRS, the predicted targets of indirect branches executed
cannot be controlled by software that was executed
On Mon, Jul 30, 2018 at 10:59:59AM +0200, Peter Zijlstra wrote:
>
>
> Aside from the Changelog nit in #3 this looks good to me.
>
> Acked-by: Peter Zijlstra (Intel)
Thanks!
Updated patch is below with changelog changes (nit corrected and add Ack).
- Joel
-8<-
From: "Joel Fe
On Sat, Jul 28, 2018 at 4:10 PM, Paolo Bonzini wrote:
> If the vCPU enters system management mode while running a nested guest,
> RSM starts processing the vmentry while still in SMM. In that case,
> however, the pages pointed to by the vmcs12 might be incorrectly
> loaded from SMRAM. To avoid t
On Mon, Jul 30, 2018 at 12:09:47PM -0700, Sinan Kaya wrote:
> Reducing the verbosity level to debug for people that are interested in
> debugging watchdog issues.
>
> [0.152492] NMI watchdog: Perf event create on CPU 0 failed with -2
> [0.156002] NMI watchdog: Perf NMI watchdog permanently
RCU's rcu_iw irq-work (rcu_iw_handler()) acquires the raw spinlock
rnp->lock without disabling interrupts. The lock is held normally with
disabled interrupts for a short time.
Mark irq-work as IRQ_WORK_HARD_IRQ so it is invoked in IRQ context like
on !RT.
Reported-by: John Ogness
Signed-off-by: S
On Mon, Jul 30, 2018 at 12:15 PM, Rik van Riel wrote:
> On Mon, 2018-07-30 at 18:26 +0200, Peter Zijlstra wrote:
>> On Mon, Jul 30, 2018 at 10:30:11AM -0400, Rik van Riel wrote:
>>
>> > > What happened to the rework I did there? That not only avoided
>> > > fiddling
>> > > with active_mm, but also
On Mon, Jul 30, 2018 at 07:08:55PM +, David Chen wrote:
> Hi Paul,
>
> Just want to know what's your plan on stable branches regarding this issue.
> Do you intend to backport the ->nocb_lock? Or are you going with just the
> memory barrier change?
That depends on you. I am not going to submi
On Mon, 2018-07-30 at 12:17 +0200, Oleg Nesterov wrote:
> On 07/30, Jürg Billeter wrote:
> >
> > This is required for job control in a shell that uses CLONE_NEWPID for
> > child processes.
>
> Could you explain in more details?
The SIGNAL_UNKILLABLE flag, which is implicitly set for tasks cloned
- On Jul 30, 2018, at 3:07 PM, Pavel Machek pa...@ucw.cz wrote:
> Hi!
>
>> > Thanks for pointer.
>> >
>> > +Restartable sequences are atomic with respect to preemption (making
>> > it
>> > +atomic with respect to other threads running on the same CPU), as
>> > well
>> > +as signal delivery (
Commit-ID: d018031f562b9c2eff038969ab1955a370c52d8f
Gitweb: https://git.kernel.org/tip/d018031f562b9c2eff038969ab1955a370c52d8f
Author: Mukesh Ojha
AuthorDate: Tue, 24 Jul 2018 20:17:48 +0530
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 21:30:52 +0200
cpu/hotplug: Clarify CP
On 2018-07-24 05:25, Quentin Perret wrote:
Schedutil aggregates the PELT signals of CFS, RT, DL and IRQ in order
to decide which frequency to request. Energy Aware Scheduling (EAS)
needs to be able to predict those requests to assess the energy impact
of scheduling decisions. However, the PELT si
On Mon, 2018-07-30 at 12:30 -0700, Andy Lutomirski wrote:
> On Mon, Jul 30, 2018 at 12:15 PM, Rik van Riel
> wrote:
> > On Mon, 2018-07-30 at 18:26 +0200, Peter Zijlstra wrote:
> > > On Mon, Jul 30, 2018 at 10:30:11AM -0400, Rik van Riel wrote:
> > >
> > > > > What happened to the rework I did th
On Mon, Jul 30, 2018 at 02:46:59PM -0400, Jeremy Cline wrote:
> I dropped patch 1/3 and 2/3 from the original series because they can
> both be covered by some sanitation in fs/quota/quota.c, so the this is
> only patch from the v1 series that should be applied.
>
> Sorry for not being more clear!
On Mon, 30 Jul 2018, Jürg Billeter wrote:
> On Mon, 2018-07-30 at 12:17 +0200, Oleg Nesterov wrote:
> > On 07/30, Jürg Billeter wrote:
> > >
> > > This is required for job control in a shell that uses CLONE_NEWPID for
> > > child processes.
> >
> > Could you explain in more details?
>
> The SIG
Commit-ID: fc91a3c4c27acdca0bc13af6fbb68c35cfd519f2
Gitweb: https://git.kernel.org/tip/fc91a3c4c27acdca0bc13af6fbb68c35cfd519f2
Author: Joel Fernandes (Google)
AuthorDate: Mon, 23 Jul 2018 14:25:31 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 30 Jul 2018 21:36:37 +0200
debugobject
early_init_amd() is called on all AMD processors, both 64 and 32 bit.
Presently 32 bit processors get the X86_FEATURE_VMMCALL feature set, which
they do not support. Add conditionals to restrict it to 64 bit processors.
Cc: Paolo Bonzini
Signed-off-by: Matthew Whitehead
---
arch/x86/kernel/cpu/
Hi Don,
On 7/30/2018 12:28 PM, Don Zickus wrote:
[0.152492] NMI watchdog: Perf event create on CPU 0 failed with -2
[0.156002] NMI watchdog: Perf NMI watchdog permanently disabled
Hi Sinan,
Any reason why? Usually when the 'perf event' fails, that indicates a
system problem. And most
On Mon, Jul 30, 2018 at 11:39 AM Nathan Chancellor
wrote:
>
> On Mon, Jul 30, 2018 at 10:06:20AM -0700, Nick Desaulniers wrote:
> > Starting with Clang-7.0, _THIS_IP_ generates -Wreturn-stack-address
> > warnings for almost every translation unit. In general, I'd prefer to
> > leave this on (retur
On Mon, Jul 30, 2018 at 12:36 PM, Rik van Riel wrote:
> On Mon, 2018-07-30 at 12:30 -0700, Andy Lutomirski wrote:
>> On Mon, Jul 30, 2018 at 12:15 PM, Rik van Riel
>> wrote:
>> > On Mon, 2018-07-30 at 18:26 +0200, Peter Zijlstra wrote:
>> > > On Mon, Jul 30, 2018 at 10:30:11AM -0400, Rik van Riel
On Mon, Jul 30, 2018 at 11:59:13AM -0700, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 11:38 AM Matthew Wilcox wrote:
> >
> > I wasn't proposing putting gettext in the kernel. I was reacting to
> > Pavel saying "You can't return English strings from the kernel, you have
> > to translate number
On Mon, 30 Jul 2018, Eduardo Valentin wrote:
> On Mon, Jul 30, 2018 at 10:53:54AM +0200, Peter Zijlstra wrote:
> > On Thu, Jul 26, 2018 at 08:56:56AM -0700, Eduardo Valentin wrote:
> > > System instability are seen during resume from hibernation when system
> > > is under heavy CPU load. This is du
On Mon, Jul 30, 2018 at 12:48:06PM -0700, Nick Desaulniers wrote:
> On Mon, Jul 30, 2018 at 11:39 AM Nathan Chancellor
> wrote:
> >
> > On Mon, Jul 30, 2018 at 10:06:20AM -0700, Nick Desaulniers wrote:
> > > Starting with Clang-7.0, _THIS_IP_ generates -Wreturn-stack-address
> > > warnings for alm
From: Thomas Petazzoni
Date: Tue, 24 Jul 2018 13:53:05 +0200
> This is necessary to be able to include when
> CONFIG_GENERIC_MSI_IRQ_DOMAIN is enabled. Without this, a build with
> CONFIG_GENERIC_MSI_IRQ_DOMAIN fails with:
...
> Signed-off-by: Thomas Petazzoni
Applied.
On Fri, Jul 27, 2018 at 11:15:28AM +0100, Suzuki K Poulose wrote:
> Coresight uses DT graph bindings to describe the connections of the
> components. However we have some undocumented usage of the bindings
> to describe some of the properties of the connections.
>
> The coresight driver needs to k
From: Thomas Petazzoni
Date: Tue, 24 Jul 2018 13:53:04 +0200
> The definitions in arch/sparc/include/asm/msi.h are only used in
> arch/sparc/mm/srmmu.c, so it makes sense to have them in the C file
> directly.
>
> In addition, having a custom arch/sparc/include/asm/msi.h prevents
> from using th
401 - 500 of 734 matches
Mail list logo
