It's useful for tuning to be able to edit thermal_zone_parameters from
userspace. Export them to the thermal_zone sysfs so that they can be
easily changed.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-off-by: Javi Merino
---
Documentation/thermal/sysfs-api.txt | 52 +++
On Thu, Feb 19, 2015 at 05:34:46PM +0300, Vladimir Davydov wrote:
> Currently, we call cgroup_subsys->bind only on unmount, remount, and
> when creating a new root on mount. Since the default hierarchy root is
> created in cgroup_init, we will not call cgroup_subsys->bind if the
> default
*** BLURB HERE ***
Hi linux-pm,
Introduce the power allocator governor, a thermal governor that
allocates device power to control temperature. This series is based
on branch "linus" of Eduardo's linux-soc-thermal tree:
On Thu, Feb 19, 2015 at 05:34:47PM +0300, Vladimir Davydov wrote:
> If the memory cgroup controller is initially mounted in the scope of the
> default cgroup hierarchy and then remounted to a legacy hierarchy, it
> will still have hierarchy support enabled, which is incorrect. We should
> disable
On Mon, Mar 2, 2015, at 10:45, Bastien Nocera wrote:
> Move the getting/setting of the adaptive keyboard mode to separate
> functions, so that we can reuse them later through sysfs attributes.
>
> Signed-off-by: Bastien Nocera
Acked-by: Henrique de Moraes Holschuh
> ---
>
On Mon, Mar 2, 2015, at 10:45, Bastien Nocera wrote:
> Rather than checking on each suspend and resume whether the laptop
> has an adaptive keyboard, check when the driver is initialised.
>
> Signed-off-by: Bastien Nocera
Acked-by: Henrique de Moraes Holschuh
> ---
>
Hi,
I spent some time looking at this patch series and testing some scenarios.
On Mon, Feb 23, 2015 at 9:25 AM, Kan Liang wrote:
>
> From: Yan, Zheng
>
> PEBS always had the capability to log samples to its buffers without
> an interrupt. Traditionally perf has not used this but always set the
From: Antonios Motakis
Some IOMMU drivers, such as the ARM SMMU driver, make available the
IOMMU_NOEXEC flag to set the page tables for a device as XN (execute never).
This affects devices such as the ARM PL330 DMA Controller, which respects
this flag and will refuse to fetch DMA instructions
From: Antonios Motakis
This patch forms the common skeleton code for platform devices support
with VFIO. This will include the core functionality of VFIO_PLATFORM,
however binding to the device and discovering the device resources will
be done with the help of a separate file where any Linux
From: Antonios Motakis
We introduce the VFIO_DMA_MAP_FLAG_NOEXEC flag to the VFIO dma map call,
and expose its availability via the capability VFIO_DMA_NOEXEC_IOMMU.
This way the user can control whether the XN flag will be set on the
requested mappings. The IOMMU_NOEXEC flag needs to be
On Thu, Feb 26, 2015 at 8:19 PM, Wang Nan wrote:
> As early_trap_init() doesn't use IST, replace set_intr_gate_ist() and
> set_system_intr_gate_ist() with their standard counterparts.
>
> set_intr_gate() requires a trace_debug symbol which we don't have and
> won't use. This patch seprates
On 02/25/2015 03:32 PM, John Stultz wrote:
> I've hosted my timekeeping tests on github for the last few years:
> https://github.com/johnstultz-work/timetests
>
> but I suspect not too many folks have actually used them.
>
> I've been meaning to get them reworked and submitted into the
>
On Thu, Feb 26, 2015 at 12:12:31PM -0500, Rik van Riel wrote:
> On Thu, 26 Feb 2015 19:05:57 +0800
> Zefan Li wrote:
>
> > Make it return -ENOMEM ? Or make it a global variable and allocate memory
> > for it
> > in cpuset_init().
>
> Here you are. This addresses your concern, as well as the
>
On 02/25/2015 03:32 PM, John Stultz wrote:
> Try to streamline the makefile so its easier to add timer/timekeeping
> tests.
>
> Cc: Shuah Khan
> Cc: Prarit Bhargava
> Cc: Thomas Gleixner
> Cc: Richard Cochran
> Signed-off-by: John Stultz
> ---
> tools/testing/selftests/timers/Makefile | 9
From: Antonios Motakis
This patch enables the IOCTLs VFIO_DEVICE_GET_REGION_INFO ioctl call,
which allows the user to learn about the available MMIO resources of
a device.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 106
From: Antonios Motakis
Level sensitive interrupts are exposed as maskable and automasked
interrupts and are masked and disabled automatically when they fire.
Signed-off-by: Antonios Motakis
[Baptiste Reynal: Move masked interrupt initialization from "vfio/platform:
trigger an interrupt via
From: Antonios Motakis
This patch allows to set an eventfd for a platform device's interrupt,
and also to trigger the interrupt eventfd from userspace for testing.
Level sensitive interrupts are marked as maskable and are handled in
a later patch. Edge triggered interrupts are not advertised as
From: Antonios Motakis
We want to reuse virqfd functionality in multiple VFIO drivers; before
moving these functions to core VFIO, add the vfio_ prefix to the
virqfd_enable and virqfd_disable functions, and export them so they can
be used from other modules.
Signed-off-by: Antonios Motakis
From: Antonios Motakis
Enable building the VFIO AMBA driver. VFIO_AMBA depends on VFIO_PLATFORM,
since it is sharing a portion of the code, and it is essentially implemented
as a platform device whose resources are discovered via AMBA specific APIs
in the kernel.
Signed-off-by: Antonios Motakis
From: Antonios Motakis
VFIO_PCI passes the VFIO device structure *vdev via eventfd to the handler
that implements masking/unmasking of IRQs via an eventfd. We can replace
it in the virqfd infrastructure with an opaque type so we can make use
of the mechanism from other VFIO bus drivers.
From: Antonios Motakis
Now we have finally completely decoupled virqfd from VFIO_PCI. We can
initialize it from the VFIO generic code, in order to safely use it from
multiple independent VFIO bus drivers.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
From: Antonios Motakis
With this patch the VFIO user will be able to set an eventfd that can be
used in order to mask and unmask IRQs of platform devices.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_irq.c | 47
From: Antonios Motakis
The virqfd functionality that is used by VFIO_PCI to implement interrupt
masking and unmasking via an eventfd, is generic enough and can be reused
by another driver. Move it to a separate file in order to allow the code
to be shared.
Signed-off-by: Antonios Motakis
From: Antonios Motakis
The Virqfd code needs to keep accesses to any struct *virqfd safe, but
this comes into play only when creating or destroying eventfds, so sharing
the same spinlock with the VFIO bus driver is not necessary.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
On Mon, 02 Mar 2015, Peter Griffin wrote:
> Currently the ahci_st driver will hang the system on probe, as the
> st_configure_oob function does some register writes before the IP
> is clocked. This patch moves the function call to after
> ahci_platform_enable_resources (which enables the IP
From: Antonios Motakis
VFIO returns a file descriptor which we can use to manipulate the memory
regions of the device. Usually, the user will mmap memory regions that are
addressable on page boundaries, however for memory regions where this is
not the case we cannot provide mmap functionality
From: Antonios Motakis
This patch is a skeleton for the VFIO_DEVICE_SET_IRQS IOCTL, around which
most IRQ functionality is implemented in VFIO.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 52 +--
From: Antonios Motakis
Add support for discovering AMBA devices with VFIO and handle them
similarly to Linux platform devices.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_amba.c | 115 ++
From: Antonios Motakis
Allow to memory map the MMIO regions of the device so userspace can
directly access them. PIO regions are not being handled at this point.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform_common.c | 65
From: Antonios Motakis
Return information for the interrupts exposed by the device.
This patch extends VFIO_DEVICE_GET_INFO with the number of IRQs
and enables VFIO_DEVICE_GET_IRQ_INFO.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/Makefile
From: Antonios Motakis
A VFIO userspace driver will start by opening the VFIO device
that corresponds to an IOMMU group, and will use the ioctl interface
to get the basic device info, such as number of memory regions and
interrupts, and their properties. This patch enables the
From: Antonios Motakis
Enable building the VFIO PLATFORM driver that allows to use Linux platform
devices with VFIO.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/Kconfig | 1 +
drivers/vfio/Makefile | 1 +
drivers/vfio/platform/Kconfig |
From: Antonios Motakis
The functions vfio_pci_virqfd_init and vfio_pci_virqfd_exit are not really
PCI specific, since we plan to reuse the virqfd code with more VFIO drivers
in addition to VFIO_PCI.
Signed-off-by: Antonios Motakis
[Baptiste Reynal: Move rename vfio_pci_virqfd_init and
On Mon, 02 Mar 2015, Peter Griffin wrote:
> As part of testing ahci_st driver working on stih407 I noticed
> several things wrong in the DT documentation: -
>
> 1) Compatible string doesn't match the driver code
> 2) pwr-rst reset isn't documented (but exists in the driver)
> 3) some whitespace
On Sat, Feb 28, 2015 at 05:39:53PM +0800, Qiao Zhou wrote:
> On 02/23/2015 07:23 PM, Vinod Koul wrote:
> >On Thu, Feb 05, 2015 at 08:54:19PM +0800, Qiao Zhou wrote:
> >>Below are the refinements.
> >>1. Set DMA abort bit when disabling dma channel. This will clear
> >>the remaining data in dma
On Mon, 02 Mar 2015, Peter Griffin wrote:
> Now that the miphy28lp is upstream, we can add the sata dt nodes
> for stih407 family silicon. This has been tested on b2120 board
> J4 (sata0 channel). These nodes are disabled by default as a
> special mini pci-e to sata daughter board is required
From: Antonios Motakis
Replace the function vfio_domains_have_iommu_cache() with a more generic
function vfio_domains_have_iommu_cap() which allows to check all domains
of an vfio_iommu structure for a given cached capability.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
From: Antonios Motakis
Driver to bind to Linux platform devices, and callbacks to discover their
resources to be used by the main VFIO PLATFORM code.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
drivers/vfio/platform/vfio_platform.c | 103
From: Antonios Motakis
VFIO_IOMMU_TYPE1 keeps track for each domain it knows a list of protection
flags it always applies to all mappings in the domain. This is used for
domains that support IOMMU_CAP_CACHE_COHERENCY.
Refactor this slightly, by keeping track instead that a given domain
supports
On 03/02/2015 10:03 AM, Radim Krčmář wrote:
2015-03-02 10:25-0500, Bandan Das:
Radim Krčmář writes:
2015-03-01 21:29-0500, Bandan Das:
Joel Schopp writes:
+static int wbinvd_interception(struct vcpu_svm *svm)
+{
+ kvm_emulate_wbinvd(>vcpu);
+ skip_emulated_instruction(>vcpu);
On Mon, Mar 02, 2015 at 02:16:35PM +0800, Zefan Li wrote:
> Hi Tejun,
>
> Could you pick up those bug fixes? Or should I ask Ingo/akpm to take
> care of them?
Sorry about the delay. Applied to cgroup/for-4.0-fixes. Will push
out in a week.
Thanks.
--
tejun
--
To unsubscribe from this list:
From: Antonios Motakis
Currently a VFIO driver's IOMMU capabilities are encoded as a series of
numerical defines. Replace this with an enum for future maintainability.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
include/uapi/linux/vfio.h | 24 +++-
On Mon, Mar 2, 2015 at 4:26 AM, Daniel Borkmann wrote:
> On 03/02/2015 12:51 PM, Masami Hiramatsu wrote:
>> (2015/03/02 20:10), Daniel Borkmann wrote:
>>>
>>> Well, currently all possible map types (hash table, array map) that
>>> would actually call into bpf_register_map_type() are only built
On Mon, Mar 02, 2015 at 10:24:40AM +0100, Peter Zijlstra wrote:
> On Sat, Feb 28, 2015 at 03:32:03PM -0800, Paul E. McKenney wrote:
> > Whew!
> >
> > Though otherwise whatever you were doing would have been pretty cool
> > and fun to learn about. ;-)
>
> So I think I can do that; where readers
On Mon, Mar 2, 2015 at 1:04 AM, Daniel Vetter wrote:
>
> And can you please attach a bactrace of the WARN in your patch, just to
> double-check you blow up at the same spot?
So the dmesg I attached had a backtrace for the new WARN_ONCE() (in
addition to an unrelated(?) one from
> On Mar 2, 2015, at 6:57 PM, Alexandre Belloni
> wrote:
>
> On 02/03/2015 at 18:50:27 +0800, Jean-Christophe PLAGNIOL-VILLARD wrote :
>>
>>> On Mar 2, 2015, at 6:42 PM, Alexandre Belloni
>>> wrote:
>>>
>>> On some platforms, there are multiple SRAM nodes defined in the device tree
>>>
This patch is a fix to "iommu/arm-smmu: add support for iova_to_phys
through ATS1PR".
According to ARM documentation, translation registers are optional even
in SMMUv1, so ID0_S1TS needs to be checked to verify their presence.
Signed-off-by: Baptiste Reynal
---
drivers/iommu/arm-smmu.c | 2 +-
Hi Paul, Uwe,
2015-02-20 22:48 GMT+01:00 Paul Bolle :
> On Fri, 2015-02-20 at 20:54 +0100, Uwe Kleine-König wrote:
>> On Fri, Feb 20, 2015 at 07:01:03PM +0100, Maxime Coquelin wrote:
>> > This patch adds clocksource support for ARMv7-M's System timer,
>> > also known as SysTick.
>> >
>> >
Am 02.03.2015 um 17:43 schrieb Michael Mueller:
> On Mon, 02 Mar 2015 14:57:21 +0100
> Andreas Färber wrote:
>
>>> int configure_accelerator(MachineState *ms)
>>> {
>>> -const char *p;
>>> +const char *p, *name;
>>> char buf[10];
>>> int ret;
>>> bool accel_initialised =
On 3/2/15, 10:41, "Tejun Heo" wrote:
>On Mon, Mar 02, 2015 at 02:27:20AM -0600, Suravee Suthikulpanit wrote:
>> This patch adds ACPI supports for AHCI platform driver, which uses _CLS
>> method to match the device.
>>
>> The following is an example of ASL structure in DSDT for a SATA
On Sat, Feb 28, 2015 at 10:25:06PM +, Colin King wrote:
> From: Colin Ian King
>
> Fix spelling mistake, "aquire" -> "acquire" and missing newline (as
> spotted by Joe Perches.
>
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 02/27/2015 05:27 PM, Joe Perches wrote:
> On Fri, 2015-02-27 at 17:18 -0600, Suman Anna wrote:
>> Fix the following checkpatch warning,
>> WARNING: quoted string split across lines
>> +"\n\t\tName of DSP firmware file in /lib/firmware"
>> +" (if not specified
On 28/02/2015 10:01, Brian Norris wrote:
> On Wed, Feb 18, 2015 at 11:32:07AM +0100, Maxime Ripard wrote:
>> The NDDB register holds the data that are needed by the read and write
>> commands.
>>
>> However, during a read PIO access, the datasheet specifies that after each 32
>> bytes read in that
On 03/02/2015 11:32 AM, Borislav Petkov wrote:
> On Mon, Mar 02, 2015 at 11:33:33PM +0900, Naoya Horiguchi wrote:
>> Yes, CPU offlining is one option to keep other CPUs quiet. I'm not sure why
>> current kexec implementation doesn't offline the other CPUs but just doing
>> cpu_relax() loop, but
On 02/27/2015 05:26 PM, Joe Perches wrote:
> On Fri, 2015-02-27 at 17:18 -0600, Suman Anna wrote:
>> Fix couple of checkpatch warnings of the type,
>> "WARNING: Missing a blank line after declarations"
> []
>> diff --git a/drivers/remoteproc/ste_modem_rproc.c
>>
On 03/02/2015 04:23 PM, Jeff Layton wrote:
These look good at first glance, but I do need to go over patches 3 and
4 in more detail.
FWIW, usually when I see "RFC" in the subject, I take it as a hint that
this is still work-in-progress and that you're looking for early feedback
on it, and hence
On Fri, Feb 20, 2015 at 11:42:31AM +0100, Michal Simek wrote:
> Hi Vinod,
>
> On 02/20/2015 07:29 AM, Vinod Koul wrote:
> > On Sat, Feb 14, 2015 at 02:21:52PM +, Appana Durga Kedareswara Rao
> > wrote:
> >> Hi Vinod,
> >>
> >>
> >>> -Original Message-
> >>> From: Vinod Koul
On Mon, 02 Mar 2015 14:57:21 +0100
Andreas Färber wrote:
> > int configure_accelerator(MachineState *ms)
> > {
> > -const char *p;
> > +const char *p, *name;
> > char buf[10];
> > int ret;
> > bool accel_initialised = false;
> > bool init_failed = false;
> >
On Mon, Mar 02, 2015 at 02:27:20AM -0600, Suravee Suthikulpanit wrote:
> This patch adds ACPI supports for AHCI platform driver, which uses _CLS
> method to match the device.
>
> The following is an example of ASL structure in DSDT for a SATA controller,
> which contains _CLS package to be
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.81 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
On Mon, 2015-03-02 at 11:37 -0500, Steven Rostedt wrote:
> On Mon, 2 Mar 2015 10:01:00 -0600
> Tom Zanussi wrote:
>
> > Add a gfp flag that allows kmalloc() et al to be used in tracing
> > functions.
> >
> > The problem with using kmalloc for tracing is that the tracing
> > subsystem should be
On Sun, Mar 1, 2015 at 10:28 AM, Richard Cochran
wrote:
> On Wed, Feb 25, 2015 at 02:32:05PM -0800, John Stultz wrote:
>> Thoughts or comments here would be greatly appreciated!
>
> I only browsed through just to get an idea of the various tests, and
> the series looks good to me.
Thanks for the
On Mon, 2 Mar 2015 10:01:00 -0600
Tom Zanussi wrote:
> Add a gfp flag that allows kmalloc() et al to be used in tracing
> functions.
>
> The problem with using kmalloc for tracing is that the tracing
> subsystem should be able to trace kmalloc itself, which it can't do
> directly because of
* Murali Karicheri [150227 12:59]:
> On 02/27/2015 11:29 AM, Tony Lindgren wrote:
> >* Murali Karicheri [150224 13:31]:
> >>Keystone netcp driver re-uses davinci mdio driver. So enable it
> >>by default for keystone netcp driver.
> >>
> >>Signed-off-by: Murali Karicheri
> >>---
> >>
From: David Kaplan
We can make the in instruction go faster the same way the out instruction is
already.
Changes from v1
* Added kvm_fast_pio_in() implementation that was left out of v1
Signed-off-by: David Kaplan
[extracted from larger unlrelated patch, forward ported, tested]
Building with the attached random configuration file,
drivers/built-in.o: In function `i40e_cfgfs_group_make_item':
i40e_configfs.c:(.text+0x3df4ce): undefined reference to
`config_item_init_type_name'
drivers/built-in.o: In function `i40e_configfs_init':
(.text+0x3df4ee): undefined reference to
Hello,
On Mon, Mar 02, 2015 at 05:41:05PM +0900, Kamezawa Hiroyuki wrote:
> Let me start from explaining current behavior.
>
> - cpu-id is determined when a new processor(lapicid/x2apicid) is founded.
> cpu-id<->nodeid relationship is _not_ recorded.
Is this something from the firmware side
On Mon, Mar 02, 2015 at 11:33:33PM +0900, Naoya Horiguchi wrote:
> Yes, CPU offlining is one option to keep other CPUs quiet. I'm not sure why
> current kexec implementation doesn't offline the other CPUs but just doing
> cpu_relax() loop, but my guess is that in some kernel panic situation (like
On Mon, Mar 02, 2015 at 11:51:17PM +0900, Hitoshi Mitake wrote:
> I'm not sure I'm a suitable person for reviewing your patch, but I
> tested this patchset for perf bench with your latest (v2) patchset for
> x86 alternatives. It looks good to me.
> Reviewed-by: Hitoshi Mitake
Thanks a lot, I'll
On Mon, Mar 02, 2015 at 02:53:28PM +, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 381063133246 (PM / sleep: Re-implement suspend-to-idle handling)
> overlooked the fact that entering some sufficiently deep idle states
> by CPUs may cause their local timers to stop and in
On 03/02/2015 05:08 PM, Christoph Lameter wrote:
On Mon, 2 Mar 2015, Vlastimil Babka wrote:
You are thinking about an opportunistic allocation attempt in SLAB?
AFAICT SLAB allocations should trigger reclaim.
Well, let me quote your commit 952f3b51beb5:
This was about global reclaim.
On Mon, Mar 02, 2015 at 01:26:15PM +0100, Jesper Nilsson wrote:
> On Mon, Feb 09, 2015 at 05:15:27PM +0100, Tejun Heo wrote:
> > Hello,
>
> Hi!
>
> > This patch removes the possible hang by updating __cancel_work_timer()
> > to explicitly wait for clearing of CANCELING rather than invoking
> >
On Thu, Feb 26, 2015 at 10:16:09PM +, Eduardo Valentin wrote:
> On Thu, Feb 26, 2015 at 07:00:26PM +, Javi Merino wrote:
> > Hi linux-pm,
> >
> > The power allocator governor allocates device power to control
> > temperature. This requires transforming performance requests into
> >
From: Jorgen Hansen
The current maximum size of a queue in a queue pair is 128 MB. If
we increase that in the future, the queue pair allocation routines
may run into overflow issues. This change adds additional checks
to guard against this.
Acked-by: Andy King
Reported-by: Dan Carpenter
It's been almost a year, and development has slowed down enough that I felt
the need to draw a line under the last batch of work that went into trinity.
v1.5 is tagged in git, and tarballs available as usual at
http://www.codemonkey.org.uk/projects/trinity/
Going forward, I don't expect to have
On Mon, Mar 02, 2015 at 04:08:29PM +, Pawel Moll wrote:
> I'm not sure about this... The word "virtual" never works well with
> device tree nodes defined as "hardware description".
>
> I understand what you're doing, but adding this property to the display
> controller's node doesn't sound
On 02/23/2015 10:45 PM, Christoffer Dall wrote:
> On Mon, Jan 19, 2015 at 05:43:13PM +0100, Eric Auger wrote:
>> This patch enables irqfd on arm/arm64.
>>
>> Both irqfd and resamplefd are supported. Injection is implemented
>> in vgic.c without routing.
>>
>> This patch enables
* Valentin Rothberg [150302 05:39]:
> The IRQF_DISABLED flag is a NOOP and scheduled to be removed. According
> to commit e58aa3d2d0cc ("genirq: Run irq handlers with interrupts
> disabled") running IRQ handlers with interrupts enabled can cause stack
> overflows when the interrupt line of the
On 25/02/15 16:12, Ong Boon Leong wrote:
+config INTEL_QUARK_DTS_THERMAL
+ tristate "Intel Quark DTS thermal driver"
+ depends on X86 && IOSF_MBI
Since the change is in RC-1 suggest
depends on X86_INTEL_QUARK
you can skip this though it's not important.
Tested works for me:
On Wed, 2015-02-25 at 21:01 +, Arun Ramamurthy wrote:
> Added code based on linaro tree:
> http://git.linaro.org/kernel/linux-linaro-stable.git
> with commit id:6846e7822c4cab5a84672baace3b768c2d0db142
> at drivers/video/amba-clcd.c. This lets the driver set
> certain tim2 register bits after
* Valentin Rothberg [150302 06:04]:
> The IRQF_DISABLED flag is a NOOP and scheduled to be removed. According
> to commit e58aa3d2d0cc ("genirq: Run irq handlers with interrupts
> disabled") running IRQ handlers with interrupts enabled can cause stack
> overflows when the interrupt line of the
Currently update_sched_clock() is marked as notrace but this function
is not called by ftrace. This is trivially fixed by removing the mark
up.
Signed-off-by: Daniel Thompson
Reviewed-by: Stephen Boyd
---
kernel/time/sched_clock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
2015-03-02 10:25-0500, Bandan Das:
> Radim Krčmář writes:
> > 2015-03-01 21:29-0500, Bandan Das:
> >> Joel Schopp writes:
> >> > +static int wbinvd_interception(struct vcpu_svm *svm)
> >> > +{
> >> > +kvm_emulate_wbinvd(>vcpu);
> >> > +skip_emulated_instruction(>vcpu);
> >> > +
Removing the udelay between setting and clearing the soft reset bit in
the spfi control register as it is not required.
Signed-off-by: Sifan Naeem
Reviewed-by: Andrew Bresticker
---
drivers/spi/spi-img-spfi.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/spi/spi-img-spfi.c
+ if (in)
+ return kvm_fast_pio_in(vcpu, size, port);
Have I missed a patch that defined kvm_fast_pio_in()?
Not sure how I managed to leave out the bulk of the patch. Resending v2
momentarily.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Mon, Mar 02, 2015 at 05:02:57PM +0100, Mike Galbraith wrote:
> Well, those are the only ones we can do anything about. Dirt simple
> diddling of the workqueue default mask as sched domains are
> added/removed should do it I think. Automatically moving any existing
> unbound worker away from
This is v2 of my previously posted 'hashtriggers' patchset [1], but
renamed to 'hist triggers' following feedback from v1.
Since then, the kernel has gained a tracing map implementation in the
form of bpf_map, which this patchset makes a bit more generic, exports
and uses (as tracing_map_*, still
'hist' triggers allow users to continually aggregate trace events,
which can then be viewed afterwards by simply reading a 'hist' file
containing the aggregation in a human-readable format.
The basic idea is very simple and boils down to a mechanism whereby
trace events, rather than being
On Mon, 2 Mar 2015, Vlastimil Babka wrote:
> > You are thinking about an opportunistic allocation attempt in SLAB?
> >
> > AFAICT SLAB allocations should trigger reclaim.
> >
>
> Well, let me quote your commit 952f3b51beb5:
This was about global reclaim. Local reclaim is good and that can be
Make the bpf map implementation available outside of kernel/bpf - as a
general-purpose map implementation for tracing, it should be available
to any tracing facility that can make use of it, not just the bpf
syscall.
Create a set of exported tracing_map_* functions and have the bpf
implementation
Add a gfp flag that allows kmalloc() et al to be used in tracing
functions.
The problem with using kmalloc for tracing is that the tracing
subsystem should be able to trace kmalloc itself, which it can't do
directly because of paths like kmalloc()->trace_kmalloc()->kmalloc()
or
On 03/02/2015 04:46 PM, Christoph Lameter wrote:
> On Mon, 2 Mar 2015, Vlastimil Babka wrote:
>
>> So it would be IMHO better for longer-term maintainability to have the
>> relevant __GFP_THISNODE callers pass also __GFP_NO_KSWAPD to denote these
>> opportunistic allocation attempts, instead of
Make is_string_field() and is_function_field() accessible outside of
trace_event_filters.c for other users of ftrace_event_fields.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 12
kernel/trace/trace_events_filter.c | 12
2 files changed, 12
Make the kmalloc function in slab.h into a macro, and define a normal
and a _notrace version.
The _notrace version is for tracing code that wants to be able to use
kmalloc for its purposes but at the same time be able to trace kmalloc
and friends. Examples would be the bpf map and hist triggers
On Mon, 2015-03-02 at 10:29 -0500, Tejun Heo wrote:
> On Mon, Mar 02, 2015 at 01:44:50PM +0100, Mike Galbraith wrote:
> > Hm, I'm now all system-disease-ified now (still hate the bloody thing),
> > and have no problem isolating cpus via cpusets, modulo workqueues
> > wanting a bat upside the head.
Add a utility function to grab the syscall name from the syscall
metadata, given a syscall id.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 5 +
kernel/trace/trace_syscalls.c | 11 +++
2 files changed, 16 insertions(+)
diff --git a/kernel/trace/trace.h
On Mon, Mar 02, 2015 at 02:51:35PM +, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Move the fallback code path in cpuidle_idle_call() to the end of the
> function to avoid jumping to a label in a an if () branch.
Nit: "in an if () branch"
> Signed-off-by: Rafael J. Wysocki
> ---
We need to prevent any kmallocs that could be invoked from within a
tracepoint handler from being traced, in order to prevent recursion.
For tracing maps, this means the allocation of the map elements (maps
themselves along with their associated buckets, etc, are never
allocated in the context of
Some triggers may need access to the trace event, so pass it in. Also
fix up the existing trigger funcs and their callers.
Signed-off-by: Tom Zanussi
---
include/linux/ftrace_event.h| 7 ---
kernel/trace/trace.h| 6 --
kernel/trace/trace_events_trigger.c | 35
External users of the tracing_map API may customize their map usage
and need to be notified of certain events occuring during the lifetime
of a map.
One example would be element deletion - if private data has been
associated with an element's value, the client should be notified when
that element
601 - 700 of 2256 matches
Mail list logo
