* Borislav Petkov wrote:
> On Sun, Jan 31, 2016 at 09:33:25AM -0800, Andy Lutomirski wrote:
> > I broke iopl(2) with my syscall rework. Fix it up. While debugging
> > it, I found a bug in my IRQ state handling. Fix that, too.
> >
> > Andy Lutomirski (3):
> > x86/entry/64: Fix an IRQ state
Kindly review the patch. Patchv2 had refcount issue which is fixed here.
On Tue, 12 Jan 2016 09:31:46 +0530
Rohit kumar wrote:
> Currently we can only import dma buf fd's to get ion_handle.
> Adding support to import dma buf handles to support kernel
> specific use cases.
>
> An example use
* Ingo Molnar wrote:
> [...]
>
> I kept the process, threading and memory allocation bits of numa.c, just in
> case
> we need them to measure more complex syscalls. Maybe we could keep the
> threading
> bits and remove the memory allocation parameters, to simplify the benchmark?
So the
* r...@redhat.com wrote:
> (v3: address comments raised by Frederic)
>
> Running with nohz_full introduces a fair amount of overhead.
> Specifically, various things that are usually done from the
> timer interrupt are now done at syscall, irq, and guest
> entry and exit times.
>
> However,
Hi folks!
I'd wish ntp_loopfilter.c would compile without problems. The mess is (I had
fixed it about 15 years ago (keyword "PPSkit")) that Linux uses ADJ_* flags to
do traditional adjtime() things, as well as NTP kernel-related things (That's
why the Linux syscall is named adjtimex()).
NTP
On Mon, 1 Feb 2016, ByeoungWook Kim wrote:
> The current realtek driver was written like my patch comments. but
> Documentation/CodingStyle isn't before.
> So I wrote patch like current realtek driver.
That is probably fine, then. Sorry for the noise. I looked at some other
code in the
The current realtek driver was written like my patch comments. but
Documentation/CodingStyle isn't before.
So I wrote patch like current realtek driver.
How should i do it?
Regards,
Byeoungwook.
2016-02-01 16:01 GMT+09:00 Julia Lawall :
>
>
> On Mon, 1 Feb 2016, Byeoungwook Kim wrote:
>
>>
This patch adds the needed spi node for rk3036 dts.
We have to use the 4 bus emmc to work if someone want to support
the spi devices, since the pins are re-used by emmc data[5-8] and spi.
In some caseswe need to support the spi devices, that will waste the
emmc performance.
Moment, the kylin/evb
Hi Robert
On Sun, 2016-01-31 at 00:20 +0100, Robert Jarzmik wrote:
> Marcel, would you try the patch here after ?
> I have tested it on my cm-x300 with a devicetree build, let's see if
> that is a
> solution to your issue.
Yes, that indeed cuts it nicely. Thanks!
> Cheers.
>
> --
> Robert
>
On Mon, Feb 01, 2016 at 05:14:32PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160129:
blackfin defconfig fails, and it needs
https://patchwork.kernel.org/patch/8148161/
regards
sudip
Hi, Richard
> From: Richard Weinberger [mailto:rich...@nod.at]
> Sent: Thursday, January 28, 2016 5:32 PM
> To: Bean Huo 霍斌斌 (beanhuo); Artem Bityutskiy; Adrian Hunter; Brian
> Norris
> Cc: linux-...@lists.infradead.org; linux-kernel@vger.kernel.org; Boris
> Brezillon; Peter Pan 潘栋
In some conditions(such as umount fs failed),origin path or origin bdev or both
of the two is same
as cow's.If this happens, origin dev will be freed when get cow dev in function
"dm_get_device" ,
then "s->origin->dev" which used by "dm_exception_store_create" will be a NULL
pointer.
On Mon, 1 Feb 2016, Byeoungwook Kim wrote:
> clean up checkpatch warning:
> WARNING: Block comments use * on subsequent lines
>
> Signed-off-by: Byeoungwook Kim
> ---
> drivers/staging/rtl8192u/r8192U_wx.c | 38
> +++-
> 1 file changed, 20 insertions(+), 18
Hello Vinod,
Is there any chance apply the DMA patches?:-)
-
Caesar
在 2016年01月22日 19:06, Caesar Wang 写道:
This series patches are apply on linus master branch.
Okay, this series patches verified on my github.
(https://github.com/Caesar-github/rockchip/commits/for-dma-tests)
Linux version
On 01/29/2016 07:55 PM, Paul Gortmaker wrote:
> [Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible pointer check
> into error] On 29/01/2016 (Fri 13:17) Daniel Wagner wrote:
>
>> On 01/28/2016 03:44 PM, Daniel Wagner wrote:
>>> +# enforce correct pointer usage
>>> +KBUILD_CFLAGS +=
Certain spi controllers may provide accelerated interface to read from
m25p80 type flash devices. This interface provides better read
performance than regular SPI interface.
Call spi_flash_read(), if supported, to make use of such interface.
Signed-off-by: Vignesh R
---
Resend v5:
Rebased on
Resend v5:
Rebased on top of v4.5-rc1
Changes since v4:
Use syscon to access system control module register in ti-qspi driver.
Changes since v3:
Rework to introduce spi_flash_read_message struct.
Support different opcode/addr/data formats as per Brian's suggestion
here:
ti-qspi controller provides mmap port to read data from SPI flashes.
mmap port is enabled in QSPI_SPI_SWITCH_REG. ctrl module register may
also need to be accessed for some SoCs. The QSPI_SPI_SETUP_REGx needs to
be populated with flash specific information like read opcode, read
mode(quad, dual,
In addition to providing direct access to SPI bus, some spi controller
hardwares (like ti-qspi) provide special port (like memory mapped port)
that are optimized to improve SPI flash read performance.
This means the controller can automatically send the SPI signals
required to read data from the
On Monday 01 February 2016 11:58 AM, Sushaanth Srirangapathi wrote:
add binding information for tps6507x touchscreen input.
Signed-off-by: Sushaanth Srirangapathi
Please ignore this patch. It was an older version which was sent by
mistake.
Thanks,
Sushaanth
在 2016年01月31日 18:46, Heiko Stuebner 写道:
Am Donnerstag, 28. Januar 2016, 16:43:30 schrieb Caesar Wang:
As the kylin schematic drawing, add the needed work led for
kylin board.
Run:
echo 0 > /sys/class/leds/kylin:red:led/brightness
echo 1 > /sys/class/leds/kylin:red:led/brightness
The led can
On Wed, Jan 20, 2016 at 07:26:14PM +0900, Byungchul Park wrote:
> On Wed, Jan 20, 2016 at 02:43:35PM +0900, Byungchul Park wrote:
> >
> > It looks very tricky. I have a question. Do we have to call the
> > scheduler_tick() even while the tick is stopped? IMHO, it seems to be
> > ok even if we
Hi Andre,
On Wed, Jan 27, 2016 at 11:51:45PM +, André Przywara wrote:
> Hi,
>
> On 18/01/16 14:28, Lee Jones wrote:
> > This call matches clocks which have been marked as critical in DT
> > and sets the appropriate flag. These flags can then be used to
> > mark the clock core flags
Heiko,
在 2016年01月31日 19:06, Heiko Stuebner 写道:
Hi Caesar,
Am Donnerstag, 28. Januar 2016, 16:43:38 schrieb Caesar Wang:
[...]
memory {
@@ -485,6 +486,23 @@
status = "disabled";
};
+ spi: spi@20074000 {
+ compatible =
Add DT support for touchscreen input device tps6507x-ts which is part
of MFD device "TPS6507x"
Sushaanth Srirangapathi (3):
Input: tps6507x-ts - add binding for tps6507x-ts
Input: tps6507x-ts - Add device tree support
ARM: DTS: da850: add DT node for tps6507x-ts
Add device tree support for TPS6507x touchscreen input device.
Signed-off-by: Sushaanth Srirangapathi
---
drivers/input/touchscreen/tps6507x-ts.c | 51 ---
1 file changed, 47 insertions(+), 4 deletions(-)
diff --git a/drivers/input/touchscreen/tps6507x-ts.c
add binding information for tps6507x touchscreen input.
"ti,min-pressure" was added as TI specific binding because it
was specific to tps6507x IP and not applicable or relevant for
other touchscreen drivers.
Signed-off-by: Sushaanth Srirangapathi
---
add binding information for tps6507x touchscreen input.
Signed-off-by: Sushaanth Srirangapathi
---
Documentation/devicetree/bindings/mfd/tps6507x.txt | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/tps6507x.txt
add tps6507x touchscreen device tree node information to
DA850 EVM
Signed-off-by: Sushaanth Srirangapathi
---
arch/arm/boot/dts/da850-evm.dts |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/da850-evm.dts b/arch/arm/boot/dts/da850-evm.dts
index ef061e9..b4f54fc 100644
On Mon, Feb 01, 2016 at 11:31:12AM +0900, Sergey Senozhatsky wrote:
> On (01/29/16 21:43), Byungchul Park wrote:
> [..]
> > +extern int is_console_lock(raw_spinlock_t *lock);
> > +
> > static void __spin_lock_debug(raw_spinlock_t *lock)
> > {
> > u64 i;
> > @@ -113,11 +115,19 @@ static void
Hi Rob,
Thank you for your review.
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: 2016年1月30日 0:20
> To: Yang, Wenyou
> Cc: Ferre, Nicolas ; Alexandre Belloni
> ; Jean-Christophe Plagniol-Villard
> ; Russell King ; linux-
> c...@vger.kernel.org; Pawel Moll ;
On Mon, 2016-02-01 at 12:15 +0800, Daniel Kurtz wrote:
> On Mon, Feb 1, 2016 at 10:04 AM, Horng-Shyang Liao
> wrote:
> >
> > On Fri, 2016-01-29 at 21:15 +0800, Daniel Kurtz wrote:
> > > On Fri, Jan 29, 2016 at 8:24 PM, Horng-Shyang Liao
> > > wrote:
> > > > On Fri, 2016-01-29 at 16:42 +0800,
Hi all,
Changes since 20160129:
The dt-rh tree gained a conflict against the qcom tree.
The rcu tree gained a build failure so I used the version from
next-20160129.
The staging tree gained conflicts against the staging.current and
tty trees.
The gpio tree still had its build failure so I
On 30-01-16, 12:49, Rafael J. Wysocki wrote:
> On Friday, January 29, 2016 04:33:39 PM Saravana Kannan wrote:
> > AFAIR, the ABBA issue was between the sysfs lock and the policy lock.
Yeah, to be precise here it is:
CPU0 (sysfs read) CPU1 (exit governor)
sysfs-read
Sanity check at binder ioctl function,
Only allow the shared mm_struct to use the same binder-object
to do binder operate.
And add proc->vma_vm_mm = current->mm at the open function.
The libbinder do ioctl before mmap called.
V2: Fix compile error for error commit
V3: Change the condition to
On Monday 25 January 2016 01:19 PM, Shawn Lin wrote:
> Hello Kishon,
>
> Any changce to apply this patch? :)
back from vacation. Will review it this week. Sorry for the delay.
Thanks
Kishon
>
> On 2016/1/5 9:08, Shawn Lin wrote:
>> This patch to add a generic PHY driver for ROCKCHIP eMMC
On 29-01-16, 16:57, Saravana Kannan wrote:
> I haven't looked at the cpufreq-tests, but I doubt they do hotplug testing
> where they remove all the CPUs of a policy (to trigger a policy exit).
They do.
--
viresh
Hi Javier & Mark,
I am educated. Thank you all.
> -Original Message-
> From: Javier Martinez Canillas [mailto:jav...@dowhile0.org]
> Sent: 2016年1月29日 19:50
> To: Mark Brown
> Cc: Yang, Wenyou ; Liam Girdwood
> ; Rob Herring ; Pawel Moll
> ; Ian Campbell ; Kumar
> Gala ; Krzysztof
Andi Kleen writes:
> On Mon, Feb 01, 2016 at 09:08:44AM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://github.com/0day-ci/linux
>> Andi-Kleen/Optimize-int_sqrt-for-small-values-for-faster-idle/20160129-054629
>> commit
On 01/27/2016 08:45 AM, One Thousand Gnomes wrote:
> On Wed, 27 Jan 2016 15:17:52 +0300
> Aleksey Makarov wrote:
>
>> On 01/25/2016 07:11 PM, Peter Hurley wrote:
>>> On 01/25/2016 03:45 AM, Aleksey Makarov wrote:
This patchset is based on the patchset by Leif Lindholm [1]
'ARM
On Mon, Feb 01, 2016 at 09:08:44AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux
> Andi-Kleen/Optimize-int_sqrt-for-small-values-for-faster-idle/20160129-054629
> commit 6ffc77f48b85ed9ab9a7b2754a7b49891ebaff83 ("Optimize int_sqrt for
clean up checkpatch warning:
WARNING: Block comments use * on subsequent lines
Signed-off-by: Byeoungwook Kim
---
drivers/staging/rtl8192u/r8192U_wx.c | 38 +++-
1 file changed, 20 insertions(+), 18 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
clean up checkpatch warning:
WARNING: Block comments use * on subsequent lines
Signed-off-by: Byeoungwook Kim
---
drivers/staging/rtl8192u/r8192U_wx.c | 38 +++-
1 file changed, 20 insertions(+), 18 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
clean up checkpatch warning:
WARNING: Block comments use * on subsequent lines
Signed-off-by: Byeoungwook Kim
---
drivers/staging/rtl8192u/r8192U_wx.c | 38 +++-
1 file changed, 20 insertions(+), 18 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
Okay. I've started from driver level printk
results are:
On 4.2
[414006.575989] Before pci_enable_device IRQ 20
[414006.575991] After pci_enable_device IRQ 20
[414006.575997] Before pci_enable_device IRQ 21
[414006.575999] After pci_enable_device IRQ 21
on 4.3
[ 114.862289] Before
Hi Jitao,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.5-rc2 next-20160129]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
Hi Rik,
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.5-rc2 next-20160129]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
On Fri, Jan 29, 2016 at 10:08:23AM +0200, Kalle Valo wrote:
> Sudip Mukherjee writes:
>
> >> >> That's also my experience from maintaining wireless-drivers for a year,
> >> >> this seems to be a "hit and run" type of phenomenon.
> >> >
> >> > Should we be looking for someone to run a
Kever,
On Sun, Jan 31, 2016 at 7:32 PM, Kever Yang wrote:
> Doug,
>
>
> On 02/01/2016 06:09 AM, Doug Anderson wrote:
>>
>> Kever,
>>
>> On Sun, Jan 31, 2016 at 1:36 AM, Kever Yang
>> wrote:
>>>
>>> Doug,
>>>
>>>
>>> On 01/29/2016 10:20 AM, Douglas Anderson wrote:
In
Соберем для Вас по интернет базу данных потенциальных клиентов для Вашего
Бизнеса!!! Много! Быстро! Не дорого! Узнайте об этом подробнее по
Тел\Viber\Whatsapp:+79133913837 Skype:prodawez389 Email:gdrozdov...@gmail.com
Hi Sudip,
On Mon, Feb 1, 2016 at 3:25 PM, Sudip Mukherjee
wrote:
> On Mon, Feb 01, 2016 at 11:03:35AM +1100, Julian Calaby wrote:
>> Hi Sudip,
>>
>> On Fri, Jan 29, 2016 at 8:49 PM, Sudip Mukherjee
>> wrote:
>> > On error we jumped to the error label and returned the error code but we
>> >
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 36f90b0a2ddd60823fe193a85e60ff1906c2a9b3
commit: c6d308534aef6c99904bf5862066360ae067abc4 UBSAN: run-time undefined
behavior sanity checker
date: 11 days ago
config: i386-randconfig-h1-02011158 (attached
On Mon, Feb 01, 2016 at 11:03:35AM +1100, Julian Calaby wrote:
> Hi Sudip,
>
> On Fri, Jan 29, 2016 at 8:49 PM, Sudip Mukherjee
> wrote:
> > On error we jumped to the error label and returned the error code but we
> > missed releasing sinfo.
> >
> > Signed-off-by: Sudip Mukherjee
>
> Should
On Mon, Feb 1, 2016 at 10:04 AM, Horng-Shyang Liao wrote:
>
> On Fri, 2016-01-29 at 21:15 +0800, Daniel Kurtz wrote:
> > On Fri, Jan 29, 2016 at 8:24 PM, Horng-Shyang Liao
> > wrote:
> > > On Fri, 2016-01-29 at 16:42 +0800, Daniel Kurtz wrote:
> > >> On Fri, Jan 29, 2016 at 3:39 PM,
This patch adds drm_bridge driver for parade DSI to eDP bridge chip.
Signed-off-by: Jitao Shi
---
Changes since v7:
- Change ps8640_regw to ps8640_regw_bytes and remove devm_kzalloc
- Fine tune ps8640 power squence
- Add ps8640_pre_enable and ps8640_post_disable in ps8640_get_modes
- Remove
Add documentation for DT properties supported by
ps8640 DSI-eDP converter.
Signed-off-by: Jitao Shi
Acked-by: Rob Herring
Reviewed-by: Philipp Zabel
---
Changes since v7:
- No change
---
.../devicetree/bindings/display/bridge/ps8640.txt | 43
1 file changed, 43
This patch fix a typo witin HOWTO, which was translated in Japanese.
Replace a word "kernlehacker" with "kernelhacker".
Signed-off-by: Masanari Iida
---
Documentation/ja_JP/HOWTO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ja_JP/HOWTO
On Mon, Feb 01, 2016 at 02:45:21PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/panel/panel.c
>
> between commit:
>
> b64a1cbef6df ("Revert "Staging: panel: usleep_range is preferred over
> udelay"")
>
>
On Mon, Feb 01, 2016 at 02:51:46PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/dgap/dgap.c
>
> between commits:
>
> 6aa56785e735 ("staging: digi: Replace open-coded tty_wakeup()")
> 2d73b069f816
Hi Arnd:
I have got a new idea about the problem:
In include/linux/time64.h
#define NSEC_PER_SEC10L
I think we should change it to
#define NSEC_PER_SEC10LL
My reason is :
1. when it is used in a multiplication, it will easily get overflow.
2. when it don't get
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/dgap/dgap.c
between commits:
6aa56785e735 ("staging: digi: Replace open-coded tty_wakeup()")
2d73b069f816 ("staging: dgap: Remove redundant write_wait wakeups")
9db276f8f021 ("tty: Use termios
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/panel/panel.c
between commit:
b64a1cbef6df ("Revert "Staging: panel: usleep_range is preferred over
udelay"")
from the staging.current tree and commit:
df44f1504b4d ("staging: panel: remove
huang ying writes:
> On Sat, Jan 30, 2016 at 9:18 AM, Ding Tianhong
> wrote:
>> On 2016/1/29 17:53, Peter Zijlstra wrote:
>>> On Sun, Jan 24, 2016 at 04:03:50PM +0800, Ding Tianhong wrote:
>>>
looks good to me, I will try this solution and report the result, thanks
everyone.
>>>
>>>
On 2016/2/1 11:02, Davidlohr Bueso wrote:
> On Mon, 01 Feb 2016, Kefeng Wang wrote:
>
>> Hi Davidlohr,
>>
[...]
>>
>> Yes, it works, but what you are doing is to revert commit
>> a36a99618b1adb2d6ca0b7e08e3a656a04e477fe
>
> Oh, I see. I was definitely not aware of that one.
>
> [...]
>
>>
Hi Andy,
Andy Shevchenko 於 2016/1/29 下午 08:40 寫道:
On Fri, 2016-01-29 at 16:20 +0800, Peter Hung wrote:
Hi Andy,
Andy Shevchenko 於 2016/1/28 下午 08:04 寫道:
On Thu, 2016-01-28 at 17:20 +0800, Peter Hung wrote:
- /* Fintek PCI serial cards */
- { PCI_DEVICE(0x1c29, 0x1104),
Doug,
On 02/01/2016 06:09 AM, Doug Anderson wrote:
Kever,
On Sun, Jan 31, 2016 at 1:36 AM, Kever Yang wrote:
Doug,
On 01/29/2016 10:20 AM, Douglas Anderson wrote:
In dwc2_hcd_qh_deactivate() we will put some things on the
periodic_sched_ready list. These things won't be taken off the
On Sat, Jan 30, 2016 at 9:18 AM, Ding Tianhong wrote:
> On 2016/1/29 17:53, Peter Zijlstra wrote:
>> On Sun, Jan 24, 2016 at 04:03:50PM +0800, Ding Tianhong wrote:
>>
>>> looks good to me, I will try this solution and report the result, thanks
>>> everyone.
>>
>> Did you get a change to run with
On 2016/2/1 10:17, Wangnan (F) wrote:
On 2016/1/31 5:02, Tong Zhang wrote:
reproduce:
lzto@objd ~ $ ~/linux/tools/perf/perf record -I -e
intel_pt/tsc=1,noretcomp=1/u /bin/ls
lzto@objd ~ $ ~/linux/tools/perf/perf script -F
event,comm,pid,tid,time,addr,ip,sym,dso,iregs
Following segfault can happen with a non-root user:
$ ./perf record -I -e intel_pt/tsc=1,noretcomp=1/u /bin/ls
WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted,
check /proc/sys/kernel/kptr_restrict.
Samples in kernel functions may not be resolved if a suitable vmlinux
In error processing path of intel_pt_process_auxtrace_info() it calls
thread__zput() to clean and free pt->unknown_thread which is created by
thread__new(). However, when error raise, a segfault happen:
# perf script -F event,comm,pid,tid,time,addr,ip,sym,dso,iregs
Samples for 'instructions:u'
The pinctrl of rk3399 is much different from other's,
especially the 3bits of drive strength.
Signed-off-by: David Wu
Reviewed-by: Heiko Stuebner
---
Changes in v5:
- merge the binding-doc-addition in one patch (Linus Heiko)
- fix the comment of bit15 drive setting (Heiko)
Change in v4: None
On Mon, 01 Feb 2016, Kefeng Wang wrote:
Hi Davidlohr,
On 2016/2/1 6:17, Davidlohr Bueso wrote:
On Sat, 30 Jan 2016, Paul E. McKenney wrote:
On 2016/1/28 12:25, Kefeng Wang wrote:
> Insmod locktorture with torture_type=mutex will lead to crash,
You actually want mutex_lock here, we always
Hi Paul,
After merging the rcu tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
In file included from /home/sfr/next/next/include/linux/spinlock_types.h:18:0,
from /home/sfr/next/next/include/linux/spinlock.h:81,
from
On Thu, Jan 28, 2016 at 02:27:44PM +0100, Alexander Potapenko wrote:
> On Thu, Jan 28, 2016 at 1:51 PM, Alexander Potapenko
> wrote:
> >
> > On Jan 28, 2016 8:40 AM, "Joonsoo Kim" wrote:
> >>
> >> Hello,
> >>
> >> On Wed, Jan 27, 2016 at 07:25:10PM +0100, Alexander Potapenko wrote:
> >> > Stack
On Tue, 2016-01-19 at 15:29 +0800, Sascha Hauer wrote:
> Eduardo,
>
> On Mon, Jan 04, 2016 at 03:19:40PM +0100, Sascha Hauer wrote:
> > Hi Eduardo,
> >
> > >
> > > That should remove the policy of computing the maximum from this driver.
> > > Please have a look on the work being done [1] to add
Hi Andy,
Andy Shevchenko 於 2016/1/29 下午 09:41 寫道:
On Fri, 2016-01-29 at 13:50 +0800, Peter Hung wrote:
Andy Shevchenko 於 2016/1/28 下午 07:55 寫道:
I would suggest to rearrange definition block here (and in the rest
of
the functions in entire series) to somehow follow the following
pattern
1)
On Wed, Jan 27, 2016 at 07:25:13PM +0100, Alexander Potapenko wrote:
> Quarantine isolates freed objects in a separate queue. The objects are
> returned to the allocator later, which helps to detect use-after-free
> errors.
>
> Freed objects are first added to per-cpu quarantine queues.
> When a
On 01/31/2016 11:17 AM, Greg Kroah-Hartman wrote:
On Wed, Jan 27, 2016 at 07:21:27PM -0800, Guenter Roeck wrote:
On 01/27/2016 06:23 PM, Guenter Roeck wrote:
On 01/27/2016 10:11 AM, Greg Kroah-Hartman wrote:
-
NOTE:
There are still a lot of pending stable patches in
Hi Heiko,
在 2016/1/30 20:16, Heiko Stuebner 写道:
Hi David,
Am Samstag, 30. Januar 2016, 19:31:57 schrieb David Wu:
Change-Id: Ic1bdb3dc358837e97d7b48dd58be2f8d9d08d766
please no Change-Id, it's missing the Signed-off, and as Linus Walleij said,
the compatible addition to the documentation can
On (01/29/16 21:43), Byungchul Park wrote:
[..]
> +extern int is_console_lock(raw_spinlock_t *lock);
> +
> static void __spin_lock_debug(raw_spinlock_t *lock)
> {
> u64 i;
> @@ -113,11 +115,19 @@ static void __spin_lock_debug(raw_spinlock_t *lock)
> return;
>
As late as Friday, I was planning on talking about how nice it is to
see this new trend of tiny rc2 releases, because there really hadn't
been very many pull requests at all.
But it turns out the pull requests were just heavily skewed to the end
of the week, and 4.5-rc2 isn't particularly small
Hi Davidlohr,
On 2016/2/1 6:17, Davidlohr Bueso wrote:
> On Sat, 30 Jan 2016, Paul E. McKenney wrote:
>
>>> On 2016/1/28 12:25, Kefeng Wang wrote:
>>> > Insmod locktorture with torture_type=mutex will lead to crash,
>
> You actually want mutex_lock here, we always use the _lock suffix, mainly
>
Commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly") always
reports positive value when Apple hardware queries _OSI("Darwin").
But sometimes the users might want to tell the hardware they don't
need the Darwin feature, for example, users may leverage the hardware
to power off the
On 2016/1/31 5:02, Tong Zhang wrote:
reproduce:
lzto@objd ~ $ ~/linux/tools/perf/perf record -I -e
intel_pt/tsc=1,noretcomp=1/u /bin/ls
lzto@objd ~ $ ~/linux/tools/perf/perf script -F
event,comm,pid,tid,time,addr,ip,sym,dso,iregs
Segmentation fault
lzto@objd ~ $
Upon further
On Thu, Jan 28, 2016 at 02:29:42PM +0100, Alexander Potapenko wrote:
> On Thu, Jan 28, 2016 at 1:37 PM, Alexander Potapenko
> wrote:
> >
> > On Jan 28, 2016 8:44 AM, "Joonsoo Kim" wrote:
> >>
> >> On Wed, Jan 27, 2016 at 07:25:07PM +0100, Alexander Potapenko wrote:
> >> > This patch adds KASAN
From: Rik van Riel
After removing __acct_update_integrals from the profile,
native_sched_clock remains as the top CPU user. This can be
reduced by only calling account_{user,sys,guest,idle}_time
once per jiffy for long running tasks on nohz_full CPUs.
This will reduce timing accuracy on
From: Rik van Riel
It looks like all the call paths that lead to __acct_update_integrals
already have irqs disabled, and __acct_update_integrals does not need
to disable irqs itself.
This is very convenient since about half the CPU time left in this
function was spent in local_irq_save alone.
(v3: address comments raised by Frederic)
Running with nohz_full introduces a fair amount of overhead.
Specifically, various things that are usually done from the
timer interrupt are now done at syscall, irq, and guest
entry and exit times.
However, some of the code that is called every single
From: Rik van Riel
When running a microbenchmark calling an invalid syscall number
in a loop, on a nohz_full CPU, we spend a full 9% of our CPU
time in __acct_update_integrals.
This function converts cputime_t to jiffies, to a timeval, only to
convert the timeval back to microseconds before
From: Rik van Riel
Change the indentation in __acct_update_integrals to make the function
a little easier to read.
Suggested-by: Peter Zijlstra
Signed-off-by: Rik van Riel
Acked-by: Frederic Weisbecker
---
kernel/tsacct.c | 51 ++-
1 file
On (02/01/16 10:45), Byungchul Park wrote:
> But avoiding an unnecessary recursive cycle is better than panic(). What I
> handled
> in this patch is the warning case which causes unnecessary lockup and don't
> need to
> happen.
Hello,
correct, that was one of the reasons why I proposed to
On Fri, Jan 29, 2016 at 06:09:01PM +0800, Herbert Xu wrote:
> On Thu, Jan 28, 2016 at 12:19:42PM +0900, Joonsoo Kim wrote:
> >
> > I have tested asynchronous compression APIs in zram and I saw
> > regression. Atomic allocation and setting up SG lists are culprit
> > for this regression. Moreover,
Hi Rob,
Today's linux-next merge of the dt-rh tree got a conflict in:
MAINTAINERS
between commit:
43ed2986476d ("MAINTAINERS: add qcom i2c and spi drivers to list")
from the qcom tree and commit:
e68d7c143a62 ("MAINTAINERS: Add missing platform maintainers for dts files")
from the
On Fri, 2016-01-29 at 21:15 +0800, Daniel Kurtz wrote:
> On Fri, Jan 29, 2016 at 8:24 PM, Horng-Shyang Liao
> wrote:
> > On Fri, 2016-01-29 at 16:42 +0800, Daniel Kurtz wrote:
> >> On Fri, Jan 29, 2016 at 3:39 PM, Horng-Shyang Liao
> >> wrote:
> >> > Hi Dan,
> >> >
> >> > Many thanks for your
Iterating code of /proc/kallsyms calls module_get_kallsym() which grabs
and drops module_mutex internally and returns "struct module *",
module is removed, aforementioned "struct module *" is used in non-trivial
way.
So, grab module_mutex for entire operation like /proc/modules does.
Steps to
On Sun, Jan 31, 2016 at 09:40:08PM +0900, Sergey Senozhatsky wrote:
> On (01/29/16 21:54), Byungchul Park wrote:
> > Hello, Andrew
> >
> > Please take this v5 patch instead of v2 patch, which you took. Or give your
> > opinion.
> >
> > > It causes an infinite recursive cycle when using
4-2015-02-07.cgz-x86_64-rhel-78d1788350477246d516496d8d7684fa80ef7f18-20160131-120638-crvdne-0.yaml"
max_uptime: 1500
initrd: "/osimage/debian/debian-x86_64-2015-02-07.cgz"
bootloader_append:
- root=/dev/ram0
- user=lkp
-
job=/lkp/scheduled/ivb43/bisect_vm-scalability-performance-300s-lru-file-mm
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 7412301b76bd53ee53b860f611fc3b5b1c2245b5 ("Smack: Assign smack_known_web
as default smk_in label for kernel thread's socket")
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Jaegeuk-Kim/f2fs-avoid-multiple-node-page-writes-due-to-inline_data/20160124-041711
commit ea32c36edcf58f8c27653f3e5bc41f8c0b41e235 ("f2fs: avoid multiple node
page writes due to inline_data")
On 29.01.2016 23:50, Arnd Bergmann wrote:
> We cannot select a symbol that has disabled dependencies, so
> we get a warning if we ever enable EXYNOS_THERMAL without
> also turning on THERMAL_OF:
>
> warning: (ARCH_EXYNOS) selects EXYNOS_THERMAL which has unmet direct
> dependencies (THERMAL &&
1 - 100 of 596 matches
Mail list logo
