Hi,
> From: Bastien Nocera [mailto:had...@hadess.net]
> Subject: Re: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet
>
> On Fri, 2016-03-04 at 03:37 +, Zheng, Lv wrote:
>
> >
> > > I'm not happy about the "fix" for this problem either, but blaming
> > > user-space for this i
2016-03-22 6:02 GMT+09:00 Greg KH :
> On Mon, Mar 14, 2016 at 01:28:01PM +0900, Daeseok Youn wrote:
>> Signed-off-by: Daeseok Youn
>
> Your subject: does not make sense, and I can't take a patch without any
> changelog entry :(
ok. I will add comment to changelog entry and resend this.
Thanks.
r
Hi Tadeusz,
thank you very much for your quick reply!
Tadeusz Struk writes:
> On 03/21/2016 06:26 AM, Nicolai Stange wrote:
>> This is a resend of v2 with the crypto people properly CC'd.
>>
>> The original v1 can be found here:
>>
>>
>> http://lkml.kernel.org/g/1458237606-4954-1-git-send-
On Mon, Mar 21, 2016 at 05:40:30PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 21, 2016 at 09:08:52AM +0100, Jiri Olsa escreveu:
> > On Fri, Mar 18, 2016 at 02:38:52PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Mar 18, 2016 at 12:16:23PM -0500, Josh Poimboeuf escreveu:
> > > > So
> Bandan Das wrote on 03/21/2016 07:43:41 PM:
> > "Michael Rapoport" writes:
> >
> > Hi Bandan,
> >
> >> From: Bandan Das
> >>
> >> At Linuxcon last year, based on our presentation "vhost: sharing is
> > better" [1],
> >> we had briefly discussed the idea of cgroup aware workqueues with
Teju
2016-03-22 6:05 GMT+09:00 Greg KH :
> On Mon, Mar 14, 2016 at 01:28:31PM +0900, Daeseok Youn wrote:
>> For using tty_alloc_driver, SerialDriver has to be pointer type.
>
> Yes, but you aren't calling tty_alloc_driver, so this patch totally
> breaks the working code :(
yes.. my changelog was NOT goo
Hi,
On Wed, Mar 09, 2016 at 04:44:01PM +0100, Hans de Goede wrote:
> Hi,
>
> On 09-03-16 16:28, Maxime Ripard wrote:
> >Hi,
> >
> >On Wed, Mar 09, 2016 at 01:17:50PM +0100, Hans de Goede wrote:
> >>Hi,
> >>
> >>On 09-03-16 11:50, Maxime Ripard wrote:
> >>>Hi,
> >>>
> >>>The axp209 PMIC used in co
From: Yinghai Lu
real_mode is global variable, so we do not need to pass it around.
Signed-off-by: Yinghai Lu
Acked-by: Kees Cook
---
arch/x86/boot/compressed/aslr.c | 5 ++---
arch/x86/boot/compressed/misc.c | 2 +-
arch/x86/boot/compressed/misc.h | 6 ++
3 files changed, 5 insertions(+)
***Background:
Previously a bug is reported that kdump didn't work when kaslr is enabled.
During
discussing that bug fix, we found current kaslr has a limilation that it can
only randomize in 1GB region.
This is because in curent kaslr implementaion only physical address of kernel
loading is rand
From: Yinghai Lu
We are going to support kaslr with 64bit above 4G, and new random output
could be anywhere. Array mem_avoid is used for kaslr to search new output
address. Current code has first entry which is extra bytes before
input+input_size, and it is according to output_size. But we need t
When process 32 bit relocation tables a local variable 'extended'
is defined to calculate the physical address of relocs entry.
However its type is 'int' which is enough for i386, but not enough
for x86_64. That's why relocation can only be handled under 2G.
Otherwise a overflow will happen and cau
Function store_slot_info() is used to calculate the slot info of passed
in memory region and store it into slot_areas[].
Function mem_min_overlap is used to iterate all avoid regions to find the
one which overlap with it in the lowest address. E.g there's a memory
region[1024M, 2048M), after itera
From: Yinghai Lu
parse_elf is using local memcpy to move section to running position.
That memcpy actually only support no overlapping case or when dest < src.
Add checking in memcpy to find out the wrong case for future use, at
that time we will need to have backward memcpy for it.
Signed-off-
From: Yinghai Lu
Current aslr only support random in small range, from 16M to 1G. And
new range still use old mapping. Also it does not support new range
above 4G.
We need to have ident mapping for the new range before we can do
decompress to the new output, and later run them.
In this patch,
From: Yinghai Lu
For better understanding clarify what are VO and ZO firstly. They are
introduced in below commits by hpa.
77d1a49 x86, boot: make symbols from the main vmlinux available
37ba7ab x86, boot: make kernel_alignment adjustable; new bzImage fields
VO:
- uncompressed kernel
- size: VO_
From: Yinghai Lu
We need to include that in boot::decompress_kernel stage to set new
ident mapping.
Also add checking for __pa/__va macro definition, as we need to override them
in boot::decompress_kernel stage.
Reviewed-by: Kees Cook
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/page.h
Kernel is expected to be randomly reloaded anywhere in the whole
physical memory area, it could be near 64T at most. In this case
there could be about 4*1024*1024 randomization slots if
CONFIG_PHYSICAL_ALIGN is 0x100. Currently the starting address
of candidate position is stored into array slo
From: Yinghai Lu
Current z_extract_offset is calculated in boot/compressed/mkpiggy.c. The
problem is in mkpiggy.c we don't know the detail of decompressor. Then
we just get a rough z_extract_offset according to extra_bytes. As we know
extra_bytes can only promise a safety margin when decompressin
Several auxiliary functions and slots[] are not needed any more since
struct slot_area and new algorithm is used instead now. Hence remove
them in this patch.
Signed-off-by: Baoquan He
---
arch/x86/boot/compressed/aslr.c | 24
1 file changed, 24 deletions(-)
diff --git
Hi,
On Tue, Mar 22, 2016 at 3:22 PM, Maxime Ripard
wrote:
> Hi,
>
> On Wed, Mar 09, 2016 at 04:44:01PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> On 09-03-16 16:28, Maxime Ripard wrote:
>> >Hi,
>> >
>> >On Wed, Mar 09, 2016 at 01:17:50PM +0100, Hans de Goede wrote:
>> >>Hi,
>> >>
>> >>On 09-03-16 1
From: Yinghai Lu
Now new randomized output can only be chosen from regions above loaded
address. In this case, for bootloaders like kexec which always loads
kernel near the end of ram, it doesn't do randomization at all. Or kernel
is loaded in a very big starting address, we should not give up th
In kaslr implementation mechanism, process_e820_entry and
slots_fetch_random are 2 key functions.
process_e820_entry is used to parse passed in memory region and
store available slot area information into array slot_areas[].
slots_fetch_random is used to get a random value and translate
it into st
Kaslr extended kernel text mapping region size from 512M to 1G,
namely CONFIG_RANDOMIZE_BASE_MAX_OFFSET. This means kernel text
can be mapped to below region:
[__START_KERNEL_map + LOAD_PHYSICAL_ADDR, __START_KERNEL_map + 1G]
Introduce a function find_random_virt_offset() to get random value
betw
The old code uses CONFIG_RANDOM_OFFSET_MAX to get the offset max for kernel
virtual randomization, and CONFIG_RANDOM_OFFSET_MAX is a configurable value
within the scope of [512M, 1G] on x86_64. Currently CONFIG_RANDOM_OFFSET_MAX
always defaults to 1G, and seems no obvious benefit to make it configu
On x86_64, in old kaslr implementaion only physical address of kernel
loading is randomized. Then calculate the delta of physical address
where vmlinux was linked to load and where it is finally loaded. If
delta is not equal to 0, namely there's a new physical address where
kernel is actually decom
Current analysis is only for gzip decompressor only. In fact we can
support 6 different decompressor. Update the description to cover
all of them. Meanwhile fix several typos.
Signed-off-by: Baoquan He
---
arch/x86/boot/compressed/misc.c | 26 +-
1 file changed, 17 insert
From: Yinghai Lu
Relocation handling performs bounds checking on the relocated
addresses. The existing code uses output_len (VO size plus relocs
size) as the max address. This is not right since the max_addr check
should stop at the end of VO and exclude bss, brk, etc, which follows.
The valid ra
From: Yinghai Lu
Firstly, current run_size is calculated via shell script
arch/x86/tools/calc_run_size.sh. It gets file offset and mem size of section
.bss and .brk in vmlinux, then add them as follows:
run_size=$(( $offsetA + $sizeA + $sizeB ))
However this is completely wrong. The offset is t
From: Yinghai Lu
So now we use the formula below to get run_size.
run_size = VO__end - VO__text
Let's remove code for old run_size calculation and clean up the places
where run_size need be passed in and out.
Cc: "H. Peter Anvin"
Cc: Josh Triplett
Cc: Kees Cook
Cc: Andrew Morton
Cc
2016-03-22 6:05 GMT+09:00 Greg KH :
> On Mon, Mar 14, 2016 at 01:29:00PM +0900, Daeseok Youn wrote:
>> the tty_alloc_driver() can allocate memory for ttys and termios.
>> And also it can release allocated memory easly with using
>> put_tty_driver().
>>
>> Signed-off-by: Daeseok Youn
>
> But you br
CCing lkml this time. Hope it's the right way...
For patch 1, it only drops one printf(), which is optional.
For patch 2, it tries to dump more information when we got errors,
and also catches some silence ones.
Peter Xu (2):
trace-cmd-listen: remove useless printf
trace-recorder: better err
This line is useless since we will get more verbose info in
do_connection(). Another problem is, we will get this "connected!" line
everytime after we hit "ctrl-c" for "trace-cmd listen". We possibly do
not want that.
Signed-off-by: Peter Xu
---
trace-listen.c | 1 -
1 file changed, 1 deletion(-
Currently we have two ways to copy data, one is splice, one is read +
write. For both, dump more information when we got errors during the
copy. Also, when we update_fd(), we should make sure all bytes written,
and update written bytes only.
These information might be important to better diagnose
On (03/22/16 15:57), Byungchul Park wrote:
> On Tue, Mar 22, 2016 at 02:52:43PM +0900, Sergey Senozhatsky wrote:
> > On (03/22/16 11:13), Byungchul Park wrote:
> > [..]
> >
> > what about a "normal" case, when things are not going to explode printk(),
> > but we have several lockups on the same lo
From: Kejian Yan
Both .get_rxfh and .set_rxfh are always return 0, it should return result
from hardware when getting or setting rss. And the rss function should
return the correct data type.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
PATCH V2:
- fix the wrong cas
From: Daode Huang
When set MTU to the minimum value 68, there are increasing number
of error packets occur, which is caused by the overflowed value of
mss. This patch fix the bug.
Signed-off-by: Daode Huang
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns/hns_enet.c | 17 +++
From: Kejian Yan
Debug ports receives lots of packets with dest mac addr does not match
local mac addr, because the filter is close, and it does not drop the
useless packets. This patch adds ON/OFF switch of filtering the packets
whose dest mac addr do not match the local addr in mac table. And
From: Kejian Yan
The current upstreaming code fails to ping other IPv6 net device, because
the enet receives the multicast packets with the src mac addr which is the
same as its mac addr. These packets need to be dropped.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
P
From: Sheng Li
When sending a pause frame out from GMACs, the packets' source MAC address
does not match the GMACs' MAC address. It causes by the condition before
the mac address setting routine for GMACs, the mac address cannot be set
into loacal mac table for service ports. It obviously the con
From: Kejian Yan
If trying to get receive flow hash indirection table by ethtool, it needs
to call .get_rxnfc to get ring number first. So this patch implements the
.get_rxnfc of ethtool. And the data type of rss_indir_table is u32, it has
to be multiply by the width of data type when using memcp
This series includes some bug fixes and updates for hns driver.
>from Daode, one fix about mss.
>from Kejian, one fix about ping6 issue, one fix about mac address setting,
two fix for RSS setting, two fix about mtu setting.
>from qianqian, fixed HNS v2 xge statistic reg issue.
>from Sheng, one
From: Kejian Yan
In chip V1, the maximum mtu value is 9600. But in chip V2, it is 9728.
And it is always configurates as 9600 before this patch.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns/hns_dsaf_mac.c | 4 +++-
drivers/net/ethernet/hisilicon
From: Qianqian Xie
As the user manual of HNS V2 describs, XGE_DFX_CTRL_CFG.xge_dfx_ctrl_cfg
should be configed as zero if we want xge statistic reg to be read only.
But HNS V1 gets the other meanings. It needs to be identified the process
and then config it rightly.
Signed-off-by: Qianqian Xie
On Tue, Mar 08, 2016 at 08:52:32PM +0100, Rasmus Villemoes wrote:
> On Tue, Nov 24 2015, Rasmus Villemoes wrote:
>
> > This reduces the impact of choosing CONFIG_SCSI_CONSTANTS by about 8KB.
> >
>
> ping? does anyone feel like picking these up?
Please resend them against the current tree. I'm
From: Sheng Li
In chip V2, the default value of port id in tx BD is Zero. If it is not
configurated to the other value, all management packets will be sent out
from port0. So port_id in the tx BD needs to be updated when sending a
management packet.
In V2 chip, when sending mamagement packets, t
From: Kejian Yan
If mtu for debug port is set more than 1500, it may cause that packets
are dropped by ppe. So maximum value for debug port should be 1500.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
PATCH V2:
- use tabs instead of spaces to indent the value
PATC
Hello Jan,
On (03/22/16 07:49), Jan Kara wrote:
> Hi,
>
> On Tue 22-03-16 02:25:28, Sergey Senozhatsky wrote:
> > The patch set is based on slightly updated Jan Kara's patches.
> >
> > This patch set makes printk() completely asynchronous: new messages
> > are getting upended to the kernel prin
On Fri, Mar 18, 2016 at 11:03:47PM +0800, Peter Zijlstra wrote:
> It turns out AMD gets x86_max_cores wrong when there are compute
> units.
>
> The issue is that Linux assumes:
>
> nr_logical_cpus = nr_cores * nr_siblings
>
> But AMD reports its CU unit as 2 cores, but then sets num_smp_si
On Mon, Mar 21, 2016 at 08:56:32AM -0700, Andi Kleen wrote:
SNIP
> +EVENT GROUPS
> +
> +
> +Perf supports time based multiplexing of events, when the number of events
> +active exceeds the number of hardware performance counters. Multiplexing
> +can cause measurement errors when the w
On Mon, Mar 21, 2016 at 08:56:33AM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Correctly document what is implemented for :ppp on Intel CPUs in
> recent kernels.
>
> Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
thanks,
jirka
On Tue, Mar 22, 2016 at 02:08:59PM +0900, Joonsoo Kim wrote:
> On Fri, Mar 18, 2016 at 04:58:31PM +0900, Minchan Kim wrote:
> > "remove compressed copy from zram in-memory"
> > applied swap_slot_free_notify call in *end_swap_bio_read* to
> > remove duplicated memory between zram and memory.
> >
>
On 21.03.2016 21:34, Ivaylo Dimitrov wrote:
On 21.03.2016 16:53, Sebastian Reichel wrote:
Hi Mark,
On Mon, Mar 21, 2016 at 01:45:15PM +, Mark Brown wrote:
On Mon, Mar 21, 2016 at 03:39:15PM +0200, Ivaylo Dimitrov wrote:
On 21.03.2016 13:45, Mark Brown wrote:
No, if the voltage is v
On 03/21/2016 06:34 PM, Heiner Kallweit wrote:
Am 21.03.2016 um 16:35 schrieb Jacek Anaszewski:
On 03/19/2016 08:11 PM, Heiner Kallweit wrote:
Am 18.03.2016 um 14:10 schrieb Jacek Anaszewski:
On 03/17/2016 08:53 PM, Heiner Kallweit wrote:
Am 17.03.2016 um 14:41 schrieb Jacek Anaszewski:
Hi H
Hi Lukas,
> Try booting with: pcie_hp=nomsi
I gave this a shot but unfortunately resulted in no change in behaviour
- the device is still not detected if it is connected after boot, and
nothing shows in dmesg upon connection.
Kind regards,
Jack
signature.asc
Description: OpenPGP digital sig
On 03/21/2016, 04:58 PM, Jiri Slaby wrote:
> Hello,
>
> On 03/18/2016, 09:52 PM, Tejun Heo wrote:
>> On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote:
> I have not done that yet, but today, I see:
> destroy_workqueue: name='req_hci0' pwq=88002f590300
> wq->dfl_pwq=880
On Fri, Mar 18, 2016 at 02:33:45PM +0100, Arnd Bergmann wrote:
> The openvswitch code has gained support for calling into the
> nf-nat-ipv4/ipv6 modules, however those can be loadable modules
> in a configuration in which openvswitch is built-in, leading
> to link errors:
>
> net/built-in.o: In fu
Паролата ви ще изтече в следващите 24 часа, за да се избегне това
кликнете върху == на линк> http://mailservice-bg.dudaone.com/ представят
вашите данни за актуализиране на вашия имейл акаунт за 2016: да
потвърдиш Е-поща и получи Нови съобщения.
Благодаря
Системен администратор. © 2016 Всички пр
Hi Andreas,
> That is correct. On your device TB should be handled by the firmware.
>
> Björn suggested that we might not be reacting to acpi notifications
> (or pci hotplug interrupts) properly. To confirm this you could try to
> issue a manual pci rescan via
>
> echo "1" > /sys/bus/pci/rescan
>
On 03/21/2016 08:57 AM, Borislav Petkov wrote:
+- AMD: the number of cores in a processor. On a system where cores are
+clustered in groups of 2, 4 or more in compute units, this variable
+denotes the number of*compute units* on the node.
+
+In both cases, the number of scheduling threads is com
Remove extra article and blank.
---
Documentation/ABI/testing/sysfs-class-net | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-class-net
b/Documentation/ABI/testing/sysfs-class-net
index 668604f..83f7894 100644
--- a/Documentation/ABI/testing
On Tue 22-03-16 16:57:38, Sergey Senozhatsky wrote:
> : hardlockup detector with sysctl_hardlockup_all_cpu_backtrace.
> :
> : static void watchdog_overflow_callback(...)
> : {
> : ...
> : if (is_hardlockup()) {
> : ...
> : if (sysctl_hardlockup_all_cpu_backtr
On Tue, Mar 22, 2016 at 06:31:54AM +0100, Borislav Petkov wrote:
> On Mon, Mar 21, 2016 at 09:42:09PM +, Chris Bainbridge wrote:
> > Hi,
> >
> > I was testing something on an old server (Dell T105 opteron) and noticed
> > packet loss after updating the kernel from 3.10 to 4.5. The test was:
>
2016-03-22 17:00 GMT+09:00 Minchan Kim :
> On Tue, Mar 22, 2016 at 02:08:59PM +0900, Joonsoo Kim wrote:
>> On Fri, Mar 18, 2016 at 04:58:31PM +0900, Minchan Kim wrote:
>> > "remove compressed copy from zram in-memory"
>> > applied swap_slot_free_notify call in *end_swap_bio_read* to
>> > remove du
Hi Heiner,
On 03/21/2016 06:24 PM, Heiner Kallweit wrote:
Add generic support for RGB LED's.
Basic idea is to use enum led_brightness also for the hue and saturation
color components.This allows to implement the color extension w/o
changes to struct led_classdev.
Select LEDS_CLASS_RGB to enabl
Hi Bjorn,
> Can you open a report at http://bugzilla.kernel.org, category
> drivers/PCI, and attach complete "lspci -vv" output (run as root) and
> complete dmesg logs, both when hub is attached at boot, and when
> booting without hub and attaching hub later?
>
> I don't know much about Thunderbol
On Mon, 21 Mar 2016, Andi Kleen wrote:
> On Mon, Mar 21, 2016 at 03:08:46PM -0700, Andy Lutomirski wrote:
> > On Mon, Mar 21, 2016 at 3:05 PM, Andi Kleen wrote:
> > >> Please add a patch before this one that renames gs to gsbase. This is
> > >> unreadable as is.
> > >
> > > I investigated this no
Current code show stats of online cpus in cpuacct.statcpus,
show stats of present cpus in cpuacct.usage(_percpu), and using
present cpus for setting cpuacct.usage.
It will cause inconsistent result when a cpu is online or offline
or hotpluged.
We should always use possible cpus to avoid above pro
Sometimes, cpuacct.usage is not detialed enough to user
to see how much usage a group used. We want to know how
much time it used in user mode and how much in kernel mode.
This patch introduce some more files to tell user these information.
# ls /sys/fs/cgroup/cpuacct/cpuacct.usage*
/sys/fs/cgro
From: Yang Dongsheng
The name of 'reset' makes a little confusion in reading, we would
say, if we want to reset usage, return -EINVAL. That's not true.
Actually, we want to say, we only allow user to do a reset. This
patch rename reset to val and add a comment here, making the code
more readable
1: Use for() instead of while() loop in some functions
to make code simple.
2: Use this_cpu_ptr() instead of per_cpu_ptr() to make code
clean with little performance up.
Suggested-by: Peter Zijlstra
Signed-off-by: Zhao Lei
---
kernel/sched/cpuacct.c | 28 +---
kern
From: Dongsheng Yang
Sometimes, cpuacct.usage is not detialed enough to user
to see how much usage a group used. We want to know how
much time it used in user mode and how much in kernel mode.
This patch introduce some more files to tell user these information.
# ls /sys/fs/cgroup/cpuacct/cpuac
Hi,
There is a question about CPU usage limitation and I found no place
for my question other than here.
There are 32 cores in a system (2 cpus each 16 cores) and I want to
limit a user to use only 4 cores (100% usage for that 4 cores). There
are two kernel parameter for that according to the manu
On Tue, Mar 22, 2016 at 08:57:35AM +0100, Jiri Olsa wrote:
> > +Events from multiple different PMUs cannot be mixed in a group.
>
> hum, but we allow that right?
>
> only when there's mixture of SW and HW events we move
> it all silently under HW event context
I forgot the exact details, but we
Tony,
On 03/21/16 22:21, Tony Lindgren wrote:
> Hi,
>
> * Peter Ujfalusi [160321 01:39]:
>>
>> This is also interesting:
>> McBSP2 sidetone is in region 39 and 40 (module and L4 interconnect) which is
>> unique in case of OMAP34xx and OMAP35xx, but it is overlapping with GPIO6 on
>> OMAP36xx. No
On Mon, Mar 21, 2016 at 03:38:21PM -0400, Kroah-Hartman wrote:
hi,
On Sat, Mar 12, 2016 at 03:40:35AM -0500, YU Bo wrote:
Fix comments to use trailing */ on separste lines.
Signed-off-by: YU BO
---
drivers/staging/xgifb/vb_init.c|3 ++-
drivers/staging/xgifb/vb_setmode.c |3 ++-
2 fi
On Mon, Mar 21, 2016 at 11:23:39AM -0400, Steven Rostedt wrote:
>
> Signed-off-by: Steven Rostedt
What tree is this against? It does not apply.
fix the checkpatch.pl warning about CamelCase.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_driver.h | 4 +-
drivers/staging/dgnc/dgnc_tty.c| 118 ++---
2 files changed, 61 insertions(+), 61 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_d
On 03/17/2016 08:21 PM, Robin Murphy wrote:
> On 17/03/16 19:00, Rob Herring wrote:
>> On Thu, Mar 17, 2016 at 1:06 PM, Robin Murphy wrote:
>>> Hi Rob,
>>>
>>> On 17/03/16 17:09, Rob Herring wrote:
That would not be an SP804 nor would the vendor be ARM in that case. So
add a new compatib
On Tue, Feb 16, 2016 at 9:02 AM, Sudip Mukherjee
wrote:
> We were getting build warning about:
> fs/btrfs/extent-tree.c:7021:34: warning: ‘used_bg’ may be used
> uninitialized in this function
>
> It is not a valid warning as used_bg is never used uninitilized since
> locked is initially f
Fixed spelling error.
Signed-off-by: Alok Mistry
---
arch/powerpc/mm/hash64_64k.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/hash64_64k.c b/arch/powerpc/mm/hash64_64k.c
index b2d659c..fe89a6d 100644
--- a/arch/powerpc/mm/hash64_64k.c
+++ b/arch/powerpc/mm/
On Tue, Mar 22, 2016 at 04:37:04PM +0800, Zhao Lei wrote:
> Sometimes, cpuacct.usage is not detialed enough to user
> to see how much usage a group used. We want to know how
> much time it used in user mode and how much in kernel mode.
>
> This patch introduce some more files to tell user these in
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Monday, March 21, 2016 12:52 AM
>> To: KY Srinivasan
>> Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; Haiyang
>> Zhang ; Alex Ng (LIS) ;
>> Radim Krcmar ; Cathy A
On 21/03/16 17:51, Mark Brown wrote:
> On Mon, Mar 21, 2016 at 05:24:52PM +, Juri Lelli wrote:
>
> > I think this should work, but we have to understand how do we obtain the
> > max frequency of each cluster while parsing DT. OPP bindings are
> > helpful, but AFAIK there are platforms for whic
On some QOCM platforms(eg 8996) BAM control registers are managed remotely
hence can not be accessed by application processor for writes. So skip the
bam_init
for any such platform if DT property is set.
Tested on 8996 (BAM Global control is through remote) and DB410C boards.
Tested with i2c DMA
Clear the BAM IRQ bit only if there is a BAM interrupt.
Signed-off-by: Pramod Gurav
---
drivers/dma/qcom/bam_dma.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/qcom/bam_dma.c b/drivers/dma/qcom/bam_dma.c
index d5e0a9c..0880345 100644
--- a/drivers/dma/qcom/ba
On some QOCM platforms BAM control registers are managed remotely
hence can not be accessed by application processor for writes. Pass
a DT property qcom,bam_ctrl_remote to declare the same to skip bam_init.
Move the pipe number initialisation from bam_init to probe functiom
as it should be done fo
On 03/22/2016 06:40 AM, Antony Pavlov wrote:
> On Tue, 22 Mar 2016 00:02:57 +0100
> Matthias Schiffer wrote:
>
>> Hi,
>> we're experiencing weird nondeterministic hangs during bootconsole/console
>> handover on some ath79 systems on OpenWrt. I've seen this issue myself on
>> kernel 3.18.23~3.18.2
On Mon, 2016-03-21 at 15:30 -0400, Alan Stern wrote:
> On Mon, 21 Mar 2016, Oliver Neukum wrote:
>
> > We have an autosuspend timeout because we think that IO, if it will
> > come at all, is likeliest to come soon. If, however, the IO is
> > periodic that heuristics is false.
> > To save most pow
Kirill Marinushkin wrote:
> For details see
> Documentation/security/keys-derived.txt
Usage?
David
'struct timeval' uses a 32-bit seconds field which will overflow in
year 2038 and beyond. This patch is part of a larger effort to remove
all instances of 'struct timeval' from the kernel and replace them
with 64-bit timekeeping variables.
The correctness of the code isn't affected by this patch -
On 03/22/2016 11:49 AM, Pramod Gurav wrote:
> On some QOCM platforms(eg 8996) BAM control registers are managed remotely
> hence can not be accessed by application processor for writes. So skip the
> bam_init
> for any such platform if DT property is set.
>
> Tested on 8996 (BAM Global control is
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Monday, March 21, 2016 1:19 AM
>> To: KY Srinivasan
>> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
>> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical
On Mon, Mar 21, 2016 at 11:19:02PM -0400, Waiman Long wrote:
> Instead, the subject was
>
> [lkp] [locking/mutex] 5267438002: +38.9%
> fileio.time.involuntary_context_switches
>
> 4409 ± 1% +38.9% 6126 ± 2%
> fileio.time.involuntary_context_switches
> 6.00 ± 0% +33.3%
On Tue, Mar 22, 2016 at 10:39:59AM +0100, Geert Uytterhoeven wrote:
> On Tue, Feb 16, 2016 at 9:02 AM, Sudip Mukherjee
> wrote:
> > We were getting build warning about:
> > fs/btrfs/extent-tree.c:7021:34: warning: ‘used_bg’ may be used
> > uninitialized in this function
> >
> > It is not a
Martin,
This patch is being reviewed , we shall get back with reviews by
tomorrow.
Thanks,
Chaitra
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Tuesday, March 22, 2016 6:00 AM
To: Calvin Owens
Cc: Sathya Prakash; Chaitra P B; Suganath Prabu Subra
On Tue, Mar 22, 2016 at 06:39:51AM +, Lakshmi Sai Krishna Potthuri wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to. Please also avoid reflowing other text
into l
Current code fails to ignore the 'hugepages=' parameters when unsupported
hugepagesize is specified. With this patchset, introduce new architecture
independent routine hugetlb_bad_size to handle such command line options. And
then call it in architecture specific code.
Vaishali Thakkar (2):
mm/h
Hi,
as Paolo has merged the test into kvm-unit-tests, this patch (and
original bug) can be now tested with it.
git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
at least:
be9b007 powerpc: add test to check invalid instruction trap
Run this with KVM-PR and check your dmesg:
qemu
Update the setup_hugepagesz function to call the routine
hugetlb_bad_size when unsupported hugepage size is found.
Misc:
- Silent 80 characters warning
Signed-off-by: Vaishali Thakkar
Cc: Mike Kravetz
Cc: Naoya Horiguchi
Cc: Hillf Danton
Cc: Michal Hocko
Cc: Yaowei Bai
Cc: Dominik Dingel
When any unsupported hugepage size is specified, 'hugepagesz=' and
'hugepages=' should be ignored during command line parsing until any
supported hugepage size is found. But currently incorrect number of
hugepages are allocated when unsupported size is specified as it fails
to ignore the 'hugepages
1 - 100 of 880 matches
Mail list logo
