On Wed, 24 Aug 2016 20:36:26 +0200
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 19:45:23 +0200
>
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus reuse the corresponding fu
On Sun, 2016-08-21 at 21:01 -0700, Josh Max wrote:
> This patch allows binfmt_misc to select the interpeter for arbitrary
> binaries by comparing a specified registered keyword with the value
> of a specified binary's extended attribute (user.binfmt.interp),
> and then launching the program with th
> diff --git a/drivers/i2c/muxes/i2c-mux-pca9541.c
> b/drivers/i2c/muxes/i2c-mux-pca9541.c
> index 3cb8af635db5..f052c3067791 100644
> --- a/drivers/i2c/muxes/i2c-mux-pca9541.c
> +++ b/drivers/i2c/muxes/i2c-mux-pca9541.c
> @@ -349,7 +349,8 @@ static int pca9541_probe(struct i2c_client *client,
>
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Block comments use a trailing */ on a separate line
Signed-off-by: Anson Jacob
---
drivers/staging/fbtft/fb_ssd1306.c | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/
On Thu, Aug 25, 2016 at 12:09:23PM -0400, Anson Jacob wrote:
> On Thu, Aug 25, 2016 at 06:47:08PM +0300, Andrey Utkin wrote:
> >
> > > +#define CHANNEL_BITS(x) ((x) & 0x7)
> > > +#define CHANNEL_MASK 0x7
> >
> > No uniform alignment. Please get everything in a row.
> > If it'
Fix checkpatch.pl warning for
Comparisons should place the constant on the right side of the test
Signed-off-by: Anson Jacob
---
drivers/staging/comedi/drivers/s626.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/s626.h
b/drivers/staging/come
On Mon, Aug 15, 2016 at 03:40:23PM +0200, Peter Rosin wrote:
> Hi!
>
> The nxp pca9541 chip does not have any devicetree bindings.
> When trying to write such bindings matching the implementation,
> I stumbled upon something which I did not like. I had to
> give the node holding the i2c child bus
Hi,
Here is the 2nd version of remote cross-arch probe support on perf-probe.
V1 is here:
https://lkml.org/lkml/2016/8/24/29
Currently perf-probe doesn't supoort cross/remote target. This means
we have to cross-build the perf-tools including libraries (elfutils,
libelf etc.), and to prepare vml
On 24.08.2016 00:18, Lucas De Marchi wrote:
> Diff from v3:
>
> - Fix over 80chars in one place
>
> - Move check for adapter being able to dynamically update TAR to be done
> on probe time rather than init as requested by Jarkko
>
> For the previous version, Christian had added:
>
Ignore the buildid of running kernel when both of --definition and
--vmlinux is given because that kernel should be off-line.
This also skips post-processing of kprobe event for relocating
symbol and checking blacklist, because it can not be done on
off-line kernel.
E.g. without this fix perf show
On Thu, Aug 25, 2016 at 06:22:37PM +0200, Peter Rosin wrote:
> On 2016-08-25 18:19, Wolfram Sang wrote:
> >
> >> diff --git a/drivers/i2c/muxes/i2c-mux-pca9541.c
> >> b/drivers/i2c/muxes/i2c-mux-pca9541.c
> >> index 3cb8af635db5..f052c3067791 100644
> >> --- a/drivers/i2c/muxes/i2c-mux-pca9541.c
Add --definition/-D option for showing the trace-event
definition in stdout. This can be useful in debugging
or combined with a shell script.
e.g.
# perf probe --definition 'do_sys_open $params'
p:probe/do_sys_open _text+2261728 dfd=%di:s32 filename=%si:u64 flags=%dx:s32
mode=%cx:u16
From: Markus Elfring
Date: Thu, 25 Aug 2016 18:20:30 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle s
Support probing on offline cross-architecture binary by
adding getting the target machine arch from ELF and
choose correct register string for the machine.
Here is an example:
-
$ perf probe --vmlinux=./vmlinux-arm --definition 'do_sys_open $params'
p:probe/do_sys_open do_sys_open+0 dfd=
On Fri, Jul 29, 2016 at 10:17:56AM +0200, Peter Rosin wrote:
> This unifies usage with i2c_lock_bus and i2c_unlock_bus, and paves the
> way for the next patch which looks a bit saner with this preparatory
> work taken care of beforehand.
>
> Signed-off-by: Peter Rosin
Applied to for-next, thanks
> > + ax8975@0c {
>
> Drop the leading 0. With that,
I fixed that locally.
signature.asc
Description: PGP signature
On 08/25/2016 11:43 AM, Peter Zijlstra wrote:
On Tue, Aug 23, 2016 at 06:13:43PM -0700, Jason Low wrote:
I tested this patch on an 8 socket system with the high_systime AIM7
workload with diskfs. The patch provided big performance improvements in
terms of throughput in the highly contended cases
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem (simply small driver fixups).
Changelog:
-
Andrew Duggan (1):
Input: synaptics-rmi4 - fix register descriptor subpacket map constr
On Fri, Jul 29, 2016 at 10:17:57AM +0200, Peter Rosin wrote:
> This makes it trivial to constify them, so do that.
>
> Signed-off-by: Peter Rosin
Applied to for-next, thanks!
signature.asc
Description: PGP signature
On Thu, Aug 25, 2016 at 12:33:04PM -0400, Waiman Long wrote:
> On 08/25/2016 11:43 AM, Peter Zijlstra wrote:
> >On Tue, Aug 23, 2016 at 06:13:43PM -0700, Jason Low wrote:
> >>I tested this patch on an 8 socket system with the high_systime AIM7
> >>workload with diskfs. The patch provided big perfor
On 25/08/16 14:45, Sudeep Holla wrote:
On 25/08/16 14:18, Neil Armstrong wrote:
[...]
Here I used if(is_legacy) to stop duplicating functions, is this ok
for you ?
I am still thinking if it can be abstracted well, some kind of mapping
but haven't thought too much about that yet. Also I
On Thu, Aug 18, 2016 at 10:04 AM, One Thousand Gnomes
wrote:
>> No, the code should be fast as it is so simple. I assume there is some
>> reason the tty buffering is more complex than just a circular buffer.
>
> I would suggest you read n_tty.c carefully and then it'll make a fair bit
> of sense.
On Thu, Aug 25, 2016 at 06:11:56PM +0800, Johnny Chuang wrote:
> This CL takes the responsibility for getting product/hardware id
> on recovery mode.
> It will fix firmware update script could not find correspond firmware
> file name on recovery mode.
> BTW, firmware must need to support reading pr
Ping !!
On 8/17/2016 9:23 AM, Santosh Shilimkar wrote:
Hi Arnd, Olof,
Can you please pick-up the fix for 4.8-rcx ?
Roger reported that USB ports are broken on Keystone2 boards
since v4.8-rc1 because USB_HPY config option got dropped.
On 8/17/2016 3:44 AM, Roger Quadros wrote:
Simply enabling
On Thu, Aug 25, 2016 at 10:56:50AM -0400, Rich Felker wrote:
> On Thu, Aug 25, 2016 at 10:07:08AM +0200, Thomas Gleixner wrote:
> > On Wed, 24 Aug 2016, Rich Felker wrote:
> As for this topic, what happened is that, after the first and second
> time of expressing confusion about how the infrastruct
Hi Bjorn,
On Wed, 10 Aug 2016, Bjorn Andersson wrote:
> On Mon 01 Aug 10:10 PDT 2016, Peter Griffin wrote:
>
> Sorry for the slow response, but I have a few more (small) concerns.
No problem, thanks for reviewing. Equally I've been away on holiday last 3
weeks, so sorry about my delay as well :
On Wed, Aug 24, 2016 at 11:25:41PM +0200, Jan Glauber wrote:
> Hi Wolfram,
>
> this update should address all comments. The probe funtion
> is much easier to read now after using the managed device functions.
>
> We also had an issue with the 5ms timeout and some ipmi/ssif commands so
> I dropped
On Wed, Aug 24, 2016 at 11:52:05AM +0200, Martin Kepplinger wrote:
> According to the kernel's guidelines, let's directly include the
> workqueue functions we use.
>
> Signed-off-by: Martin Kepplinger
> ---
> I don't know if it's worth it, but I should have included this according to
> the guidel
On Wed, Aug 24, 2016 at 10:51:20AM +0200, Thomas Gleixner wrote:
> On Tue, 16 Aug 2016, Bin Gao wrote:
> > On some newer Intel x86 processors/SoCs the TSC frequency can be directly
> > calculated by factors read from specific MSR registers or from a cpuid
> > leaf (0x15). TSC frequency calculated b
For DAX inodes we need to be careful to never have page cache pages in the
mapping->page_tree. This radix tree should be composed only of DAX
exceptional entries and zero pages.
ltp's readahead02 test was triggering a warning because we were trying to
insert a DAX exceptional entry but found that
From: Gustavo Padovan
If userspace is running an synchronously atomic commit and interrupts the
atomic operation during fence_wait() it will hang until the timer expires,
so here we change the wait to be interruptible so it stop immediately when
userspace wants to quit.
Also adds the necessary e
>> This issue was detected also by using the Coccinelle software.
>
> Do you have the scripts you use published somewhere?
Not yet.
I hope that I can clarify a few more implementation details around
my evolving scripts for the semantic patch language.
I guess that this approach can be publishe
>
> The email addresses below are also bcc'd here to see what bounces.
> The list of the bounces will be collected.
>
> Thoughts?
>
> aacr...@adaptec.com
> aacr...@microsemi.com
Hi Joe,
aacr...@microsemi.com is a mailing list, and is valid. I thought I had changed
aacr...@adaptec.com, but mus
Hi Arnd,
[auto build test WARNING on net-next/master]
[also build test WARNING on v4.8-rc3 next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience)
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Signed-off-by: Anson Jacob
---
drivers/staging/fbtft/fb_s6d1121.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/fbtft/fb_s6d1121.c
b/drivers/staging/fbtft/fb_s6d1121.c
index d6ae76b
On Thu, Aug 25, 2016 at 09:59:46PM +0800, Ming-Chia Chung wrote:
> On Tue, Aug 23, 2016 at 12:01:36PM +0530, Sudip Mukherjee wrote:
> > On Tue, Aug 23, 2016 at 08:19:46AM +0800, Ming-Chia Chung wrote:
> > > On Mon, Aug 22, 2016 at 10:51:27PM +0530, Sudip Mukherjee wrote:
> > > > On Tue, Aug 23, 201
Many modules call misc_register and misc_deregister in its module init
and exit methods without any additional code. This ends up being
boilerplate. This patch adds helper macro module_misc_device(), that
replaces module_init()/ module_exit() with template functions.
This patch also converts drive
On 08/24/2016 02:30 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 20:20:02 +0200
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Improve determination of sizes
> Use memdup_user() rather than du
- On Aug 19, 2016, at 4:23 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Fri, Aug 19, 2016 at 1:07 PM, Mathieu Desnoyers
> wrote:
>>
>> Benchmarking various approaches for reading the current CPU number:
>
> So I'd like to see the benchmarks of something that actually *does*
The lpc18xx driver currently manipulates the pwm_device struct directly
rather then using the pwm_set_chip_data. While the current method may
save a clock cycle or two, it is more obvious that data is set to
the local chip data pointer.
Signed-off-by: Olliver Schinagl
---
Hi,
This is a resend of
Hi,
> The omap i2c controller (at least on dra7x devices)
> doesn't have start/stop (STT/STP) support for slave mode
> so event #5 is not implemented in the driver.
I think you can deduce that. If a new {READ|WRITE}_REQUESTED slave event
comes in when you had *_PROCESSED events before, there mu
On Wed, Aug 24, 2016 at 01:28:58PM +0530, Vignesh R wrote:
> Add a driver to read group of GPIO lines and provide its status as a
> numerical value as input event to the system. This will help in
> interfacing devices, that can be connected over GPIOs, that provide
> input to the system by driving
On Thu, Aug 25, 2016 at 11:56:55AM +0100, Mark Rutland wrote:
> On Wed, Aug 24, 2016 at 06:23:03PM -0500, Zach Brown wrote:
> > The sdhci controller on xilinx zynq devices will not function unless
> > the cd bit is provided. http://www.xilinx.com/support/answers/61064.html
> > In cases where it is
This patch removes module_init()/module_exit() from driver code by using
module_misc_device() macro. All modules in this patch has a print
statement which is removed when module_misc_device() macro is used.
If undesirable this patch can be dropped entirely, this is the only
purpose of making this a
Hi Chao,
On Thu, Aug 25, 2016 at 05:22:29PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/8/24 0:53, Jaegeuk Kim wrote:
> > Hi Chao,
> >
> > On Sun, Aug 21, 2016 at 11:21:30PM +0800, Chao Yu wrote:
> >> From: Chao Yu
> >>
> >> In batch discard approach of fstrim will grab/release gc_mutex loc
On Thursday 25 August 2016 06:34 PM, Peter Zijlstra wrote:
On Thu, Aug 25, 2016 at 05:28:03PM +0530, Hari Bathini wrote:
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index d9b80ef..d35fbd3 100644
--- a/tools/perf/util/evsel.c
+++ b/tools/perf/util/evsel.c
@@ -929,6 +929,8 @@
On Thu, Aug 25, 2016 at 1:15 PM, Sean Paul wrote:
>
>
> On Wed, Aug 24, 2016 at 10:25 PM, Mark yao wrote:
>>
>> On 2016年08月23日 21:13, Sean Paul wrote:
>>>
>>> On Mon, Aug 22, 2016 at 8:40 PM, Mark yao
>>> wrote:
On 2016年08月23日 04:30, Sean Paul wrote:
>
> On Thu, Aug 18, 2016 at
This patch adds static keys transparently for all the cpu_hwcaps
features by implementing an array of default-false static keys and
enabling them when detected. The cpus_have_cap() check uses the static
keys if the feature being checked is a constant, otherwise the compiler
generates the bitmap tes
The static key API is currently designed around single variable
definitions. There are cases where an array of static keys is desirable,
so extend the API to allow this rather than using the internal static
key implementation directly.
Suggested-by: Dave P Martin
Cc: Jason Baron
Cc: Jonathan Cor
This series is aimed to optimise the arm64 cpus_have_cap() functionality
(checking for the presence of certain CPU capabilities/features) to
avoid a bitmap test and use a jump label instead, patched at boot time.
While this series may not provide a clear performance improvement with
the current ke
On Thu, Aug 25, 2016 at 10:50:18PM +0530, Hari Bathini wrote:
> Actually, on second thought, how about using inode number of some
> other namespace that any container would have (mount, probably?)..
I have no clue about those things. The only thing I can tell you is that
you get to pick once ;-)
> Right, I was waiting for some confirmation if v4.8-rc3 was a good base,
> but I'm running out of patience...
For me, it is perfect.
> Anyway, I'll send the pull request no later that tomorrow morning (CEST).
Thanks!
> I assume I can add your ack?
Rather this:
Reviewed-by: Wolfram Sang
> -Original Message-
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On
> Behalf Of Yauheni Kaliuta
> Sent: Wednesday, August 24, 2016 9:54 PM
> To: k...@exchange.microsoft.com
> Cc: o...@aepfle.de; gre...@linuxfoundation.org; jasow...@redhat.com; Alex
> Ng (LIS) ; l
On Thu, 25 Aug 2016 19:34:29 +0200
SF Markus Elfring wrote:
> >> This issue was detected also by using the Coccinelle software.
> >
> > Do you have the scripts you use published somewhere?
>
> I would like to add another view for the corresponding software development.
>
> The complete answe
On 08/25/2016 05:05 AM, Alexey Brodkin wrote:
> Hi Liav,
>
> On Wed, 2016-08-17 at 09:23 +0300, Liav Rehana wrote:
>> From: Liav Rehana
>>
>> User mode callee regs are explicitly collected before signal delivery
>> or breakpoint trap. r25 is special for kernel as it serves as task
>> pointer, so u
>> This issue was detected also by using the Coccinelle software.
>
> Do you have the scripts you use published somewhere?
I would like to add another view for the corresponding software development.
The complete answer depends also on the kind of "scripts"
you are looking for. Would you like
hw->DACreg has a size of 80 bytes and MGADACbpp32 has 21. So when
memcpy copies MGADACbpp32 to hw->DACreg it copies 80 bytes but
only 21 bytes are valid.
Signed-off-by: Sudip Mukherjee
---
drivers/video/fbdev/matrox/matroxfb_Ti3026.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
On Thu, Aug 25, 2016 at 05:41:29PM +0200, Thomas Gleixner wrote:
> On Thu, 25 Aug 2016, Rich Felker wrote:
> > assumption that is was just a bug. Now that Mark Rutland has explained
> > it well (and with your additional explanation below in your email), I
> > see what the motivation was, but I stil
On Wed, 2016-08-24 at 18:23:03 -0500, Zach Brown wrote:
> The sdhci controller on xilinx zynq devices will not function unless
> the cd bit is provided. http://www.xilinx.com/support/answers/61064.html
> In cases where it is impossible to provide the cd bit in hardware,
> setting the controller to
On Wed, Aug 24, 2016 at 02:37:07PM -0500, Josh Poimboeuf wrote:
> On Wed, Aug 24, 2016 at 02:37:21PM -0400, Linus Torvalds wrote:
> > On Wed, Aug 24, 2016 at 2:22 PM, Peter Zijlstra
> > wrote:
> > >
> > > I actively disable KASLR on my dev box and feed these hex numbers into
> > > addr2line -ie v
On Thu, Aug 25, 2016 at 11:52:01AM +0200, Daniel Wagner wrote:
> diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
> index 22d1760..f397026 100644
> --- a/drivers/base/firmware_class.c
> +++ b/drivers/base/firmware_class.c
> @@ -91,10 +91,13 @@ static inline bool fw_is_buil
From: Olliver Schinagl
The pwm-block of some of the sunxi chips feature a 'ready' flag to
indicate the software that it is ready for new commands.
Right now, when we call pwm_config and set the period, we write the
values to the registers, and turn off the clock to the IP. Because of
this, the h
Hi all,
last year I've sent out this patch series and there was little technical
discussion, so hopefully we can rekindle it.
This patch series fixes 2 issues. For one, we add a delay between disabling
the PWM hardware block and removing the clock, this to yield the PWM hardware
time to actually
When we inform the PWM block to stop toggeling the output, we may end up
in a state where the output is not what we would expect (e.g. not the
low-pulse) but whatever the output was at when the clock got disabled.
To counter this we have to wait for maximally the time of one whole
period to ensure
> You obviously run some kind of semantic patching.
Yes. - I developed some software for search patterns I became interested in.
> It would really help ease review if you could publish the semantic patches
> that generate your patches
This is reasonable.
> - that is probably more helpful in r
Am 24.08.2016 22:36, schrieb SF Markus Elfring:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 22:26:37 +0200
>
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus reuse the corresponding function "kmalloc_ar
>You should generally test with something not ancient,
It has been tested with 4.7 kernel too, board was booted but it can
not verified further as 4.7 vanilla kernel does not launched shell
prompt with udoo board, well this can be done.
>Sorry, but this approach is never going to be accepted. Sim
On 8/25/16, 10:08 AM, "Mathieu Desnoyers"
wrote:
> The most appealing application we have so far is Dave Watson's Facebook
>services using jemalloc as a memory allocator. It would be nice if he
>could re-run those benchmarks with my rseq implementation. The trade-offs
>here are about
Arnd Bergmann writes:
> On Thursday, August 25, 2016 4:43:04 PM CEST Arnd Bergmann wrote:
>> drivers/net/ethernet/smsc/smc91x.h | 50
>> +++---
>> 1 file changed, 30 insertions(+), 20 deletions(-)
>>
>> While this patch fixes one bug on Neponset, it probably doe
On Thu, 25 Aug 2016, Arnd Bergmann wrote:
> As Russell King found out the hard way, a change I did to fix multiplatform
> builds with this driver broke the old Assabet/Neponset platform: It turns
> out that while the driver is runtime configurable in principle, the
> runtime configuration does not
On Thu, Aug 25, 2016 at 12:15:44PM -0500, Zach Brown wrote:
> On Thu, Aug 25, 2016 at 11:56:55AM +0100, Mark Rutland wrote:
> > On Wed, Aug 24, 2016 at 06:23:03PM -0500, Zach Brown wrote:
> > > +- fake-cd: On Zynq Devices the SDHCI Controller will not work without
> > > the cd
> > > + bit. When t
On Thu, 25 Aug 2016, SF Markus Elfring wrote:
> >> This issue was detected also by using the Coccinelle software.
> >
> > Do you have the scripts you use published somewhere?
>
> I would like to add another view for the corresponding software development.
>
> The complete answer depends also o
On Thu, 25 Aug 2016, Arnd Bergmann wrote:
> The ARM specific I/O operations are almost the same as the generic
> ones, with the exception of the SMC_outw macro that works around
> a problem of some platforms that cannot write to 16-bit registers
> at an address that is not 32-bit aligned.
>
> By
On Thu, 25 Aug 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 25 Aug 2016 17:45:23 +0200
>
> Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
> Thus use the corresponding function "kmalloc_array".
>
> Or some close variant.
I have got more script variants evolving in my software collection.
There are further approaches available from various contributors,
aren't there?
Regards,
Markus
On Thu, Aug 25, 2016 at 01:51:35PM -0400, Rich Felker wrote:
> On Thu, Aug 25, 2016 at 05:38:06PM +0100, Mark Rutland wrote:
> > On Thu, Aug 25, 2016 at 10:56:50AM -0400, Rich Felker wrote:
> > > On Thu, Aug 25, 2016 at 10:07:08AM +0200, Thomas Gleixner wrote:
> > > Nominally it uses the same range
On Thu, Aug 25, 2016 at 05:38:06PM +0100, Mark Rutland wrote:
> On Thu, Aug 25, 2016 at 10:56:50AM -0400, Rich Felker wrote:
> > On Thu, Aug 25, 2016 at 10:07:08AM +0200, Thomas Gleixner wrote:
> > > On Wed, 24 Aug 2016, Rich Felker wrote:
> > As for this topic, what happened is that, after the fir
On Thu, 25 Aug 2016, SF Markus Elfring wrote:
> > Or some close variant.
>
> I have got more script variants evolving in my software collection.
>
> There are further approaches available from various contributors,
> aren't there?
What she is asking for is a concise and precise decription of wh
On 8/24/2016 1:54 AM, Randy Li wrote:
>
>
> On 08/24/2016 04:46 AM, John Youn wrote:
>> On 8/21/2016 12:32 PM, Randy Li wrote:
>>> On the rk3288 USB host-only port (the one that's not the OTG-enabled
>>> port) the PHY can get into a bad state when a wakeup is asserted (not
>>> just a wakeup from
Hi,
On Wed, Aug 24, 2016 at 11:42:00AM -0500, Steven J. Hill wrote:
> It is actually two patches that cause the breakage. The other is:
>
>commit e55aeb6ba4e8cc3549bff1e75ea1d029324bce21
>of/irq: Mark interrupt controllers as populated before initialisation
>
> I needed to revert both of
On Thu 25 Aug 05:59 PDT 2016, Stanimir Varbanov wrote:
> Hi Bjorn,
>
> Thanks for the review and comments!
>
> On 08/23/2016 05:50 AM, Bjorn Andersson wrote:
> > On Mon 22 Aug 06:13 PDT 2016, Stanimir Varbanov wrote:
> >
> > Hi Stan,
> >
> >> This adds core part of the vidc driver common helpe
On Thu, Aug 25, 2016 at 01:26:22PM -0500, Zach Brown wrote:
> On Thu, Aug 25, 2016 at 07:10:00PM +0100, Mark Rutland wrote:
> > On Thu, Aug 25, 2016 at 12:15:44PM -0500, Zach Brown wrote:
> > > In cases where the card is non-removable then polling doesn't make sense.
> >
> > We have the non-remova
On 08/24/2016 02:48 PM, Tillmann Heidsieck wrote:
> For systems with >4G of RAM, the current implementation adds a second
> inbound PCIe window starting at 128G this leaves all memory from 4G to
> 128G inaccessible to inbound PCIe transactions.
The second inbound window is at 256G, and it maps all
On Tue, Aug 23, 2016 at 08:57:22PM -0400, Jarkko Sakkinen wrote:
> + if (flags & TPM_TRANSMIT_LOCK)
> + mutex_lock(&chip->tpm_mutex);
I think I would invert this. UNLOCKED is the exceptional case, so I'd
make the 0 flags lock. If we see UNLOCKED in the caller then we know
to audit
Den 25.08.2016 15:09, skrev Rob Herring:
On Mon, Aug 22, 2016 at 3:25 PM, Noralf Trønnes wrote:
The SimpleDRM driver binds to simple-framebuffer devices and provides a
DRM/KMS API. It provides only a single CRTC+encoder+connector combination
plus one initial mode.
Userspace can create dumb-bu
Hello,
This patch series implements a mechanism which allows the kernel to pass
on a buffer to the kernel that will be kexec'd. This buffer is passed
as a segment which is added to the kimage when it is being prepared
by kexec_file_load.
How the second kernel is informed of this buffer is archite
Now that mutex::count and mutex::owner are the same field, we can
allow SPIN_ON_OWNER while DEBUG_MUTEX.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/Kconfig.locks |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/Kconfig.locks
+++ b/kernel/Kconfig.locks
@@ -225,7 +225,7
There's a number of iffy in mutex because mutex::count and
mutex::owner are two different fields; this too is the reason
MUTEX_SPIN_ON_OWNER and DEBUG_MUTEX are mutually exclusive.
Cure this by folding them into a single atomic_long_t field.
This nessecairly kills all the architecture specific mu
Now that we have an atomic owner field, we can do explicit lock
handoff. Use this to avoid starvation.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/locking/mutex.c | 52 +++--
1 file changed, 46 insertions(+), 6 deletions(-)
--- a/kernel/locking
Poking at lock internals is not cool. Since I'm going to change the
implementation this will break, take it out.
Cc: Chris Wilson
Cc: Daniel Vetter
Signed-off-by: Peter Zijlstra (Intel)
---
drivers/gpu/drm/i915/i915_gem_shrinker.c | 26 +++---
1 file changed, 3 insertions
... might still eat your pets and set your house on fire ...
Passes reaim high_systime on 4 socket haswell..
4.8.0-rc3-00185-g9f55477 +2 +all
Forks Jobs/min Jobs/min Jobs/min
10 1040.001039.83 1039.83
20 1600.00
On 08/25/2016 04:30 PM, Alan Stern wrote:
On Thu, 25 Aug 2016, Jacek Anaszewski wrote:
I'd see it as follows:
#cat available_ports
#1-1 1-2 2-1
#echo "1-1" > new_port
#cat observed_ports
#1-1
#echo "2-1" > new_port
#cat observed_ports
#1-1 2-1
We've already had few discussions about the s
On 08/12/2016 05:59 PM, Waiman Long wrote:
> + * The lock and the hpet value are stored together and can be read in a
> + * single atomic 64-bit read. It is explicitly assumed that arch_spinlock_t
> + * is 32 bits in size.
This requirement forces us to give up all of the goodness of lockdep.
Is th
Bug 150611 uncovered that the WMI ID used by the toshiba-wmi driver
is not Toshiba specific, and as such, the driver was being loaded
on non Toshiba laptops too.
This patch adds a DMI matching list checking for TOSHIBA as the
vendor, refusing to load if it is not.
Also the WMI GUID was renamed, d
Greg KH writes:
> On Thu, Aug 25, 2016 at 07:14:52AM +0200, Rafał Miłecki wrote:
>>
>> Good question. I would like to extend this USB port trigger in the
>> future by reacting to USB activity. This involves playing with URBs
>> and I believe that at that point it'd be getting too much USB specific
On Thursday 25 August 2016 12:31 PM, Dave Young wrote:
On 08/10/16 at 03:35pm, Hari Bathini wrote:
When fadump is enabled, by default 5% of system RAM is reserved for
fadump kernel. While that works for most cases, it is not good enough
for every case.
Currently, to override the default value
On Thu, Aug 25, 2016 at 07:10:00PM +0100, Mark Rutland wrote:
> On Thu, Aug 25, 2016 at 12:15:44PM -0500, Zach Brown wrote:
> > On Thu, Aug 25, 2016 at 11:56:55AM +0100, Mark Rutland wrote:
> > > On Wed, Aug 24, 2016 at 06:23:03PM -0500, Zach Brown wrote:
> > > > +- fake-cd: On Zynq Devices the SDH
Acked-by: Bradley Grove
On 08/20/2016 10:33 PM, Shawn Lin wrote:
We don't need to use kzalloc as we will always memset the
local_atto_ioctl later.
Signed-off-by: Shawn Lin
---
drivers/scsi/esas2r/esas2r_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/
Acked-by: Bradley Grove
On 08/20/2016 10:39 PM, Shawn Lin wrote:
req_table is allocate by kzalloc, so we don't need to
zero it again anyway.
Signed-off-by: Shawn Lin
---
drivers/scsi/esas2r/esas2r_init.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/scsi/esas2r/esas2r_init.
Subject: x86,mm,sched: make lazy TLB mode even lazier
Lazy TLB mode can result in an idle CPU being woken up for a TLB
flush, when all it really needed to do was flush %cr3 before the
next context switch.
This is mostly fine on bare metal, though sub-optimal from a power
saving point of view, and
401 - 500 of 744 matches
Mail list logo
