On Thu, 28 Jan 2016, Thomas Gleixner wrote:
> On Thu, 28 Jan 2016, Ulf Hansson wrote:
> > Therefore, the only way we currently can make sure to don't get the
> > IRQ is to free and later re-request it. Now, apparently that has
> > issues when using threaded IRQ handlers.
>
> What's the issue?
On Thu, Jan 28, 2016 at 04:16:27PM +0100, Ulf Hansson wrote:
> That's really great news. Thank you very much Adrian!
>
> Perhaps Russell is willing to help co-maintain it?
Unfortunately, I'm not really in a position to co-maintain it, as
I'd be doing it in my spare time, and my spare time is
[I am sorry I am coming here late but I didn't have time earlier]
On Fri 15-01-16 15:30:59, Johannes Weiner wrote:
> On Fri, Jan 15, 2016 at 12:58:34PM +0300, Vladimir Davydov wrote:
> > With the follow-up it looks good to me. All exported counters look
> > justified enough and the format follows
When dma_addr_t is 64-bit, we get a warning about an invalid cast
in the call to ux500_dma_is_compatible() from ux500_dma_channel_program():
drivers/usb/musb/ux500_dma.c: In function 'ux500_dma_channel_program':
drivers/usb/musb/ux500_dma.c:210:51: error: cast to pointer from integer of
The musb driver prints DMA addresses in a few places, using the
0x%x format string. This is wrong on 64-bit architectures (which
need %lx) and 32-bit ARM with CONFIG_LPAE set (which needs
%llx), otherwise we print the wrong data, as gcc warns:
musb/musbhsdma.c: In function 'configure_channel':
The power_up function is used for otg or udc mode, but nost when
the driver is only configured for host mode:
drivers/usb/phy/phy-isp1301-omap.c:261:13: error: 'power_up' defined but not
used [-Werror=unused-function]
This marks the function __maybe_unused to avoid the warning and
silently drop
The netdev_stats_to_stats64 function copies the deprecated
net_device_stats format stats into rtnl_link_stats64 for legacy support
purposes, but with the BUILD_BUG_ON as it was, it wasn't possible to
extend rtnl_link_stats64 without also extending net_device_stats. Relax
the BUILD_BUG_ON to only
On Thu, 28 Jan 2016, Ulf Hansson wrote:
> On 28 January 2016 at 11:20, Russell King - ARM Linux
> wrote:
> >> - free_irq(host->irq, host);
> >> + disable_irq(host->irq);
> >
> > This is really not acceptable I'm afraid. While it's common on ARM for
> > each interrupt to
The USB_FSL_MPH_DR_OF symbol is used to ensure the code that interprets
the DR device node is built whenever one of the two drivers (EHCI or
UDC) for the platform is enabled. However, if CONFIG_USB is disabled
and we only support gadget mode, this causes a Kconfig warning:
warning: (USB_FSL_USB2)
This converts the pxa25x udc driver to use readl/writel as normal
driver should do, rather than dereferencing __iomem pointers
themselves.
Based on the earlier preparation work, we can now also pass
the register start in the device pointer so we no longer need
the global variable.
The unclear
This removes the dependency on the mach/hardware.h header file
from the pxa25x_udc driver after the register definitions were
already unified in the previous patch.
Following the model of pxa27x_udc (and basically all other drivers
in the kernel), we define the register numbers as offsets from
Hi
I want to get system available memory and memory usage of one
precess(known Pid). Now I read /proc/meminfo and /proc/$pid/stat to
get above data.
And my question is:
1 Is there system call or API to get above data?
2 Linux kernel add "MemAvailable" to "/proc/meminfo" in 3.14, but I
ixp4xx and pxa25x both use this driver and provide a slightly
different set of register definitions for it. Aside from that,
the definition in the ixp4xx-regs.h header conflicts with the
on in the pxa27x device driver when compile-testing that:
In file included from
Hi Felipe,
This set of patches addresses warnings I got in randconfig builds,
in the USB drivers. The first three patches are for the pxa25x
UDC driver and are a larger scale cleanup triggered by finding
the initial bug. The other four are relatively simple but still
need to be reviewed properly,
Hi Jan,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.5-rc1 next-20160128]
[cannot apply to tip/perf/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Jan-Glauber
On Thu, 28 Jan 2016 13:53:04 -0200
Mauro Carvalho Chehab wrote:
> Em Wed, 6 Jan 2016 13:27:04 -0700
> Shuah Khan escreveu:
>
> > Checking for tuner availability from frontend thread start
> > disrupts video stream. Change to check for tuner and start
> > pipeline from frontend open instead
[Ups this one somehow fall through cracks]
On Wed 13-01-16 16:51:57, Johannes Weiner wrote:
> Changing page->mem_cgroup of a live page is tricky and fragile. In
> particular, the memcg writeback code relies on that mapping being
> stable and users of mem_cgroup_replace_page() not overlapping with
Hi Stephan,
On 01/27/2016 10:26 PM, Stephan Mueller wrote:
>> +for (i = 0; i < areq->tsgls; i++)
>> > + put_page(sg_page(sg + i));
> Shouldn't here be the same logic as in put_sgl? I.e.
>
> for (i = 0; i < sgl->cur; i++) {
> if (!sg_page(sg + i))
>
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
Nicolas Ferre writes:
> From: Cyrille Pitchen
>
> The non-DT platform that uses this driver (actually the AVR32) was taking a
> bad
> branch for determining if the IP would use gpio for CS.
> Adding the presence of DT as a condition fixes this issue.
>
> Signed-off-by: Cyrille Pitchen
>
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux-keypad,wakeup" boolean property to enable the
wakeup source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup properties with the unified
"wakeup-source"
On Thu, Jan 28, 2016 at 5:49 AM, Thomas Gleixner wrote:
> On Thu, 28 Jan 2016, Brian Starkey wrote:
>> I've got a few devices on the same interrupt line. One driver does
>
> Just for the record: When will hardware folks finally understand that shared
> interrupt lines are a nightmare?
>
>>
Em Wed, 6 Jan 2016 13:27:06 -0700
Shuah Khan escreveu:
> au0828 is changed to use v4l_enable_media_tuner() to check for
> tuner availability from vidioc_g_tuner(), and au0828_v4l2_close(),
> before changing tuner settings. If tuner isn't free, return busy
> condition from vidioc_g_tuner() and
On Wed, Jan 27, K. Y. Srinivasan wrote:
> + depends on SCSI_FC_ATTRS
I think 'depends' instead of 'select' will cause HYPERV_STORAGE to
disapepar during make oldconfig if SCSI_FC_ATTRS was not set before.
Not sure what the policy of 'depends' vs. 'select' actually is. If
SCSI_FC_ATTRS is
On Thu, 28 Jan 2016 16:29:57 +0100
Peter Zijlstra wrote:
> On Thu, Jan 28, 2016 at 02:53:53PM +, Mathieu Desnoyers wrote:
> > On x86, many BIOS wipe the memory content even after a warm reset :(
> > The most reliable solution I found on x86 is to use kexec() to
> > boot into a new kernel,
On Thu, 28 Jan 2016 16:03:34 +0100
Ulf Hansson wrote:
> [...]
>
> >
> >> > of it's bad code structure. Therefore I have taken a quite simple
> >> > approach by rejecting new callbacks and quirks, in a way to prevent it
> >> > from being worse.
> >
> > Which merely guarantees that the
On Wed 27-01-16 19:28:57, Vladimir Davydov wrote:
> When vmpressure is called for the entire subtree under pressure we
> mistakenly use vmpressure->scanned instead of vmpressure->tree_scanned
> when checking if vmpressure work is to be scheduled. This results in
> suppressing all vmpressure events
On 01/27/2016 03:52 PM, Jan Stancek wrote:
> Hello,
>
> pthread_cond_wait_1/2 [1] is rarely failing for me on 4.5.0-rc1,
> on x86_64 KVM guest with 2 CPUs.
>
> This test [1]:
> - spawns 2 SCHED_RR threads
> - first thread with higher priority sets alarm for 2 seconds and blocks on
> condition
>
Em Wed, 6 Jan 2016 13:27:04 -0700
Shuah Khan escreveu:
> Checking for tuner availability from frontend thread start
> disrupts video stream. Change to check for tuner and start
> pipeline from frontend open instead and stop pipeline from
> frontend release.
That's wrong, as DVB can be opened
On Thu, Jan 28, 2016 at 11:34:40AM +0100, Linus Walleij wrote:
> On Sat, Jan 23, 2016 at 5:32 PM, Antoine Tenart
> wrote:
>
> > This patch adds the GPIO support for the Baytrail family.
> >
> > Signed-off-by: Antoine Tenart
>
> I'm confused by this and Mika's comment on patch 0.
>
> Is the
This adds an rx_nohandler stat counter, along with a sysfs statistics
node, and copies the counter out via netlink as well.
CC: "David S. Miller"
CC: Eric Dumazet
CC: Jiri Pirko
CC: Daniel Borkmann
CC: Tom Herbert
CC: Jay Vosburgh
CC: Veaceslav Falico
CC: Andy Gospodarek
CC:
CC: Jiri Pirko
CC: net...@vger.kernel.org
Signed-off-by: Jarod Wilson
---
drivers/net/team/team.c | 10 +++---
include/linux/if_team.h | 1 +
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c
index 718ceea..00558e1 100644
---
The network core tries to keep track of dropped packets, but some packets
you wouldn't really call dropped, so much as intentionally ignored, under
certain circumstances. One such case is that of bonding and team device
slaves that are currently inactive. Their respective rx_handler functions
The netdev_stats_to_stats64 function copies the deprecated
net_device_stats format stats into rtnl_link_stats64 for legacy support
purposes, but with the BUILD_BUG_ON as it was, it wasn't possible to
extend rtnl_link_stats64 without also extending net_device_stats. Relax
the BUILD_BUG_ON to only
Sample output with this set applied for an active-backup bond:
$ cat /sys/devices/virtual/net/bond0/lower_p7p1/statistics/rx_nohandler
16568
$ cat /sys/devices/virtual/net/bond0/lower_p5p2/statistics/rx_nohandler
16583
$ cat /sys/devices/virtual/net/bond0/statistics/rx_nohandler
33151
CC: Jay
Ping
> Subject: RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL
> PCIe Host Controller
>
> > On Mon, Dec 21, 2015 at 05:23:47AM +, Bharat Kumar Gogada wrote:
> > > Hi Bjorn, can you comment on this. Marc has also replied for query
> > > on
> > irq_dispose_mapping().
> >
Hello,
On Wed, Jan 27, 2016 at 10:11:44PM +0100, Dmitry Vyukov wrote:
> Sorry, I meant only the second once. The mm bug.
> I guess you need at least CONFIG_DEBUG_VM. Run it in a tight parallel
> loop with CPU oversubscription (e.g. 32 parallel processes on 2 cores)
> for at least an hour.
Does
+tglx, Jon
On 28 January 2016 at 11:20, Russell King - ARM Linux
wrote:
> On Thu, Jan 28, 2016 at 05:42:26PM +0800, Haibo Chen wrote:
>> Currently sdhci driver free irq in host suspend, and call
>> request_threaded_irq() in host resume. But during host resume,
>> Ctrl+C can impact sdhci host
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Wednesday, January 27, 2016 10:03 PM
> To: KY Srinivasan ; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; oher...@suse.com;
>
On (01/28/16 19:53), Sergey Senozhatsky wrote:
> > ah... silly me... you mean the first CPU that triggers the spin_dump() will
> ^^^ this, of course, is true for
> console_sem->lock and logbuf_lock
>
Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.
Signed-off-by: Andrew Lunn
---
drivers/nvmem/core.c | 77 +-
include/linux/nvmem-provider.h | 4 ++-
Now that the AT24 uses the NVMEM framework, replace the
memory_accessor in the setup() callback with nvmem API calls.
Signed-off-by: Andrew Lunn
---
arch/arm/mach-davinci/board-mityomapl138.c | 5 +++--
arch/arm/mach-davinci/common.c | 4 ++--
drivers/misc/eeprom/at24.c
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backwards compatibility in the NVMEM config,
so that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
drivers/misc/eeprom/at25.c |
The setup() callback is not used by any in kernel code. Remove it.
Any new code which requires access to the eeprom can use the NVMEM
API.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/at25.c | 26 --
include/linux/spi/eeprom.h | 2 --
2 files changed, 28
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Set the NVMEM config structure to enable backward, so
that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
drivers/misc/eeprom/at24.c |
This patch set converts the old EEPROM drivers in driver/misc/eeprom to
use the NVMEM framework. These drivers export there content in /sys as
read only to root, since the EEPROM may contain sensitive information.
So the first patch adds a flag so the NVMEM framework will create its
file in /sys
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backward compatibility in the MVMEM config
structure, so that the 'eeprom' file in sys is provided by the
framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
Legacy AT24, AT25 EEPROMs are exported in sys so that only root can
read the contents. The EEPROMs may contain sensitive information. Add
a flag so the provide can indicate that NVMEM should also restrict
access to root only.
Signed-off-by: Andrew Lunn
---
drivers/nvmem/core.c | 57
Mathieu Poirier writes:
>> I'd like to understand all the potential failures here, because it's
>> really a good idea to keep those to a minimum for the sake of
>> consistency. That is, if the user succeeded in creating an event, about
>> the only good reason for the event not starting is a
On Wed, Jan 27, 2016 at 10:28:48AM -0600, Christoph Lameter wrote:
> On Wed, 27 Jan 2016, Mike Galbraith wrote:
>
> > > Since we (the NOHZ people) care mostly about NOHZ then lets restrict
> > > that to the NOHZ mode. Then it should not affect your load.
> >
> > Tons of folks do have NO_HZ
On Wed 27-01-16 12:26:16, Christoph Lameter wrote:
> On Wed, 27 Jan 2016, Michal Hocko wrote:
>
> > This is caused by 0eb77e988032 ("vmstat: make vmstat_updater deferrable
> > again and shut down on idle") which has placed quiet_vmstat into
> > cpu_idle_loop. The main reason here seems to be that
Em Wed, 6 Jan 2016 13:27:02 -0700
Shuah Khan escreveu:
> au0828_create_media_graph() doesn't do any checks to determine,
> if vbi_dev, vdev, and input entities have been registered prior
> to creating pad links. Checking graph_obj.mdev field works as
> the graph_obj.mdev field gets initialized
The description mentions kswapd threads, while the deferred struct page
initialization is actually done by one-off "pgdatinitX" threads. Fix the
description so that potentially users are not confused about pgdatinit threads
using CPU after boot instead of kswapd.
Signed-off-by: Vlastimil Babka
On Thu 28-01-16 16:31:11, Michal Hocko wrote:
> On Wed 27-01-16 12:26:16, Christoph Lameter wrote:
> > On Wed, 27 Jan 2016, Michal Hocko wrote:
> [...]
> > > +void quiet_vmstat(void)
> > > +{
> > > + if (system_state != SYSTEM_RUNNING)
> > > + return;
> > > +
> > > + /*
> > > + * If we
On Thu, 2016-01-28 at 07:48 +0100, Olaf Hering wrote:
> On Wed, Jan 27, James Bottomley wrote:
>
> > It's not really architecture independent, is it? Just use the bit
> > width config.
>
> Again: which one? This driver is not for mips|powerpc|score|sh.
zgrep CONFIG_.*BIT /proc/config.gz
[...]
On Wed, Jan 27, 2016 at 03:00:11PM -0800, Paul E. McKenney wrote:
> On Wed, Jan 27, 2016 at 06:39:23PM +, Will Deacon wrote:
> > On Wed, Jan 27, 2016 at 07:25:51PM +0100, Peter Zijlstra wrote:
> > > On Wed, Jan 27, 2016 at 06:22:04PM +, Will Deacon wrote:
> > > > As much as we'd like to
Em Wed, 6 Jan 2016 13:26:57 -0700
Shuah Khan escreveu:
> Add a new interfaces to be used by v4l-core to invoke enable
> source and disable_source handlers in the media_device. The
> enable_source helper function invokes the enable_source handler
> to find tuner entity connected to the decoder
On Wed 27-01-16 12:26:16, Christoph Lameter wrote:
> On Wed, 27 Jan 2016, Michal Hocko wrote:
[...]
> > +void quiet_vmstat(void)
> > +{
> > + if (system_state != SYSTEM_RUNNING)
> > + return;
> > +
> > + /*
> > +* If we are already in hands of the shepherd then there
> > +*
On Thu, Jan 28, 2016 at 02:53:53PM +, Mathieu Desnoyers wrote:
> On x86, many BIOS wipe the memory content even after a warm reset :(
> The most reliable solution I found on x86 is to use kexec() to
> boot into a new kernel, mount the DAX filesystem again and read the
> buffers from there.
Em Wed, 6 Jan 2016 13:26:58 -0700
Shuah Khan escreveu:
> Add a new v4l_vb2q_enable_media_tuner() wrapper function
> to be called from v4l2-core to enable the media tuner with
> videobuf2 queue, when the calling frunction has the videobuf2
> queue and doesn't have the struct video_device
On Thu, Jan 28, 2016 at 10:03:15AM +0100, Borislav Petkov wrote:
> +
> +struct power_pmu {
> + raw_spinlock_t lock;
Now that the list is gone, what does this thing protect?
> + struct pmu *pmu;
This member seems superfluous, there's only the one possible value.
>
On Thu, Jan 28, 2016 at 06:17:07AM -0800, Kees Cook wrote:
> This changes several users of manual "on"/"off" parsing to use strtobool.
>
> Signed-off-by: Kees Cook
> Cc: x...@kernel.org
> Cc: linuxppc-...@lists.ozlabs.org
> Cc: linux-s...@vger.kernel.org
> ---
> arch/powerpc/kernel/rtasd.c
this patch.
> Pretty much all non-MMU builds fail, plus several MMU builds.
> I had prepared a patch for mn10300, but gave up after I noticed
> all the other failures.
Please try mine "[PATCH] mm: polish virtual memory accounting"
instead of that. It should fix some (or all) fails
On Thu, Jan 28, 2016 at 06:38:25AM -0800, Kees Cook wrote:
> There continue to be unexpected security exposures when users have access
> to CLONE_NEWUSER. For admins of systems that do not use user namespaces
> and are running distro kernels with CONFIG_USER_NS enabled, there is
> no way to
Rik van Riel writes:
> Hi,
>
> I am trying to gauge interest in discussing VM containers at the LSF/MM
> summit this year. Projects like ClearLinux, Qubes, and others are all
> trying to use virtual machines as better isolated containers.
>
> That changes some of the goals the memory management
On 1/28/16 15:22, Heiko Carstens wrote:
> On Mon, Jan 25, 2016 at 04:58:18AM +0800, cheng...@emindsoft.com.cn wrote:
>> From: Chen Gang
>>
>> hlist_bl_unhashed() and hlist_bl_empty() are all boolean functions, so
>> return bool instead of int.
>>
>> Signed-off-by: Chen Gang
>> ---
>>
Em Wed, 6 Jan 2016 13:26:53 -0700
Shuah Khan escreveu:
> Add new fields to struct media_device to add enable_source, and
> disable_source handlers, and source_priv to stash driver private
> data that is need to run these handlers. The enable_source handler
> finds source entity for the passed
On Thu, 28 Jan 2016 15:56:55 +0100,
Shuah Khan wrote:
>
> On 01/21/2016 11:09 AM, Shuah Khan wrote:
> > Please note that I am sending just the 4 patches that
> > changed during series rebase to Linux 4.5. The rebase
> > was pain free. media_device_init() type change required
> > changes to
On Thu, Jan 28, 2016 at 6:59 AM, Mark Rutland wrote:
> On Thu, Jan 28, 2016 at 06:06:53AM -0800, Kees Cook wrote:
>> On Thu, Jan 28, 2016 at 3:06 AM, Mark Rutland wrote:
>> > One thing I would like to do is to avoid the need for fixup_executable
>> > entirely, by mapping the kernel text RO from
[...]
>> I don't intend to contribute much with actual patches. I am willing to
>> help review and also help with expertise around the PM related parts.
>>
>> I do realize that some callbacks may still be needed, even in the end
>> when sdhci has become a pure library. Although, those should be
Thanks for your advices.
I will take your advice if I could have the opportunity
to write the final code.
As matter of factor, I trigger this bug when I tried to
migrate H323 code to other operating systems.
This could trigger a panic because get_h2x5_addr functions
is the first time we ever
Em Wed, 6 Jan 2016 13:26:52 -0700
Shuah Khan escreveu:
> Add new interfaces to register and unregister entity_notify
> hook to media device to allow drivers to take appropriate
> actions when as new entities get added to the shared media
> device.When a new entity is registered, all registered
On Thu, Jan 28, 2016 at 06:46:50AM -0800, Eric Dumazet wrote:
> On Thu, 2016-01-28 at 06:44 -0800, Eric Dumazet wrote:
> > On Thu, 2016-01-28 at 06:42 -0800, Eric Dumazet wrote:
> >
> > >
> > > Sure, you also can set stats64->rx_unhandled to 0 here, just to be 100%
> > > safe.
> >
> > And not
On 01/28/2016 06:37 AM, Paul Gortmaker wrote:
> [Re: Regression: 4.5-rc1 (bisect: hugetlb: make mm and fs code explicitly
> non-modular vs CONFIG_TIMER_STATS)] On 28/01/2016 (Thu 10:48) Christian
> Borntraeger wrote:
>
>> On 01/28/2016 10:40 AM, Hillf Danton wrote:
Paul,
the
[...]
>
>> > of it's bad code structure. Therefore I have taken a quite simple
>> > approach by rejecting new callbacks and quirks, in a way to prevent it
>> > from being worse.
>
> Which merely guarantees that the problem gets worse, because everyone
> just puts their SD patches into Android
Em Wed, 6 Jan 2016 13:26:51 -0700
Shuah Khan escreveu:
> Add ALSA Media Controller capture, playback, and mixer
> function entity defines.
>
> Signed-off-by: Shuah Khan
> ---
> include/uapi/linux/media.h | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git
Em Wed, 6 Jan 2016 13:26:50 -0700
Shuah Khan escreveu:
> From: Mauro Carvalho Chehab
>
> Declare the interface types to be used on alsa for the new
> G_TOPOLOGY ioctl.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> drivers/media/media-entity.c | 12
>
The SAW2 (Subsystem Power Manager and Adaptive Voltage Scalling Wrapper)
is part of the SPM subsystem. It is a hardware block in the Qualcomm
chipsets that regulates the power to the CPU cores on platform such as
apq8064, apq8084 and others.
Signed-off-by: Georgi Djakov
---
Changes since v1
On Thu, Jan 28, 2016 at 06:06:53AM -0800, Kees Cook wrote:
> On Thu, Jan 28, 2016 at 3:06 AM, Mark Rutland wrote:
> > One thing I would like to do is to avoid the need for fixup_executable
> > entirely, by mapping the kernel text RO from the outset. However, that
> > requires rework of the
On Thu, Jan 28, 2016 at 01:20:28PM +, Wang Nan wrote:
> A new patch of libbabeltrace [1] reveals a object leak problem in
> perf data CTF support: perf code never release event_class which is
> allocated in add_event() and stored in evsel's private field.
>
> If libbabeltrace has the above
>> The admin of such a machine could have disabled userns months earlier
>> and limited the scope of the attack.
>
> Of course for the paranoid there is already a mechanism to do this.
> /sbin/chroot.
>
> No new user namespaces are allowed to be created inside of a chroot.
Another alternative is
On 01/21/2016 11:09 AM, Shuah Khan wrote:
> Please note that I am sending just the 4 patches that
> changed during series rebase to Linux 4.5. The rebase
> was pain free. media_device_init() type change required
> changes to patches 18 and 26. I re-tested the series
> and everything looks good.
>
On 01/28/2016 04:47 AM, Linus Walleij wrote:
On Mon, Jan 25, 2016 at 5:14 PM, Andrew F. Davis wrote:
Add driver for TI TPIC2810 8-Bit LED Driver with I2C Interface.
The TPIC2810 has 8 open-drain outputs that can but used to drive
LEDs and other low-side switched resistive loads.
ARMv8.1 increases the PMU event number space. Detect the
presence of this PMUv3 type and extend the event mask.
The event mask is moved to struct arm_pmu so different event masks
can exist, depending on the PMU type.
Signed-off-by: Jan Glauber
---
arch/arm64/kernel/perf_event.c | 33
Add a compatible string for the Cavium ThunderX PMU.
Signed-off-by: Jan Glauber
---
Documentation/devicetree/bindings/arm/pmu.txt | 1 +
arch/arm64/boot/dts/cavium/thunder-88xx.dtsi | 5 +
2 files changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/pmu.txt
Hi Mark & Will,
I'm resending the arm64 PMU patches. The only difference to the first
version is that I dropped the x on thunder in order to be consistent
with the existing device tree name.
Thanks,
Jan
Jan Glauber (5):
arm64/perf: Rename Cortex A57 events
arm64/perf: Add Cavium ThunderX
Support PMU events on Caviums ThunderX SOC. ThunderX supports
some additional counters compared to the default ARMv8 PMUv3:
- branch instructions counter
- stall frontend & backend counters
- L1 dcache load & store counters
- L1 icache counters
- iTLB & dTLB counters
- L1 dcache & icache prefetch
With the long cycle counter bit (LC) disabled the cycle counter is not
working on ThunderX SOC (ThunderX only implements Aarch64).
Also, according to documentation LC == 0 is deprecated.
To keep the code simple the patch does not introduce 64 bit wide counter
functions. Instead writing the cycle
The implemented Cortex A57 events are not A57 specific.
They are recommended by ARM and can be found on other
ARMv8 SOCs like Cavium ThunderX too. Therefore move
these events to the common PMUv3 table.
Signed-off-by: Jan Glauber
---
arch/arm64/kernel/perf_event.c | 28
On Thu, Jan 28, 2016 at 01:42:09PM +0100, Borislav Petkov wrote:
> http://git.kernel.org/cgit/linux/kernel/git/bp/bp.git/log/?h=tip-perf
>
> Please use that branch instead.
I'm pasting next version here, I'm not hoping that kbuild robot will be
able to paste this email and know *not* to build it
- On Jan 28, 2016, at 9:47 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Thu, Jan 28, 2016 at 02:38:16PM +, Mathieu Desnoyers wrote:
>> - On Jan 28, 2016, at 8:57 AM, Peter Zijlstra pet...@infradead.org wrote:
>>
>> > On Thu, Jan 28, 2016 at 01:38:00PM +, Mathieu Desnoyers
On Wed, 27 Jan 2016 19:25:09 +0100
Alexander Potapenko wrote:
> --- a/include/linux/ftrace.h
> +++ b/include/linux/ftrace.h
> @@ -762,6 +762,26 @@ struct ftrace_graph_ret {
> typedef void (*trace_func_graph_ret_t)(struct ftrace_graph_ret *); /* return
> */
> typedef int
+-+++---+
| | 074b6f53c3
| a1fd55538c | next-20160128
rcu_nocb_gp_cleanup() is called while holding rnp->lock. Currently,
this is okay because the wake_up_all() in rcu_nocb_gp_cleanup() will
not enable the IRQs. lockdep is happy.
By switching over using swait this is not true anymore. swake_up_all()
enables the IRQs while processing the waiters.
From: Paul Gortmaker
As of commit dae6e64d2bcfd4b06304ab864c7e3a4f6b5fedf4 ("rcu: Introduce
proper blocking to no-CBs kthreads GP waits") the RCU subsystem started
making use of wait queues.
Here we convert all additions of RCU wait queues to use simple wait queues,
since they don't need the
From: Marcelo Tosatti
The problem:
On -rt, an emulated LAPIC timer instances has the following path:
1) hard interrupt
2) ksoftirqd is scheduled
3) ksoftirqd wakes up vcpu thread
4) vcpu thread is scheduled
This extra context switch introduces unnecessary latency in the
LAPIC path for a KVM
From: "Peter Zijlstra (Intel)"
The existing wait queue support has support for custom wake up call
backs, wake flags, wake key (passed to call back) and exclusive
flags that allow wakers to be tagged as exclusive, for limiting
the number of wakers.
In a lot of cases, none of these features are
Hi,
The -Werror=incompatible-pointer-types compiler flag is now
unconditionally added. The compile test with various configurations
and architectures didn't show up any show problem. *fingers crossed*
Obviously, the series is rebased and I rerun the KVM tests
to gather more up to date values.
With the introduction of the simple wait API we have two very
similar APIs in the kernel. For example wake_up() and swake_up()
is only one character away. Although the compiler will warn
happily the wrong usage it keeps on going an even links the kernel.
Thomas and Peter would rather like to see
On 01/28/2016 05:20 AM, Mark Rutland wrote:
On Thu, Jan 28, 2016 at 11:08:20AM +, Will Deacon wrote:
On Thu, Jan 28, 2016 at 10:34:41AM +, Catalin Marinas wrote:
I thought there was also a suggestion that we could fail gracefully in
the EFI stub if we detected an unsupported page
701 - 800 of 2364 matches
Mail list logo
