Some platforms have the capability to configure the performance state of
PM domains. This patch enhances the genpd core to support such
platforms.
The performance levels (within the genpd core) are identified by
positive integer values, a lower value represents lower performance
state.
This patch
On 2017-10-11 16:33:24 [-0500], Kim Phillips wrote:
> Unregistering the driver before calling cpuhp_remove_multi_state() removes
> any remaining hotplug cpu instances so __cpuhp_remove_state_cpuslocked()
> doesn't emit this warning:
…
> Fixes: 8df038725ad5 ("bus/arm-ccn: Use cpu-hp's multi instance
On Thu, Oct 12, 2017 at 1:23 AM, Andrew Morton
wrote:
> On Wed, 11 Oct 2017 16:22:22 +0800 Abbott Liu wrote:
>
>> Because arm instruction set don't support access the address which is
>> not aligned, so must change memory_is_poisoned_16 for arm.
>>
>> ...
>>
>> --- a/mm/kasan/kasan.c
>> +++ b/m
* Andi Kleen wrote:
> From: Andi Kleen
>
> Move the XSAVE initialization code to be after parsing early parameters.
> I don't see any reason why the FPU code needs to be initialized that
> early, nothing else in the initialization phase uses XSAVE.
> This is useful to be able to handle command
Hi
On Mon, Oct 09, 2017 at 07:50:53PM +0200, Andrey Konovalov wrote:
> I've got the following report while fuzzing the kernel with syzkaller.
>
> On commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f (4.14-rc4).
>
> I'm not sure whether this is a bug in the driver, or just a way to
> report misbeha
On Wed, Oct 11, 2017 at 10:51 PM, Jin Qian wrote:
> From: Jin Qian
>
> Expose emmc revision as part of device attributes.
>
> Signed-off-by: Jin Qian
So have you tried and seen what happens with an MMC that
is not an eMMC, i.e. a good old MMC card from back in the days?
Does it display all ze
On Wed, Oct 11, 2017 at 10:22 AM, Abbott Liu wrote:
> Hi,all:
>These patches add arch specific code for kernel address sanitizer
> (see Documentation/kasan.txt).
Nice!
When I build-tested KASAN on x86 and arm64, I ran into a lot of build-time
regressions (mostly warnings but also some errors
On Wed, Oct 11, 2017 at 01:48:00PM +0100, Jean-Philippe Brucker wrote:
> I wonder if SVM originated in OpenCL first, rather than intel? That's why
> I'm using it, but it is ambiguous. I'm not sure IOVM is precise enough
> though, since the name could as well be used without shared tables, for
> cla
Hello Dmitry,
On 10/11/2017 11:08 PM, Dmitry Osipenko wrote:
> Add a device node for the video decoder engine found on Tegra20.
>
> Signed-off-by: Dmitry Osipenko
> ---
> arch/arm/boot/dts/tegra20.dtsi | 17 +
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dt
On Wed, Oct 11, 2017 at 04:14:30PM -0400, Waiman Long wrote:
> > kern :warn : [0.00] WARNING: CPU: 0 PID: 0 at
> > kernel/jump_label.c:161 static_key_disable_cpuslocked+0x69/0x80
> > kern :warn : [0.00] static_key_disable+0x1a/0x30
> > kern :warn : [0.00] native_p
On Thu, Oct 12, 2017 at 9:32 AM, Linus Walleij wrote:
> I think it is by far a better idea that Android start to read out these
> things using the ioctl() operation and cut this sysfs business.
But hey, too early in the morning. It's just the revision of the extcsd
that is being exposed. That's
Anju T Sudhakar writes:
> On Wednesday 11 October 2017 01:55 AM, Stewart Smith wrote:
>> Michael Ellerman writes:
>>> Anju T Sudhakar writes:
>>>
Add a kernel command line parameter option to disable In-Memory Collection
(IMC) counters and add documentation. This helps in debug.
>>> I'
In pcie-designware.c many places we are calling "usleep_range" which
are in atomic context. This patch fixes these potential BUGs and
replaces "usleep_range" with mdelay calls.
Signed-off-by: Pankaj Dubey
---
drivers/pci/dwc/pcie-designware.c | 8
drivers/pci/dwc/pcie-designware.h | 3 +
On Tue, Oct 10, 2017 at 03:51:37PM +0900, Byungchul Park wrote:
> The workqueue added manual acquisitions to catch deadlock cases.
> Now crossrelease was introduced, some of those are redundant, since
> wait_for_completion() already includes the acquisition for itself.
> Removed it.
I think manual
On Wed 11-10-17 12:03:59, Shakeel Butt wrote:
> The allocations from filp cache can be directly triggered by user
> space applications. A buggy application can consume a significant
> amount of unaccounted system memory. Though we have not noticed
> such buggy applications in our production but upo
On Tue, Oct 10, 2017 at 03:44:04PM +0900, Byungchul Park wrote:
> Currently, migrating tasks to cpu0 unconditionally happens when the
> heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0).
> We have to distinguish between the empty case and cpu0 to avoid the
> unnecessary migrantion
On 10/10/2017 1:50 AM, John Stultz wrote:
> On Tue, Oct 3, 2017 at 2:58 AM, Minas Harutyunyan
> wrote:
>>
>> Could you please apply patch from Vardan Mikayelyan "usb: dwc2: Fix
>> dwc2_hsotg_core_init_disconnected()" submitted at 02/25/2017
>> (https://urldefense.proofpoint.com/v2/url?u=https-3A__
On 11/10/17 09:22, Abbott Liu wrote:
> From: Andrey Ryabinin
>
> This patch initializes KASan shadow region's page table and memory.
> There are two stage for KASan initializing:
> 1. At early boot stage the whole shadow region is mapped to just
>one physical page (kasan_zero_page). It's fini
On Tue, Oct 10, 2017 at 03:37:52PM +0900, Byungchul Park wrote:
Any problem with this? Peter, you suggested and I implemented it.
Did I do in a wrong way?
> Change from v10
>-. modify a comment a bit as Steven suggested
>
> Change from v9
>-. modify a comment a bit so to be more clear as
On 12 October 2017 at 09:09, Viresh Kumar wrote:
> Some platforms have the capability to configure the performance state of
> PM domains. This patch enhances the genpd core to support such
> platforms.
>
> The performance levels (within the genpd core) are identified by
> positive integer values,
Hi,
Thanks for the report.
On Thu, 2017-10-12 at 14:19 +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: cd1a0cdbf9ada9bb975d8730a375bc13824ef065 ("mac80211: aead api to
> reduce redundancy")
I guess the commit isn't actually an upstream com
On Thursday 12 October 2017 01:21 PM, Stewart Smith wrote:
Anju T Sudhakar writes:
On Wednesday 11 October 2017 01:55 AM, Stewart Smith wrote:
Michael Ellerman writes:
Anju T Sudhakar writes:
Add a kernel command line parameter option to disable In-Memory Collection
(IMC) counters and a
On Wed, Oct 11, 2017 at 09:12:34PM +0300, Alexey Dobriyan wrote:
> On Tue, Oct 10, 2017 at 03:08:06PM -0700, Andrei Vagin wrote:
> > On Sun, Sep 24, 2017 at 11:06:20PM +0300, Alexey Dobriyan wrote:
> > > From: Aliaksandr Patseyenak
> > >
> > > Implement system call for bulk retrieveing of opened
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 05/10/17 15:06, Arnd Bergmann wrote:
> The new backlight code causes a link failure when backlight
> support itself is disabled:
>
> drivers/gpu/drm/omapdrm/display
* Andi Kleen wrote:
> --- /dev/null
> +++ b/arch/x86/kernel/cpu/cpuid-deps.c
> @@ -0,0 +1,109 @@
> +/* Declare dependencies between CPUIDs */
> +#include
> +#include
> +#include
> +#include
> +
> +struct cpuid_dep {
> + unsigned short feature;
> + unsigned short depends;
> +};
Why a
On Wed, Oct 11, 2017 at 3:58 PM, Ulf Hansson wrote:
> Actually completing the request in the ->done callback, may still be
> possible, because in principle it only needs to inform the other
> prepared request that it may start, before it continues to post
> process/completes the current one.
I t
* Andi Kleen wrote:
> From: Andi Kleen
>
> Make clearcpuid= an early param, to make sure it is parsed
> before the XSAVE initialization. This allows to modify
> XSAVE state by clearing specific CPUID bits.
>
> Reviewed-by: Thomas Gleixner
> Signed-off-by: Andi Kleen
> ---
> arch/x86/kernel
On Wed, 2017-10-11 at 22:33 +0100, Kim Phillips wrote:
> Unregistering the driver before calling cpuhp_remove_multi_state()
> removes
> any remaining hotplug cpu instances so
> __cpuhp_remove_state_cpuslocked()
> doesn't emit this warning:
Cool, thanks!
I'm getting together a series of fixes now,
* Andi Kleen wrote:
> From: Andi Kleen
>
> Before enabling XSAVE, not only check the XSAVE specific CPUID bits,
> but also the base CPUID features of the respective XSAVE feature.
> This allows to disable individual XSAVE states using the existing
> clearcpuid= option, which can be useful for
* Ingo Molnar wrote:
> > + bool changed;
> > + __u32 disable[NCAPINTS + NBUGINTS];
> > + unsigned long *disable_mask = (unsigned long *)disable;
> > + const struct cpuid_dep *d;
>
> The constant forced types are really ugly and permeate the whole code. Please
> introduce some suitably
On Wed, 2017-10-11 at 11:34 -0500, Alan Tull wrote:
> Some platforms require reset to be released to allow register
> access.
>
> Signed-off-by: Alan Tull
> ---
> v2: Request shared controller
> return all errors from reset controller request
> drop conditions on asserting/deasserting res
On 11.10.2017 18:46, David Laight wrote:
From: Mathias Nyman
Sent: 11 October 2017 15:41
..
If possible I'd like to try and find some other solution before chopping the
Segment
size to smaller than 256.
I think that your first proposal of adding the guard page to the segment pool
could be an
On Sun, Sep 10, 2017 at 11:24:00AM +0200, Paolo Bonzini wrote:
> ... doh, I missed PeterZ's remark that the early test is gone in tip.
> Then the series makes total sense. Peter, if you ack patch 1 I can push
> it through the KVM tree.
I see its in already, but Ack ;-)
Hi,
On 11-10-17 20:10, Marcel Holtmann wrote:
Hi Hans,
It is no longer possible to build BT_HCIUART into the kernel
when SERIAL_DEV_BUS is a loadable module, even if none of the
SERIAL_DEV_BUS based implementations are selected:
drivers/bluetooth/hci_ldisc.o: In function `hci_uart_set_flow_con
On Wed, Oct 11, 2017 at 6:34 PM, Alan Tull wrote:
> Some platforms require reset to be released to allow register
> access.
>
> Signed-off-by: Alan Tull
> ---
> v2: Request shared controller
> return all errors from reset controller request
> drop conditions on asserting/deasserting rese
On 12 October 2017 at 10:08, Linus Walleij wrote:
> On Wed, Oct 11, 2017 at 3:58 PM, Ulf Hansson wrote:
>
>> Actually completing the request in the ->done callback, may still be
>> possible, because in principle it only needs to inform the other
>> prepared request that it may start, before it co
On 11 October 2017 at 23:14, Tom Gall wrote:
>>> * libhugetlbfs - 76 pass - 1 skip
>>> * ltp-cap_bounds-tests - 1 pass
>>> * ltp-commands-tests - 27 pass - 13 skip - 5 known failures (ksh not in
>>> test img)
>>> * ltp-containers-tests - 63 pass - 18 fail (these are being looked at looks
>>> lik
Hi Felipe, Alex,
On 10/11/2017 04:38 PM, Alexandre Torgue wrote:
>
>
> On 10/11/2017 03:26 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Alexandre Torgue writes:
>>> Hi
>>>
>>> On 10/11/2017 01:50 PM, Felipe Balbi wrote:
Hi,
Alexandre Torgue writes:
> Hi Felip
>
> On
On Tue, Oct 10, 2017 at 4:22 AM, Maxime Ripard
wrote:
> We've had quite a big number of warnings in our device trees due to some
> convention that was added before any kind of warning was introduced, and
> went on since.
>
> Some of our newest SoC will not generate any warning but the unavoidable
On Wed, Oct 11, 2017 at 06:23:29PM +0100, Will Deacon wrote:
> On Wed, Oct 11, 2017 at 05:10:35PM +0100, Mark Brown wrote:
> > I'm don't feel confident I can resolve this conflict sensibly without
> > taking too long so I've used the tip tree from yesterday.
> It's a shame that the conflict is so
Hi Hans,
It is no longer possible to build BT_HCIUART into the kernel
when SERIAL_DEV_BUS is a loadable module, even if none of the
SERIAL_DEV_BUS based implementations are selected:
drivers/bluetooth/hci_ldisc.o: In function `hci_uart_set_flow_control':
hci_ldisc.c:(.text
On Wed, 11 Oct 2017, Bjorn Helgaas wrote:
> On Tue, Sep 19, 2017 at 05:26:53PM +0800, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang
> >
> > This patch set adds ls1012a MSI and PCIe support, including driver
> > and device tree nodes. The ls1046a's MSI support patch and PCIe
> > driver patch has been
Hi,
Amelie DELAUNAY writes:
> Hi Felipe, Alex,
>
> On 10/11/2017 04:38 PM, Alexandre Torgue wrote:
>>
>>
>> On 10/11/2017 03:26 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Alexandre Torgue writes:
Hi
On 10/11/2017 01:50 PM, Felipe Balbi wrote:
>
> Hi,
>
> Alexan
Hi Sebastian,
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 29/09/17 16:26, Sebastian Reichel wrote:
> Hi Tomi & Laurent,
>
> ping?
I've been having quick glances at this every now and then, but I'm not
sure
[CC Christoph who seems to be the author of the code]
I would also note that a single patch rarely requires a separate cover
letter. If there is an information which is not suitable for the
changelog then you can place it in the diffstate area.
On Fri 06-10-17 08:36:34, Luis Felipe Sandoval Castr
On Tue, Oct 03, 2017 at 10:06:34PM +0800, Fengguang Wu wrote:
> #!/bin/bash
>
> kernel=$1
> initrd=openwrt-trinity-i386.cgz
>
> wget --no-clobber
> https://github.com/fengguang/reproduce-kernel-bug/raw/master/initrd/$initrd
>
> kvm=(
> qemu-system-x86_64
> -enable-kvm
> -cpu
This is a followup patch for: https://lkml.org/lkml/2017/10/11/375 and
https://patchwork.kernel.org/patch/649/
Make these structures const as they are either passed to the functions
having the argument as const or stored as a reference in the "ci_type"
const field of a config_item structure.
On 11/10/17 21:08, Dmitry Osipenko wrote:
> Add a device node for the video decoder engine found on Tegra20.
>
> Signed-off-by: Dmitry Osipenko
> ---
> arch/arm/boot/dts/tegra20.dtsi | 17 +
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dts/tegra20.dtsi b/ar
On Thu, Oct 12, 2017 at 12:21:46AM +0530, Pankaj Gupta wrote:
> We are sharing the prototype version of 'fake DAX' flushing
> interface for the initial feedback. This is still work in progress
> and not yet ready for merging.
>
> Protoype right now just implements basic functionality without advan
On 2017-10-10 14:43:13 [-0700], Paul E. McKenney wrote:
> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> index 6d5880089ff6..558f9e7b283e 100644
> --- a/kernel/rcu/srcutree.c
> +++ b/kernel/rcu/srcutree.c
> @@ -830,7 +866,7 @@ void __call_srcu(struct srcu_struct *sp, struct rcu_head
On Wed, Oct 11, 2017 at 11:44:26PM +0200, Pali Rohár wrote:
> On Wednesday 11 October 2017 23:24:35 Pali Rohár wrote:
> > On Wednesday 04 October 2017 17:33:32 Pali Rohár wrote:
> > > Hi! There is a big inconsistency in Linux tools which read or write
> > > FAT32 label in filesystem images. The mos
On Thu, Oct 12, 2017 at 7:10 AM, Abhishek Shah
wrote:
>> I am facing one issue, where; while disabling/ masking interrupts just
>> before kexec reboot, access to gpio expander pca9505 residing over
>> i2c bus hangs, because i2c interrupts are disabled prior to writing
>> pca9505 register.
This d
free the allocated insn before returning, when an error occurs
before adding insn to file->insn_list.
Signed-off-by: Kamalesh Babulal
---
tools/objtool/check.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index a0c518e
On Wed, Oct 11, 2017 at 04:11:37PM -0700, Andi Kleen wrote:
> Sorry I take back what I wrote earlier. This RCU is actually still needed,
> otherwise the reader could see partially written entries.
Why? All the readers and writers take the mutex now.
--
Regards/Gruss,
Boris.
Good mailing pra
On Wed, Oct 11, 2017 at 11:31:07AM -0500, Gustavo A. R. Silva wrote:
> Quoting Johan Hovold :
>
> > On Wed, Oct 11, 2017 at 10:12:50AM -0500, Gustavo A. R. Silva wrote:
> >> Hi Johan,
> >>
> >> Quoting Johan Hovold :
> >
> >> > Patch is fine, but next time make sure to run scripts/get_maintainer.s
This is a followup patch for: https://lkml.org/lkml/2017/10/11/375 and
https://patchwork.kernel.org/patch/649/
Make these structures const as they are either passed to the functions
having the argument as const or stored as a reference in the "ci_type"
const field of a config_item structure.
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Thursday, October 12, 2017 12:02 AM
> To: Madalin-cristian Bucur
> Subject: Re: [PATCH 3/4] dpaa_eth: change device used
>
> From: Madalin Bucur
> Date: Tue, 10 Oct 2017 17:10:17 +0300
>
> > @@ -2696,7 +2681,
On 10/12/2017 10:46 AM, Michal Hocko wrote:
> [CC Christoph who seems to be the author of the code]
>
> I would also note that a single patch rarely requires a separate cover
> letter. If there is an information which is not suitable for the
> changelog then you can place it in the diffstate area.
On Thursday 12 October 2017 10:56:58 Karel Zak wrote:
> On Wed, Oct 11, 2017 at 11:44:26PM +0200, Pali Rohár wrote:
> > On Wednesday 11 October 2017 23:24:35 Pali Rohár wrote:
> > > On Wednesday 04 October 2017 17:33:32 Pali Rohár wrote:
> > > > Hi! There is a big inconsistency in Linux tools which
On Tue, 10 Oct 2017, Marc Zyngier wrote:
> int its_alloc_vcpu_irqs(struct its_vm *vm)
> {
> int vpe_base_irq, i;
>
> + vm->affinity_masks = kzalloc(vm->nr_vpes * sizeof(*vm->affinity_masks),
> + GFP_KERNEL);
> + if (!vm->affinity_masks)
> +
On Thu, Oct 12, 2017 at 10:47:25AM +0200, Peter Zijlstra wrote:
On Tue, Oct 03, 2017 at 10:06:34PM +0800, Fengguang Wu wrote:
#!/bin/bash
kernel=$1
initrd=openwrt-trinity-i386.cgz
wget --no-clobber
https://github.com/fengguang/reproduce-kernel-bug/raw/master/initrd/$initrd
kvm=(
qem
Some $(call cc-option,...) are invoked very early, even before
KBUILD_CFLAGS, etc. are initialized.
The returned string from $(call cc-option,...) depends on
KBUILD_CPPFLAGS, KBUILD_CFLAGS, and GCC_PLUGINS_CFLAGS.
Since they are exported, they are not empty when the top Makefile
is recursively in
[ 35.721719] Kernel panic - not syncing: No working init found. Try passing
init= option to kernel. See Linux Documentation/admin-guide/init.rst for
guidance.
Well I got the same result. The script and initrd image matches well
with my local version. I'll dig what goes wrong.
And it did d
On Thu 12-10-17 11:14:02, Vlastimil Babka wrote:
> On 10/12/2017 10:46 AM, Michal Hocko wrote:
> > [CC Christoph who seems to be the author of the code]
> >
> > I would also note that a single patch rarely requires a separate cover
> > letter. If there is an information which is not suitable for t
> On Fri, 29 Sep 2017, 冯锐 wrote:
> > > On Fri, 22 Sep 2017, 冯锐 wrote:
> > >
> > > > > On Fri, Sep 22, 2017 at 05:36:24PM +0800, rui_f...@realsil.com.cn
> wrote:
> > > > > > From: rui_feng
> > > > > >
> > > > > > Add support for new chip rts5260.
> > > > > > In order to support rts5260，the definiti
Freeing a list of pages current enables/disables IRQs for each page freed.
This patch splits freeing a list of pages into two operations -- preparing
the pages for freeing and the actual freeing. This is a tradeoff - we're
taking two passes of the list to free in exchange for avoiding multiple
enab
(cc'ing those that reviewed Jan's series as this series is on top)
This series is a follow-on for Jan Kara's series "Speed up page cache
truncation" series. We both ended up looking at the same problem but saw
different problems based on the same data. This series builds upon his
work. The perform
On 10/11/2017 01:53 PM, Radoslaw Pietrzyk wrote:
> Do not read data on RXNE but on BTF only due to HW
> synchronisation problems and NACKing read data too early.
> It was found during testing of stmpe811 touchscreen driver.
>
Would you mind to explain what is behind "hw sync i
All callers of release_pages claim the pages being released are cache hot.
As no one cares about the hotness of pages being released to the allocator,
just ditch the parameter.
No performance impact is expected as the overhead is marginal. The parameter
is removed simply because it is a bit stupid
During truncate each entry in a pagevec is checked to see if it is an
exceptional entry and if so, the shadow entry is cleaned up. This is
potentially expensive as multiple entries for a mapping locks/unlocks the
tree lock. This batches the operation such that any exceptional entries
removed from
Every pagevec_init user claims the pages being released are false even in
cases where it is unlikely the pages are hot. As no one cares about the
hotness of pages being released to the allocator, just ditch the parameter.
No performance impact is expected as the overhead is marginal. The parameter
The cache files are only cleaned away by "make clean". If you continue
incremental builds, the cache files will grow up little by little.
It is not a big deal in general use cases because $(call cc-option,...)
in not added/deleted quite often.
However, if you do build-test for various architectur
Most callers users of free_hot_cold_page claim the pages being released are
cache hot. The exception is the page reclaim paths where it is likely that
enough pages will be freed in the near future that the per-cpu lists are
going to be recycled and the cache hotness information is lost. As no one
r
As the page free path makes no distinction between cache hot and cold
pages, there is no real useful ordering of pages in the free list that
allocation requests can take advantage of. Juding from the users of
__GFP_COLD, it is likely that a number of them are the result of copying
other sites inste
When a pagevec is initialised on the stack, it is generally used multiple
times over a range of pages, looking up entries and then releasing them.
On each pagevec_release, the per-cpu deferred LRU pagevecs are drained
on the grounds the page being released may be on those queues and the
pages may b
On Wed 2017-10-11 12:46:47, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> The variable printk_safe_irq_ready is set and never cleared at system
> boot up, when there's only one CPU active. It is set before other
> CPUs come on line. Also, it is extremely unlikely that an NMI would
> t
Some platforms have the capability to configure the performance state of
PM domains. This patch enhances the genpd core to support such
platforms.
The performance levels (within the genpd core) are identified by
positive integer values, a lower value represents lower performance
state.
This patch
During truncation, the mapping has already been checked for shmem and dax
so it's known that workingset_update_node is required. This patch avoids
the checks on mapping for each page being truncated. In all other cases,
a lookup helper is used to determine if workingset_update_node() needs
to be ca
hi Guys,
I am building the rpm on centos 7.3 from the kernel downloaded
from kernel.org.
It can not build the kernel debuginfo rpm by cmd: make rpm.
Is anybody knows how to build kernel debuginfo rpm?
Thanks!
John.Gong
Hi Joerg,
Can you please have a look and see if you are fine with this patch?
Thanks in advance,
Tomasz
On 20.09.2017 10:52, Tomasz Nowicki wrote:
Here is my test setup where I have stareted performance measurements.
PCIe - TX - PCIe -
| Thun
This is a followup patch for:
https://lkml.org/lkml/2017/10/11/375
https://patchwork.kernel.org/patch/649/
https://lkml.org/lkml/2017/10/11/469 and
https://lkml.org/lkml/2017/10/11/661
Make the config_item_type structures const as they are either passed to
the functions having the argument as
Hi Joerg,
Can you please have a look and see if you are fine with this patch?
Thanks in advance,
Tomasz
On 20.09.2017 10:52, Tomasz Nowicki wrote:
Here is my test setup where I have stareted performance measurements.
PCIe - TX - PCIe -
| Thun
2017-10-12 18:29 GMT+09:00 Masahiro Yamada :
>
> +nr_cache := $(words $(filter __cached_%, $(.VARIABLES)))
> +
> +# Strip the last digit. Covert as follows:
I meant "Convert".
> +#0 ->
> +#123 -> 12
--
Best Regards
Masahiro Yamada
On 12 October 2017 at 11:37, Viresh Kumar wrote:
> Some platforms have the capability to configure the performance state of
> PM domains. This patch enhances the genpd core to support such
> platforms.
>
> The performance levels (within the genpd core) are identified by
> positive integer values,
Hi,
I thought about this a lot from several angles. And I would prefer
sligly different placement, see the patch below.
On Thu 2017-09-28 14:18:24, Peter Zijlstra wrote:
> Some people figured vprintk_emit() makes for a nice API and exported
> it, bypassing the kdb trap.
Sigh, printk() API is pre
The elf_fdpic code shows a harmless warning when built with MMU
enabled, I ran into this now that the configuration is possible
on ARM randconfig builds:
fs/binfmt_elf_fdpic.c: In function 'elf_fdpic_dump_segments':
fs/binfmt_elf_fdpic.c:1501:17: error: unused variable 'addr'
[-Werror=unused-vari
On Wed, Oct 11, 2017 at 06:12:30PM -0700, Ricardo Neri wrote:
> Shouldn't this function check for a null insn since it is used here?
I have to say, this whole codepath from insn_get_seg_base() with
insn==NULL is nasty but I don't see a way around it as we need to know
how many bytes to copy and fr
On 2017/10/11 20:48, Jean-Philippe Brucker wrote:
> On 11/10/17 13:15, Joerg Roedel wrote:
>> On Wed, Oct 11, 2017 at 11:54:52AM +, Liu, Yi L wrote:
>>> I didn't quite get 'iovm' mean. Can you explain a bit about the idea?
>>
>> It's short for IO Virtual Memory, basically a replacement term for
While experimenting with changes to the timekeeping code, I
ran into a build error in the liquidio driver:
drivers/net/ethernet/cavium/liquidio/lio_main.c: In function
'liquidio_ptp_settime':
drivers/net/ethernet/cavium/liquidio/lio_main.c:1850:22: error: passing
argument 1 of 'timespec_to_ns' f
From: Bjorn Helgaas
> Sent: 12 October 2017 00:33
> Why do you limit it to PCIe? Isn't it conceivable that one could
> hot-add a conventional PCI card that contained a bridge leading to
> another hotplug slot? E.g., a PCI card with PCMCIA slot or something
> on it?
There are (maybe were!) cardbu
> -Original Message-
> From: Bob Liu [mailto:liub...@huawei.com]
> Sent: Thursday, October 12, 2017 5:39 PM
> To: Jean-Philippe Brucker ; Joerg Roedel
> ; Liu, Yi L
> Cc: Lan, Tianyu ; Liu, Yi L ;
> Greg
> Kroah-Hartman ; Wysocki, Rafael J
> ; LKML ;
> io...@lists.linux-foundation.org;
Linus,
please pull sound fixes for v4.14-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.14-rc5
The topmost commit is 99fee508245825765ff60155fed43f970ff83a8f
sound fixes for 4.14-rc5
It's
It looks like there is a use case when IRQ handler is delayed a bit
and the logic in the driver does not work. What is the real root cause
I don't know.
2017-10-12 11:31 GMT+02:00 Pierre Yves MORDRET :
>
>
> On 10/11/2017 01:53 PM, Radoslaw Pietrzyk wrote:
>> Do not read data on RXNE but on
Since Kbuild runs in the objtree, __FILE__ can be a very long path
depending of $(srctree).
Commit 9da0763bdd82 ("kbuild: Use relative path when building in a
subdir of the source tree") made the situation better for cases where
objtree is a child of srctree. ($(srctree) is "..")
For other cases
Kbuild works in objtree, not in srctree. So, __FILE__ is prefixed
with $(srctree)/ for out-of-tree build.
For example, WARN_ON() will look as follows if you built your kernel
out of source tree:
WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:...
With this series, it
I want to reuse $(squote)$(quote)...$(quote)$(squote) in the next
commit. Move it to a helper.
Signed-off-by: Masahiro Yamada
---
scripts/Kbuild.include | 4
scripts/Makefile.lib | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/Kbuild.include b/scripts/Kbuil
On Tue, Oct 10, 2017 at 11:23:45AM -0700, Omar Sandoval wrote:
> On Mon, Oct 09, 2017 at 07:24:23PM +0800, Ming Lei wrote:
> > SCSI devices use host-wide tagset, and the shared driver tag space is
> > often quite big. Meantime there is also queue depth for each lun(
> > .cmd_per_lun), which is ofte
From: Hou Zhiqiang
The Freescale PCIe controller advertises the MSI/MSI-X capability
in both RC and Endpoint mode, but in RC mode it doesn't support
MSI/MSI-X by itself, it can only transfer MSI/MSI-X from downstream
devices. So add this quirk to prevent use of MSI/MSI-X in RC mode.
Signed-off-b
From: Hou Zhiqiang
The [1/2] is to fix layerscape PCIe MSI/MSI-X capability errata.
The [2/2] is to change the default AXI system error response behavior
for PCI Express outbound non-posted requests.
Hou Zhiqiang (1):
PCI: Disable MSI for Freescale PCIe RC mode
Minghuan Lian (1):
pci/layers
From: Minghuan Lian
By default, when the PCIe controller experiences an erroneous
completion from an external completer for its outbound non-posted
request, it always sends an OKAY response to the device's internal
AXI slave system interface. However, such default system error
response behavior c
1 - 100 of 970 matches
Mail list logo
