If frequency is throttled due to OCC reset then cpus will be in Psafe
frequency, so restore the frequency on all cpus to policy->cur when
OCCs are active again. And if frequency is throttled due to Pmax
capping then restore the frequency of all the cpus in the chip on
unthrottling.
Re-evaluate the chip's throttled state on recieving OCC_THROTTLE
notification by executing *throttle_check() on any one of the cpu on
the chip. This is a sanity check to verify if we were indeed
throttled/unthrottled after receiving OCC_THROTTLE notification.
We cannot call *throttle_check()
This takes a stab at sizing the xsave buffer so that it will work for
AVX-512 systems. The logic is explained in the comment.
Cc: Linus Torvalds
Cc: Ingo Molnar
Cc: Linux Kernel Mailing List
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Fenghua Yu
Cc: "H. Peter Anvin"
Cc: leg Nesterov
Cc:
This is _very_ lightly tested. Just RFC for now. The fallback
code is not tested at all because I'm hitting another bug.
--
The recent x86 FPU rework changed a dynamic allocation to a
static one. But, the static one is undersized and we overrun it,
corrupting memory in some cases.
This
From: Byungchul Park
hello paul,
can i ask you something?
when a sched entity is both waken and migrated, it looks being decayed twice.
did you do it on purpose?
or am i missing something? :(
thanks,
byungchul
--->8---
>From 793c963d0b29977a0f6f9330291a9ea469cc54f0
OCC is an On-Chip-Controller which takes care of power and thermal
safety of the chip. During runtime due to power failure or
overtemperature the OCC may throttle the frequencies of the CPUs to
remain within the power budget.
We want the cpufreq driver to be aware of such situations to be able
to
Add OPAL_MSG_OCC message definition to opal_message_type to receive
OCC events like reset, load and throttled. Host performance can be
affected when OCC is reset or OCC throttles the max Pstate.
We can register to opal_message_notifier to receive OPAL_MSG_OCC type
of message and report it to the
From: Borislav Petkov
Hi,
here are two microcode loader changes for making certain patch levels
applied by the firmware, final.
Please apply, thanks.
Borislav Petkov (2):
x86/microcode/amd: Extract current patch level read to a function
x86/microcode/amd: Do not overwrite final patch
This patchset intends to add frequency throttle reporting mechanism
to powernv-cpufreq driver when OCC throttles the frequency. OCC is an
On-Chip-Controller which takes care of the power and thermal safety of
the chip. The CPU frequency can be throttled during an OCC reset or
when OCC tries to
From: Borislav Petkov
Pave the way for checking the current patch level of the microcode in a
core. We want to be able to do stuff depending on the patch level - in
this case decide whether to update or not. But that will be added in a
later patch; here we do not introduce any functionality
On wo, 2015-07-15 at 11:15 +0800, Xing Zheng wrote:
> --- /dev/null
> +++ b/sound/soc/rockchip/rockchip_max98090.c
> +#define DRV_NAME "rockchip-snd-max98090"
> +static const struct of_device_id rockchip_max98090_of_match[] = {
> + { .compatible = "rockchip,rockchip-audio-max98090", },
> +
From: Borislav Petkov
A certain number of patch levels of applied microcode should not be
overwritten by the microcode loader, otherwise bad things will happen.
Check those and abort update if the current core has one of those final
patch levels applied by the BIOS. 32-bit needs special
The On-Chip-Controller(OCC) can throttle cpu frequency by reducing the
max allowed frequency for that chip if the chip exceeds its power or
temperature limits. As Pmax capping is a chip level condition report
this throttling behavior at chip level and also do not set the global
'throttled' on Pmax
Hi Bjorn,
On 07/15/2015 10:02 PM, Bjorn Andersson wrote:
The Qualcomm PM8941 WLED block is used for backlight and should therefor
be in the backlight framework and not in the LED framework. This moves
the driver and adapts to the backlight api instead.
Signed-off-by: Bjorn Andersson
---
From: "zilong.liu"
Remove key.h which is included twice in crypto_fname.c
Signed-off-by: zilong.liu
---
fs/ext4/crypto_fname.c |1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ext4/crypto_fname.c b/fs/ext4/crypto_fname.c
index 7dc4eb5..4c11768 100644
--- a/fs/ext4/crypto_fname.c
+++
On Wed, Jul 15, 2015 at 08:52:51AM +0530, Maninder Singh wrote:
> dev_kfree_skb checks for NULL pointer itself,
> Thus no need of explicit NULL check.
>
I hate these patches. I have told Markus to stop sending them but he
has issues so now I only complain when they introduce a bug. There was
Hi Linus,
2015-07-16 16:42 GMT+09:00 Linus Walleij :
> On Thu, Jul 16, 2015 at 9:35 AM, Masahiro Yamada
> wrote:
>> 2015-07-16 16:07 GMT+09:00 Linus Walleij :
>
ngpio == 248 for some SoCs,
and ngpio == 136 for some, etc.
>>>
>>> That is the wrong way to handle different SoC. That
2015-07-02 9:42 GMT+09:00 Chanwoo Choi :
> This patch add CPU clock configuration data and instantiate the CPU clock type
> for Exynos3250 to support Samsung specific cpu-clock type.
>
> Cc: Sylwester Nawrocki
> Cc: Tomasz Figa
> Signed-off-by: Chanwoo Choi
> Acked-by: Kyungmin Park
>
From: Ashok Raj
kexec could boot a kernel that could be legacy with no knowledge of
LMCE. Hence we should make sure we clear LMCE optin before kexec reboot.
Signed-off-by: Ashok Raj
Cc: Andy Lutomirski
Cc: Aravind Gopalakrishnan
Cc: Oleg Nesterov
Cc: Tony Luck
Cc: linux-edac
Cc: x86-ml
From: "Chen, Gong"
Use unified genpool to save Action Optional error events and put Action
Optional error handling in the same notification chain as MCE error
decoding.
[Tony: Folded in subsequent patch from Boris for early boot logging]
Signed-off-by: Chen, Gong
Link:
This used to flush out MCEs logged during early boot and which were in
the MCA registers from a previous system run. No need for that now,
since we're moving to a genpool.
Signed-off-by: Borislav Petkov
Suggested-by: Tony Luck
---
arch/x86/include/asm/mce.h | 2 +-
From: Ashok Raj
Remove unused function declarations.
Signed-off-by: Ashok Raj
Cc: Tony Luck
Cc: linux-edac
Cc: x86-ml
Link:
http://lkml.kernel.org/r/1435621095-4802-1-git-send-email-ashok@intel.com
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/mce.h | 4
1 file
Hi,
- Original Message -
> On Wed, Jul 15, 2015 at 05:30:50PM +0200, Levente Kurusa wrote:
> > Even if the signal was handled using signal(2) the message
> > would be printed. Fix that by checking whether the signal
> > is handled.
>
> Why?
One of the reasons is that arm64 prints the
From: "Chen, Gong"
printk() is not safe to use in MCE context. Add a lockless memory
allocator pool to save error records in MCE context. Those records will
be issued later, in a printk-safe context. The idea is inspired by
the APEI/GHES driver.
We're very conservative and allocate only two
From: "Chen, Gong"
An MCE is a rare event. Therefore, there's no need to have per-CPU
instances of both normal and IRQ workqueues. Make them both global.
[Tony: Folded in subsequent patch from Rui/Boris/Tony for early boot logging]
Signed-off-by: Chen, Gong
Link:
On Thu, Jul 16, 2015 at 9:35 AM, Masahiro Yamada
wrote:
> 2015-07-16 16:07 GMT+09:00 Linus Walleij :
>>> ngpio == 248 for some SoCs,
>>> and ngpio == 136 for some, etc.
>>
>> That is the wrong way to handle different SoC. That should be handled
>> by different compatible strings, and then you
From: "Chen, Gong"
Printing in MCE context is a no-no, currently, as printk is not
NMI-safe. If some of the notifiers on the MCE chain call do so, we may
deadlock. In order to avoid that, delay printk() to process context
where it is safe to do so.
[Tony: Folded in subsequent patch from Boris
Fix spaces before comma and indentation.
Signed-off-by: Guillaume Bienkowski
---
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 42 +--
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
Whenever the UART device driver gets closed from userland, the driver
disables the UART unit and then stops its clock to save power.
The bit which disabled the UART unit is described as:
"UART Enable. If this bit is set to 1, the UART is enabled. Data
transmission and reception occurs for
On Wed, Jul 15, 2015 at 01:30:14PM +0200, Ingo Molnar wrote:
> did you rebase a tree from Boris?
Yep, he did. We decided to do so because the fixes missed 4.2 and for
4.3 a clean rebase is just fine.
> Also, please send all patches as part of the submission so that I can
> comment on individual
On 15/07/15 19:57, David Daney wrote:
> On 07/15/2015 10:12 AM, Marc Zyngier wrote:
>> On 15/07/15 17:54, David Daney wrote:
>>> From: David Daney
>>>
>>> Needed to map SPI interrupt sources.
>>>
>>> Signed-off-by: David Daney
>>> ---
>>> drivers/irqchip/irq-gic-v3.c | 5 +
>>>
On Thu, Jul 9, 2015 at 3:55 AM, Masahiro Yamada
wrote:
> Kbuild should descend into drivers/pinctrl/ only when CONFIG_PINCTRL
> is enabled because everything under that directory depends on
> CONFIG_PINCTRL.
>
> We can avoid the conditional, ifeq ($(CONFIG_OF),y) ... endif.
>
> Signed-off-by:
Hi Stefan,
On Wednesday 15 July 2015 18:06:26 Stefan Wahren wrote:
> [...]
> > ---
>
> changelog for v2?
:) follows. Will send v3 which also contains the missing newline fix.
Thanks,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier PH1-LD6b SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add i2c pin-mux settings
> - sort members of
Hi Linus,
2015-07-16 16:07 GMT+09:00 Linus Walleij :
> On Thu, Jul 16, 2015 at 5:44 AM, Masahiro Yamada
> wrote:
>> 2015-07-15 23:15 GMT+09:00 Linus Walleij :
>
+ for (i = 0; i < chip->ngpio; i += UNIPHIER_GPIO_PORTS_PER_BANK) {
+ bank = i /
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier ProXstream2
> SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add i2c pin-mux settings
> - sort members of
On Thursday 16 July 2015 03:02:03 Rafael J. Wysocki wrote:
> On Sunday, June 21, 2015 01:20:32 PM Pali Rohár wrote:
> > To prevent race conditions on userspace processes with I/O some taks must be
> > called after processes are freezed. This patch adds new events which are
> > delivered by
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier PH1-Pro5 SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add i2c pin-mux settings
> - sort members of
On 07/16/2015 12:26 AM, Jan Kara wrote:
> So Dave's patches would go in only in the next merge window anyway so we
> still have like two-three weeks to decide which patchset to take. If you
> think it will take you longer, then merging Dave's patches makes some sense
> although I personally don't
On Thu, Jul 16, 2015 at 12:15 AM, Peter Zijlstra wrote:
> On Thu, Jul 16, 2015 at 08:02:03AM +0200, Stephane Eranian wrote:
>> Been running it for a couple of hours, so far so good. I will let it
>> run all night.
>
> Thanks!
>
Well, it died on NHM in the same function despite your patch. Need to
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier PH1-sLD8 SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add i2c pin-mux settings
> - sort members of
Hi Mark,
> > > > What is stacked mode?
> > > > -
> > > > ZynqMP GQSPI controller supports stacked mode with following
> > > functionalities:
> > > > 1) The Generic Quad-SPI controller also supports two SPI flash memories
> > > >in a shared bus arrangement to reduce IO pin
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier PH1-Pro4 SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add i2c pin-mux settings
> - sort members of
On Wed 15-07-15 08:01:05, Joe Perches wrote:
> On Wed, 2015-07-15 at 12:26 +0200, Jan Kara wrote:
> > I have created this patch set which removes ext3 driver (and some related
> > support
> > code) from the kernel. See changelog of patch 2/3 for more details.
>
> It'd be nice if you regenerate
On Wed 15-07-15 20:19:20, Oleg Nesterov wrote:
> On 07/15, Jan Kara wrote:
> > So I'm also in favor of Oleg's approach
> > as well. We just have to wait until he fixes the outstanding issues with
> > his code.
>
> Yes. I'll try to make the working version, hopefully this week.
>
> But,
>
> >
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> Add pin configuration and pinmux support for UniPhier PH1-LD4 SoC.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add missing "emmc_dat8" group
> - add i2c pin-mux settings
On 07/16/2015 05:20 AM, Tejun Heo wrote:
On Wed, Jul 01, 2015 at 11:16:54AM +0800, Tang Chen wrote:
...
- /* and there's no empty block */
- if (bi->start >= bi->end)
+ /* and there's no empty or non-exist block */
+ if (bi->start >=
On Wed 15-07-15 13:57:11, Andrew Morton wrote:
> On Wed, 15 Jul 2015 13:14:41 +0200 Michal Hocko wrote:
>
> > mem_cgroup structure is defined in mm/memcontrol.c currently which
> > means that the code outside of this file has to use external API even
> > for trivial access stuff.
> >
> > This
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
wrote:
> The core support for the pinctrl drivers for all the UniPhier SoCs.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - drop vogus THIS_MODULE because this file is always built-in
> - drop vogus "include because this
On Thu, 2015-07-16 at 14:54 +0800, Daniel Kurtz wrote:
> On Thu, Jul 16, 2015 at 1:38 PM, YH Huang wrote:
> > On Wed, 2015-07-15 at 23:59 +0800, YH Huang wrote:
> >> On Mon, 2015-07-13 at 18:19 +0800, Daniel Kurtz wrote:
> >> > On Mon, Jul 13, 2015 at 5:04 PM, YH Huang wrote:
> >> > > Add
On Thu, Jun 18, 2015 at 05:47:47PM +0530, Sudip Mukherjee wrote:
> allmodconfig build fails with the error:
> invalid use of undefined type 'struct kprobe_ctlblk'
>
> just declared the two basic structures after checking the struct in other
> architectures.
Gentle ping.
next-20150
Use NOKPROBE_SYMBOL() to protect handlers from kprobes
in sample modules.
Signed-off-by: Masami Hiramatsu
Ananth N Mavinakayanahalli
---
samples/kprobes/jprobe_example.c|1 +
samples/kprobes/kprobe_example.c|3 +++
samples/kprobes/kretprobe_example.c |2 ++
3 files changed,
Hi,
Here is a series of patches of kprobe blacklist enhancement
which I sent 1 yrs ago (with some performance improvements).
I've decided to split these patches from performance improvement
patches because it is easy to review/merge.
These 3 patches add NOKPROBE_SYMBOL() support for modules and
To blacklist the functions in a module (e.g. user-defined
kprobe handler and the functions invoked from it), expand
blacklist support for modules.
With this change, users can use NOKPROBE_SYMBOL() macro in
their own modules.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc:
On Wed, Jul 15, 2015 at 05:32:13PM -0700, David Miller wrote:
> From: Clemens Gruber
> Date: Thu, 16 Jul 2015 02:04:04 +0200
>
> > This reverts commit 6c3e921b18edca290099adfddde8a50236bf2d80.
> >
> > The change did break ethernet support on the i.MX6Q and possibly also on
> > other platforms:
Hello --
Your message was tagged as spam by an automated testing program.
Unless we receive a reply to this notice, the message will be set aside and
will not be seen or acted on by anyone.
Therefore, please reply to this message as soon as possible.
If you did not send any mail to an email
Fix typo s/CONFIG_TRANSPARENT_HUGEPAGES/CONFIG_TRANSPARENT_HUGEPAGE/
in #endif comment introduced by commit 2b26a9206d6a ("dax: add huge page
fault support").
Signed-off-by: Valentin Rothberg
---
fs/dax.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/dax.c b/fs/dax.c
On Thu, Jul 16, 2015 at 08:02:03AM +0200, Stephane Eranian wrote:
> Been running it for a couple of hours, so far so good. I will let it
> run all night.
Thanks!
> > ---
> > arch/x86/kernel/cpu/perf_event_intel_ds.c | 29
> > +
> > 1 file changed, 13 insertions(+),
Use kprobe_blackpoint for blacklisting .entry.text and .kprobees.text
instead of arch_within_kprobe_blacklist. This also makes them visible
via (debugfs)/kprobes/blacklist.
Signed-off-by: Masami Hiramatsu
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Ananth N Mavinakayanahalli
On Wed 15-07-15 15:44:36, David Rientjes wrote:
> OOM notifiers exist to give one last chance at reclaiming memory before
> the oom killer does its work.
>
> Thus, they don't actually belong in the oom killer proper, but rather in
> the page allocator where reclaim is invoked.
Why this is not
On Thu, Jul 16, 2015 at 5:44 AM, Masahiro Yamada
wrote:
> 2015-07-15 23:15 GMT+09:00 Linus Walleij :
>>> + for (i = 0; i < chip->ngpio; i += UNIPHIER_GPIO_PORTS_PER_BANK) {
>>> + bank = i / UNIPHIER_GPIO_PORTS_PER_BANK;
>>> + shift = i % BITS_PER_LONG;
>>> +
* Nishanth Menon [150715 06:44]:
> On 07/15/2015 01:26 AM, Tony Lindgren wrote:
> > * Nishanth Menon [150622 08:14]:
> >> DRA7 uses OMAP5 IO table at the moment. This is purely spurious since
> >> the OMAP5 and DRA7 register maps are different in many aspects.
> >>
> >> AM57xx/DRA7 TRM
On Mon, 2015-07-13 at 11:35 -0400, Mike Snitzer wrote:
> I will do additional review to answer 1 and 2 above. And Jeff Moyer
> told me he'd test the patchset on one of his testbeds.
Hi Jeff,
FYI, here is a fix for patch 1.
Or you can pull from my tree.
Hi Mark,
On Wed, Jul 15, 2015 at 10:50 PM, Mark Rutland wrote:
>
> On Wed, Jul 15, 2015 at 01:22:55PM +0100, Wendy Liang wrote:
> > Add documentation about the ZynqMP RPU remoteproc driver
> > DTS bindings.
> >
> > Signed-off-by: Jason Wu
> > Signed-off-by: Wendy Liang
> > ---
> >
2015-07-16 15:37 GMT+09:00 Duan Andy :
> From: Kamal Mostafa Sent: Thursday, July 16, 2015 9:08
> AM
>> To: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; kernel-
>> t...@lists.ubuntu.com
>> Cc: Kamal Mostafa; daniel.lezc...@linaro.org; kyungmin.p...@samsung.com;
>> Damian Eppel;
On Thu, Jul 16, 2015 at 1:38 PM, YH Huang wrote:
> On Wed, 2015-07-15 at 23:59 +0800, YH Huang wrote:
>> On Mon, 2015-07-13 at 18:19 +0800, Daniel Kurtz wrote:
>> > On Mon, Jul 13, 2015 at 5:04 PM, YH Huang wrote:
>> > > Add display PWM driver support to modify backlight for MT8173 and MT6595.
From: Kamal Mostafa Sent: Thursday, July 16, 2015 9:08 AM
> To: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; kernel-
> t...@lists.ubuntu.com
> Cc: Kamal Mostafa; daniel.lezc...@linaro.org; kyungmin.p...@samsung.com;
> Damian Eppel; kg...@kernel.org; Thomas Gleixner; linux-arm-
>
Christophe JAILLET writes:
> Use 'list_for_each_safe' instead of 'list_for_each' + own logic to keep
> safe when a list entry is deleted.
> Delete the now useless 'csio_list_prev' macro.
>
> Signed-off-by: Christophe JAILLET
> ---
> drivers/scsi/csiostor/csio_defs.h | 1 -
>
The Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks have
IIO based ADC thermistors. Enable built-in support for its driver.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes in v2:
- Add Krzysztof Kozlowski Reviewed-by tag in patch #3.
The Exynos5420 based Peach Pit and Exynos5800 based Peach Pi Chromebooks
use the Maxim max77802 Power Management IC (PMIC). This PMIC has besides
other devices, a set of regulators that can be controller over I2C.
Commit f3caa529c6f5 ("ARM: multi_v7_defconfig: Enable max77802 regulator,
rtc and
On 7/14/2015 11:28 PM, Alex Thorlton wrote:
We see the same exact messages on 4.1-rc8.
does this solves the problem?
diff --git a/include/linux/mlx4/device.h b/include/linux/mlx4/device.h
index ad31e47..c8ae3b9 100644
--- a/include/linux/mlx4/device.h
+++ b/include/linux/mlx4/device.h
@@
Hi Sato-san,
On Thu, Jul 16, 2015 at 7:15 AM, Yoshinori Sato
wrote:
> Current implemantation ptr argument evaluate 2 times.
> It'll be an unexpected result.
>
> Signed-off-by: Yoshinori Sato
Acked-by: Geert Uytterhoeven
> ---
> include/asm-generic/uaccess.h | 10 ++
> 1 file
> I have to say, I am a bit leery about applying the omap_device.c and
> omap_hwmod.c changes, since the called functions -- omap_device_delete()
> and clk_disable() -- don't explicitly document that NULLs are allowed
> to be passed in.
How are the chances to improve documentation around such
The Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks have
IIO based ADC thermistors. Enable module support for its driver
and also for the needed Exynos ADC driver.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes in v2:
- Add Krzysztof Kozlowski
Hello Kukjin and Krzysztof,
This series enables support in exynos_defconfig and multi_v7_defconfig
for the NTC Thermistors found on the Exynos5 Peach Chromebooks and
also enables support for the max77802 regulators in multi_v7_defconfig.
This is the second version that address issues pointed out
On Wed, Jul 15, 2015 at 02:13:26PM +0200, Sebastian Reichel wrote:
> -static int tsc2005_write(struct tsc2005 *ts, u8 reg, u16 value)
> -{
> - u32 tx = ((reg | TSC2005_REG_PND0) << 16) | value;
> - struct spi_transfer xfer = {
> - .tx_buf = ,
> - .len
This patch update the Documentation/filesystems/debugfs.txt
file. The main work is to add the description of the following
functions:
debugfs_create_atomic_t
debugfs_create_u32_array
debugfs_create_devm_seqfile
debugfs_create_file_size
Signed-off-by: Wang Long
---
Hi all,
For those that care: I have stopped signing these messages because
vger's mailing list software destroys the signatures and then Google
(at least) assumes that they are spam. I could clear sign them instead
(if anyone thinks that is worth while).
Changes since 20150715:
Removed tree:
* Paul Walmsley [150715 22:58]:
> Hello Markus
>
> On Tue, 30 Jun 2015, SF Markus Elfring wrote:
>
> > From: Markus Elfring
> > Date: Tue, 30 Jun 2015 14:00:16 +0200
> >
> > The functions clk_disable(), of_node_put() and omap_device_delete() test
> > whether their argument is NULL and then
On 16.07.2015 14:44, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> Thanks for the feedback.
>
> On 07/16/2015 02:45 AM, Krzysztof Kozlowski wrote:
>> On 16.07.2015 01:32, Javier Martinez Canillas wrote:
>>> The Maxim max77802 Power Management IC has besides other devices, a set of
>>>
On 2015/07/16 11:16, Wang Long wrote:
> In debugfs_kprobe_init, we create a directory 'kprobes' and three
> files 'list', 'enabled' and 'blacklist'. When any one of the three
> files creation fails, we should remove all of them. But debugfs_remove
> function can not complete this work. So use
On Wed, Jul 15, 2015 at 02:48:00PM -0400, Matthew Wilcox wrote:
> On Wed, Jul 15, 2015 at 11:25:55AM -0600, Jens Axboe wrote:
> > On 07/15/2015 11:19 AM, Keith Busch wrote:
> > >On Wed, 15 Jul 2015, Bart Van Assche wrote:
> > >>* With blk-mq and scsi-mq optimal performance can only be achieved if
Hello Brian,
On Mon, 15 Jun 2015, Brian Hutchinson wrote:
> Clocks 4-7 are capable of PWM output on dm816x.
>
> This adds the pwm capability to those timers.
>
> Cc: Paul Walmsley
> Cc: Tero Kristo
> Cc: Tony Lindgren
> Signed-off-by: Brian Hutchinson >
This patch seems to be corrupted.
On Wed, 15 Jul 2015, I wrote:
> On Tue, 14 Jul 2015, Benjamin Herrenschmidt wrote:
>
> > Maybe we should have a dedicated accessor for "mac_xpram" ...
>
> ... I can see how to implement XPRAM for matroxfb and imsttfb
I'll have to retract that. The video mode and color mode settings used by
On Wed, Jul 15, 2015 at 2:35 PM, Peter Zijlstra wrote:
> On Wed, Jul 15, 2015 at 08:42:50AM +0200, Stephane Eranian wrote:
>> On Fri, Jul 3, 2015 at 9:49 PM, Vince Weaver
>> wrote:
>> > On Fri, 3 Jul 2015, Peter Zijlstra wrote:
>> >
>> >> That said, its far too warm and I might just not be
It's often useful to be able to use a stacktrace as a hash key, for
keeping a count of the number of times a particular call path resulted
in a trace event, for instance. Add a special key named 'stacktrace'
which can be used as key in a 'keys=' param for this purpose:
# echo
Allow users to have syscall id fields displayed as syscall names in
the output by appending '.syscall' to field names:
# echo hist:keys=aaa.syscall ... \
[ if filter] event/trigger
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
kernel/trace/trace.c | 1
If we assume the maximum size for a string field, we don't have to
worry about its position. Since we only allow two keys in a compound
key and having more than one string key in a given compound key
doesn't make much sense anyway, trading a bit of extra space instead
of introducing an arbitrary
On Wed, 15 Jul 2015, David Daney wrote:
From: David Daney david.da...@cavium.com
The subject pretty much says it all. The first four patches tweak the
infrastructure a little so that we can get required behavior. The
Just that you avoid to describe what the required behaviour is.
Can you
Allow users to specify multiple trace event fields to use in keys by
allowing multiple fields in the 'keys=' keyword. With this addition,
any unique combination of any of the fields named in the 'keys'
keyword will result in a new entry being added to the hash table.
Signed-off-by: Tom Zanussi
Allow users to append 'clear' to an existing trigger in order to have
the hash table cleared.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx:vals=yyy:sort=zzz.descending:pause/cont \
[ if filter] event/trigger
to this:
# echo
Allow users to append 'pause' or 'continue' to an existing trigger in
order to have it paused or to have a paused trace continue.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx:vals=yyy:sort=zzz.descending \
[ if filter] event/trigger
to this:
# echo
Allow users to specify trace event fields to use in aggregated sums
via a new 'vals=' keyword. Before this addition, the only aggregated
sum supported was the implied value 'hitcount'. With this addition,
'hitcount' is also supported as an explicit value field, as is any
numeric trace event
Add a utility function to grab the syscall name from the syscall
metadata, given a syscall id.
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
kernel/trace/trace.h | 5 +
kernel/trace/trace_syscalls.c | 11 +++
2 files changed, 16 insertions(+)
diff --git
Add tracing_map, a special-purpose lock-free map for tracing.
tracing_map is designed to aggregate or 'sum' one or more values
associated with a specific object of type tracing_map_elt, which
is associated by the map to a given key.
It provides various hooks allowing per-tracer customization and
Hi Linus,
A collection of fixes from the last few weeks that should go into the
current series. This pull request contains:
- Various fixes for the per-blkcg policy data, fixing regressions since
4.1 From Arianna and Tejun.
- Code cleanup for bcache closure macros from me. Really just
Add a simple per-trigger 'paused' flag, allowing individual triggers
to pause. We could leave it to individual triggers that need this
functionality to do it themselves, but we also want to allow other
events to control pausing, so add it to the trigger data.
Signed-off-by: Tom Zanussi
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 tom.zanu...@linux.intel.com
---
include/linux/trace_events.h| 7 ---
kernel/trace/trace.h| 6 --
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 tom.zanu...@linux.intel.com
---
kernel/trace/trace.h | 12
kernel/trace/trace_events_filter.c | 12
On 16/07/15 18:14, David Daney wrote:
On 07/16/2015 10:09 AM, Marc Zyngier wrote:
On 16/07/15 17:50, David Daney wrote:
[...]
Patch 5 has established that you're using virtual wire SPIs, so we
need to work on exposing that with the normal kernel abstraction, and
not by messing with the
901 - 1000 of 1970 matches
Mail list logo
