On Sat, Apr 16, 2016 at 11:03:32AM +0200, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > > I don't think we know yet if there's a reliable way to turn the bug off.
> > >
> > > Also, according to the gcc guys, this bug won't always result in a
> > > truncated function, and may sometimes ju
Provide *our* view of what the rules are for the different DAI formats,
so that we do not have to trust external interpretations for this
crucial bit of interoperability.
Signed-off-by: Peter Rosin
---
Documentation/sound/alsa/soc/clocking.txt | 145 +-
1 file changed
On 15/04/16 15:12, Will Deacon wrote:
On Fri, Apr 15, 2016 at 03:10:27PM +0100, Suzuki K Poulose wrote:
On 14/04/16 18:49, Suzuki K Poulose wrote:
On 14/04/16 18:39, Will Deacon wrote:
On Wed, Apr 06, 2016 at 12:24:13PM +0100, Suzuki K Poulose wrote:
CPU Errata work arounds are detected and a
On Mon, Apr 18, 2016 at 8:19 AM, Eric Dumazet wrote:
> On Mon, 2016-04-18 at 11:44 +0300, Dan Carpenter wrote:
>> We deleted a line of code and accidentally made the "return put_user()"
>> part of the if statement when it's supposed to be unconditional.
>>
>> Fixes: 9f9a45beaa96 ('udp: do not expe
Impact: clearify meaning
Suggested-by: Andy Lutomirski
Suggested-by: Ingo Molnar
Signed-off-by: Dmitry Safonov
Acked-by: Andy Lutomirski
---
v3: initial patch
arch/x86/entry/common.c| 2 +-
arch/x86/include/asm/compat.h | 4 ++--
arch/x86/include/asm/thread_info.h | 2 +-
ar
Add possibility for userspace 32-bit applications to move
vdso mapping. Previously, when userspace app called
mremap for vdso, in return path it would land on previous
address of vdso page, resulting in segmentation violation.
Now it lands fine and returns to userspace with remapped vdso.
This will
Should print on success:
[root@localhost ~]# ./test_mremap_vdso_32
AT_SYSINFO_EHDR is 0xf773f000
[NOTE] Moving vDSO: [f773f000, f774] -> [a00, a001000]
[OK]
Or segfault if landing was bad (before patches):
[root@localhost ~]# ./test_mremap_vdso_32
AT_SYSINFO_EHDR is 0xf774f
On Thu 2016-04-14 17:16:40, Huang Shijie wrote:
> The patch "3033f14a clone: support passing tls argument via C rather ..."
> added the tls argument for _do_fork(). The patch adds the "tls" argument
> for j_do_fork to make it match _do_fork().
>
> Acked-by: Steve Capper
> Cc: Masami Hiramatsu
>
On Mon, 18 Apr 2016, Bob Tracy wrote:
> Build delayed slightly. Ran into "fs/binfmt_em86.o" build failure
> patched by Daniel Wagner back in February (incompatible-pointer-types
> warning treated as error by compiler). Is Daniel's patch queued for
> incorporation into the main kernel source tree
On 04/18/2016 05:08 PM, Rafał Miłecki wrote:
> On 18 April 2016 at 13:24, Mark Brown wrote:
>> On Mon, Apr 18, 2016 at 01:10:43PM +0200, Rafał Miłecki wrote:
>>
>>> +static int bcm53xxspi_flash_read(struct spi_device *spi,
>>> + struct spi_flash_read_message *msg)
>>
Boris,
On 18/04/16 16:13, Boris Brezillon wrote:
> Hi Roger,
>
> On Mon, 18 Apr 2016 15:52:58 +0300
> Roger Quadros wrote:
>
>> On 18/04/16 15:31, Roger Quadros wrote:
>>> On 16/04/16 11:57, Boris Brezillon wrote:
On Fri, 15 Apr 2016 09:19:51 -0700
Tony Lindgren wrote:
>
>>>
On 4/18/2016 9:10 AM, Christoph Hellwig wrote:
> On Mon, Apr 18, 2016 at 09:06:18AM -0400, ok...@codeaurora.org wrote:
>> On 2016-04-18 08:12, Christoph Hellwig wrote:
>>> On Sat, Apr 16, 2016 at 06:23:32PM -0400, Sinan Kaya wrote:
Current code is assuming that the address returned by dma_allo
On 4/18/2016 2:54 AM, Eli Cohen wrote:
> Sinan,
>
> if we get rid of the part this code:
>
> if (BITS_PER_LONG == 64) {
> struct page **pages;
> pages = kmalloc(sizeof *pages * buf->nbufs, gfp);
> if (!pages)
This is a fix for a NULL pointer dereference from cpsw which is triggered
by having two slave PHYs attached to a cpsw network device. The problem is
due to only maintaining a single reference to a PHY node in the prive data
which gets overwritten by the second PHY probe. So move the PHY node
refere
Adding a 2nd PHY to cpsw results in a NULL pointer dereference
as below. Fix by maintaining a reference to each PHY node in slave
struct instead of a single reference in the priv struct which was
overwritten by the 2nd PHY.
[ 17.870933] Unable to handle kernel NULL pointer dereference at virtual
On Mon, Apr 18, 2016 at 10:34 AM, Jinpu Wang
wrote:
> On Sat, Apr 16, 2016 at 3:50 AM, Christoph Hellwig wrote:
>>> - blk_queue_max_discard_sectors(brd->brd_queue, UINT_MAX);
>>> + blk_queue_max_discard_sectors(brd->brd_queue, UINT_MAX >> 9);
>>
>> Shouldn't we fix the issue by capping to
On 04/18/2016 01:32 AM, Oliver Neukum wrote:
On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
This patch creates new driver that supports StreamLabs usb watchdog
device. This device plugs into 9-pin usb header and connects to
reset pin and reset button on common PC.
USB commands used to
On Sat, Apr 16, 2016 at 06:18:38AM +1000, Dave Airlie wrote:
> This was just a random thought process I was having last night, and
> wondered if it was possible.
>
> We have a scenario with OpenGL where certain APIs hand large amounts
> of data from the user to the API and when you return from the
On Mon, Apr 18, 2016 at 09:49:10AM -0400, Sinan Kaya wrote:
> Here is a good description of logical address vs. virtual address.
>
> https://www.quora.com/What-is-the-Kernel-logical-and-virtual-addresses-What-is-the-difference-between-them-What-is-the-type-of-addresses-listed-in-the-System-map
Th
On Mon, Apr 18, 2016 at 06:32:08AM +, Wang Nan wrote:
> Use 'trigger' to model operations which need to be executed when
> an event (a signal, for example) is observed.
>
> States and transits:
>
> OFF--(on)--> READY --(toggle)--> TOGGLED --(process)--> PROCESSING
> ^
While VGA hotplugging worked(ish) before, it looks like that was mainly
because we'd unintentionally enable it in
valleyview_crt_detect_hotplug() when we did a force trigger. This
doesn't work reliably enough because whenever the display powerwell on
vlv gets disabled, the values set in VLV_ADPA ge
Hi Dmitry,
[auto build test WARNING on v4.6-rc4]
[also build test WARNING on next-20160418]
[cannot apply to tip/x86/core tip/x86/vdso]
[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/Dmitry
On Mon, 2016-04-18 at 16:12 +0300, Michael S. Tsirkin wrote:
> I'm not sure I understand the issue. The public API is not about how
> the driver works. It doesn't say "don't use DMA API" anywhere, does it?
> It's about telling device whether to obey the IOMMU and
> about discovering whether a dev
Em Sat, Apr 16, 2016 at 12:46:14PM -0700, Andres Freund escreveu:
> Hi,
>
> Perhaps this should also go into stable? It'd be nice to fix that
> regression for 4.4 and 4.5.
Yeah, that would be good, just send that request to sta...@kernel.org.
- Arnaldo
> Regards,
>
> Andres
>
> On 2016-03-30
On Mon, 18 Apr 2016 16:48:26 +0300
Roger Quadros wrote:
> Boris,
>
> On 18/04/16 16:13, Boris Brezillon wrote:
> > Hi Roger,
> >
> > On Mon, 18 Apr 2016 15:52:58 +0300
> > Roger Quadros wrote:
> >
> >> On 18/04/16 15:31, Roger Quadros wrote:
> >>> On 16/04/16 11:57, Boris Brezillon wrote:
> >
On Mon, Apr 18, 2016 at 06:45:54PM +0530, Shardar Shariff Md wrote:
> - Define separate function for configuration load register handling
> to make it use by different functions later.
> - Instead of calculating timeout for the config load during init,
> calculate it when config load register is wr
On Mon, 18 Apr 2016, Peter Chen wrote:
> On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote:
> > On 06/04/16 09:09, Felipe Balbi wrote:
> > >
> > > Hi,
> > >
> > > Roger Quadros writes:
> > >> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
> > >> index 2ca2cef..6b1930d
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Monday, April 18, 2016 5:59 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; Haiyang Zhang
> ; Alex Ng (LIS) ; Cathy
> Avery ; de...@linuxdriverproject.org
> Subject: Re: [PATCH 0/2] Drivers: hv:
On Mon, Apr 18, 2016 at 04:07:51PM +0200, Arnd Bergmann wrote:
> On Monday 18 April 2016 08:39:32 Josh Poimboeuf wrote:
> >
> > I agree. So how should we work around the bug in this case? There have
> > been several suggestions:
> >
> > - change wwn_to_u64() to __always_inline
> >
> > - change
On Mon, 2016-04-18 at 06:57 -0700, Guenter Roeck wrote:
> On 04/18/2016 01:32 AM, Oliver Neukum wrote:
> > On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
> >> This patch creates new driver that supports StreamLabs usb watchdog
> >> device. This device plugs into 9-pin usb header and connec
On 18/04/16 14:59, Mark Brown wrote:
On Mon, Apr 18, 2016 at 02:49:53PM +0300, Tero Kristo wrote:
suspend_prepare can be called during regulator init time also, where
It can be? That seems unexpected...
regulator_register()
-> set_machine_constraints()
-> suspend_prepare()
Called if yo
On 04/16/2016 03:13 PM, Arnd Bergmann wrote:
The altera EDAC driver refers to its per-device data
using a cast to '(void *)', which makes the pointer
non-const, though both the source and destination are
actually const.
Removing the annotation makes the reference (almost)
fit into a single lin
On Monday 18 April 2016 08:39:32 Josh Poimboeuf wrote:
>
> I agree. So how should we work around the bug in this case? There have
> been several suggestions:
>
> - change wwn_to_u64() to __always_inline
>
> - change qla2x00_get_host_fabric_name() to skip the unnecessary call to
> wwn_to_u64(
/acme/linux.git
tags/perf-urgent-for-mingo-20160418
for you to fetch changes up to 1342e0b7a6c1a060c593037fbac9f4b717f1cb3b:
perf intel-pt: Fix segfault tracing transactions (2016-04-18 11:00:56 -0300)
perf/urgent fix:
- Fix
On Mon, Apr 18, 2016 at 06:44:06PM +0800, kbuild test robot wrote:
> Hi Rich,
>
> FYI, the error/warning still remains.
I can't find where I got any notification of it before. Thanks for
bringing it to my attention now though.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/li
From: Adrian Hunter
Tracing a workload that uses transactions gave a seg fault as follows:
perf record -e intel_pt// workload
perf report
Program received signal SIGSEGV, Segmentation fault.
0x0054b58c in intel_pt_reset_last_branch_rb (ptq=0x1a36110)
at util/intel-pt.c:92
On Mon, Apr 18, 2016 at 06:45:55PM +0530, Shardar Shariff Md wrote:
> To summarize the issue observed in error cases:
>
> SW Flow: For i2c message transfer, packet header and data payload is
> posted and then required error/packet completion interrupts are enabled
> later.
>
> HW flow: HW process
On 04/16/2016 03:13 PM, Arnd Bergmann wrote:
The recently added Arria10 OCRAM ECC support caused some new
harmless warnings about unused functions when it is disabled:
drivers/edac/altera_edac.c:1067:20: error: 'altr_edac_a10_ecc_irq' defined but
not used [-Werror=unused-function]
drivers/eda
Add possibility for userspace 32-bit applications to move
vdso mapping. Previously, when userspace app called
mremap for vdso, in return path it would land on previous
address of vdso page, resulting in segmentation violation.
Now it lands fine and returns to userspace with remapped vdso.
This will
On 2016/4/18 21:45, Jiri Olsa wrote:
On Mon, Apr 18, 2016 at 06:32:08AM +, Wang Nan wrote:
Use 'trigger' to model operations which need to be executed when
an event (a signal, for example) is observed.
States and transits:
OFF--(on)--> READY --(toggle)--> TOGGLED --(process)--> PROCESS
On Monday 18 April 2016 09:12:41 Josh Poimboeuf wrote:
> On Mon, Apr 18, 2016 at 04:07:51PM +0200, Arnd Bergmann wrote:
> > On Monday 18 April 2016 08:39:32 Josh Poimboeuf wrote:
> > >
> > > I agree. So how should we work around the bug in this case? There have
> > > been several suggestions:
>
Hi Boris,
On 04/15/2016 04:46 PM, Borislav Petkov wrote:
On Fri, Apr 15, 2016 at 10:27:54AM -0500, Thor Thayer wrote:
I'll update this patch to only count errors.
... and also think about what that counting is going to bring. If it is
only going to be there to show how many network errors hap
Now that there are different revisions of the Pistachio SoC
in circulation, add this information to the boot log to make
it easier for users to determine which hardware they have.
Signed-off-by: James Hartley
Signed-off-by: Ionela Voinescu
diff --git a/arch/mips/pistachio/init.c b/arch/mips/pis
Hi,
Perhaps the patch quoted below should also go into stable? It'd be nice
to fix that regression for 4.4 and 4.5. It's been integrated into 4.6
(909890355).
Regards,
Andres
On 2016-03-30 23:33:37 -0700, tip-bot for Andres Freund wrote:
> Commit-ID: 909890355507e92bdaf648e73870f6b5df606da8
>
On Mon, 18 Apr 2016, Ralf Baechle wrote:
> The old case btw, affects ip22 with a random_config:
>
> CC arch/mips/mm/sc-ip22.o
> {standard input}: Assembler messages:
> {standard input}:137: Error: number (0x90008000) larger than 32 bits
> {standard input}:162: Error: number (0x9000
On Mon, Apr 18, 2016 at 10:20:23PM +0800, Wangnan (F) wrote:
>
>
> On 2016/4/18 21:45, Jiri Olsa wrote:
> >On Mon, Apr 18, 2016 at 06:32:08AM +, Wang Nan wrote:
> >>Use 'trigger' to model operations which need to be executed when
> >>an event (a signal, for example) is observed.
> >>
> >>Stat
On Sun, Apr 17, 2016 at 03:14:34PM +0200, Arnd Bergmann wrote:
> On Tuesday 12 April 2016 09:03:38 Rob Herring wrote:
> > On Mon, Apr 11, 2016 at 01:11:46PM +0530, Nava kishore Manne wrote:
> > > This patch updates the driver to support 64-bit DMA
> > > addressing.
> > >
> > > Signed-off-by: Nava
On Mon, Apr 18, 2016 at 10:03:52AM -0400, David Woodhouse wrote:
> On Mon, 2016-04-18 at 16:12 +0300, Michael S. Tsirkin wrote:
> > I'm not sure I understand the issue. The public API is not about how
> > the driver works. It doesn't say "don't use DMA API" anywhere, does it?
> > It's about telli
Add possibility for userspace 32-bit applications to move
vdso mapping. Previously, when userspace app called
mremap for vdso, in return path it would land on previous
address of vdso page, resulting in segmentation violation.
Now it lands fine and returns to userspace with remapped vdso.
This will
The proximity sensor relies on sending pulses to an external IR led and
it is disabled by default on powerup. The driver will enable it with a
default power setting.
Signed-off-by: Crestez Dan Leonard
---
drivers/iio/light/max44000.c | 45 ++--
1 file chan
This just adds support for reporting illuminance with default settings.
Important default registers are written on probe because the device
otherwise lacks a reset function.
Signed-off-by: Crestez Dan Leonard
---
drivers/iio/light/Kconfig| 11 ++
drivers/iio/light/Makefile | 1 +
drive
Signed-off-by: Crestez Dan Leonard
---
drivers/iio/light/max44000.c | 62
1 file changed, 62 insertions(+)
diff --git a/drivers/iio/light/max44000.c b/drivers/iio/light/max44000.c
index c58bb78..b83d47d 100644
--- a/drivers/iio/light/max44000.c
+++ b/
Sure, this is not the complete patch. As far as I know the problem
you're facing with arm is that virt_to_page() does not provide the
correct page descriptor so my suggestion will eliminate the need for
it.
On Mon, Apr 18, 2016 at 09:53:30AM -0400, Sinan Kaya wrote:
> On 4/18/2016 2:54 AM, Eli Coh
This is exposed as an output channel with "led" as an extend_name.
Other sensors also have support for controlling an external LED. It's
not clear that simply exposing an undecorated output channel is the
correct approach.
Signed-off-by: Crestez Dan Leonard
---
drivers/iio/light/max44000.c | 53
On Mon, Apr 18, 2016 at 09:54:47AM +0300, Eli Cohen wrote:
> Sinan,
>
> if we get rid of the part this code:
>
> if (BITS_PER_LONG == 64) {
> struct page **pages;
> pages = kmalloc(sizeof *pages * buf->nbufs, gfp);
>
Changes since v2:
* Drop reg_defaults from regmap_config
* Use REGCACHE_RBTREE
* Implement readable/writable/volatile reg with switches
* Use test_bit when checking the scan mask
* Add _INT_TIME info_mask in patch 4 rather than 2
* Cleaner spacing in max44000_remove
Changes since v1:
* Remove max4
This patch exposes ALSTIM as illuminance_integration_time and ALSPGA as
illuminance_scale.
Changing ALSTIM also changes the number of bits available in the data
register. This is handled inside raw value reading because:
* It's very easy to shift a few bits
* It allows SCALE and INT_TIME to be com
On Mon, Apr 18, 2016 at 11:35 AM, Paul Burton wrote:
> There are 2 distinct cases in which a kernel for a MIPS32 CPU
> (CONFIG_CPU_MIPS32=y) may use 64 bit physical addresses
> (CONFIG_PHYS_ADDR_T_64BIT=y):
>
> - 36 bit physical addressing as used by RMI Alchemy & Netlogic XLP/XLR
> CPUs.
>
On 3/22/2016 5:11 PM, Alexandre Torgue wrote:
Hi guys,
I will fix typo issues (s/vesrion/version and ethernet @).
Concerning compatible string. For sure "snps,dwmac-3.50a" string is
not used inside glue driver.
I perfere to keep it for information but if you really want that I
remove it I will
Boris,
On 30/03/16 19:14, Boris Brezillon wrote:
> Implementing the mtd_ooblayout_ops interface is the new way of exposing
> ECC/OOB layout to MTD users.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/mtd/nand/omap2.c | 194
> +++
> 1 file change
On 2016/4/18 22:29, Jiri Olsa wrote:
On Mon, Apr 18, 2016 at 10:20:23PM +0800, Wangnan (F) wrote:
On 2016/4/18 21:45, Jiri Olsa wrote:
On Mon, Apr 18, 2016 at 06:32:08AM +, Wang Nan wrote:
Use 'trigger' to model operations which need to be executed when
an event (a signal, for example)
On Monday 18 April 2016 09:29:09 Rob Herring wrote:
>
> Right, you don't need to know the exact bus width for determining the
> register/descriptor set is 32 or 64 bit addesses. I'm fine with a
> property for that, but if limiting the actual connected address bits is
> needed, then dma-ranges s
On Mon, Apr 18, 2016 at 01:50:15PM +0200, Joerg Roedel wrote:
> Hi Bjorn,
>
> On Fri, Apr 15, 2016 at 10:08:21AM -0500, Bjorn Helgaas wrote:
> > I assume you're thinking about doing pci_enable_resources() before
> > the core calls the driver's probe method? One question there is how
> > we would
On Monday 18 April 2016 15:03:51 Tomasz Nowicki wrote:
> On 16.04.2016 16:36, Jayachandran C wrote:
> > On Sat, Apr 16, 2016 at 1:01 PM, Arnd Bergmann wrote:
> >> On Saturday 16 April 2016 12:50:13 Jayachandran C wrote:
> > The whole pci-thunder-*.c is to support thunder PCI quirks since the
> > g
Hi all,
I've hit the following while fuzzing with syzkaller inside a KVM tools guest
running the latest -next kernel:
[ 326.963405] general protection fault: [#1] PREEMPT SMP KASAN
[ 326.963416] Modules linked in:
[ 326.963430] CPU: 0 PID: 10488 Comm: syz-executor Not tainted
4.6.0-rc3-n
On Fri, Apr 15, 2016 at 03:03:12PM -0700, Thomas Garnier wrote:
> +#if defined(CONFIG_KASAN)
> +static const unsigned long memory_rand_end = KASAN_SHADOW_START;
> +#elfif defined(CONFIG_X86_ESPFIX64)
> +static const unsigned long memory_rand_end = ESPFIX_BASE_ADDR;
> +#elfif defined(CONFIG_EFI)
> +
On 2016-04-08 11:15, Thierry Reding wrote:
> From: Thierry Reding
>
> Avoid forking off a shell to resolve the absolute path of the output
> directory when make's builtin $(abspath ...) function will do an
> adequate job.
The abspath function is not available in make 3.80.
Michal
On 18/04/16 17:10, Boris Brezillon wrote:
> On Mon, 18 Apr 2016 16:48:26 +0300
> Roger Quadros wrote:
>
>> Boris,
>>
>> On 18/04/16 16:13, Boris Brezillon wrote:
>>> Hi Roger,
>>>
>>> On Mon, 18 Apr 2016 15:52:58 +0300
>>> Roger Quadros wrote:
>>>
On 18/04/16 15:31, Roger Quadros wrote:
>>>
On Monday 18 April 2016 15:33:24 Tomasz Nowicki wrote:
>
> Of course we can split discussion into the two topics:
> 1. ECAM based ACPI host controller - patches [1-10]
> 2. Quirks handling and examples.
>
> IMO, it is very helpful for reviewers to go with one unified patch set
> and see the whol
On Fri 2016-04-15 10:38:15, Tejun Heo wrote:
> > Anyway, before we go that way, can we at least consider the possibility
> > of removing the kworker creation dependency on the global rwsem? AFAIU
> > this locking was added because of the pid controller. Do we even care
> > about something as volati
Parameters delay_on and delay_off of led_trigger_blink_oneshot()
are pointers, to enable blink interval adjustment by LED class drivers
of the controllers that implement hardware blinking.
Move ide_blink_delay variable to ledtrig_ide_activity() in order to
prevent the situation when adjustment com
On Monday 18 April 2016 18:00:19 Kishon Vijay Abraham I wrote:
> Hi Arnd,
>
> On Sunday 17 April 2016 01:20 AM, Arnd Bergmann wrote:
> > On Thursday 14 April 2016 11:22:58 Kishon Vijay Abraham I wrote:
> >>
> >> IMO simple-phy driver should be an independent driver and shouldn't export
> >> symbol
Hi, Namhyung
On 04/15/2016 01:42 AM, Taeung Song wrote:
Hi, Arnaldo
On 04/14/2016 09:19 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Apr 14, 2016 at 04:53:20PM +0900, Taeung Song escreveu:
To precisely manage configs,
prepare all default perf's configs that contain
default section name, variab
Right, I did not suggest this as a patch but just wanted to pinpoint the
problematic issue which is that virt_to_page does not give you the correct
pointer to the page.
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Monday, April 18, 2016 9:33 AM
To: Eli Co
v4 -> v5: 'PROCESSING' state has only one user. Remove it to
reduce confusion.
Cc: Wang Nan
Cc: Adrian Hunter
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: pi3or...@163.com
Wang Nan (6):
perf tools: Derive trigger class from auxtrace_snapshot
Use 'trigger' to model operations which need to be executed when
an event (a signal, for example) is observed.
States and transits:
OFF--(on)--> READY --(toggle)--> TOGGLED
^|
| (ready)
||
On Mon, 18 Apr 2016 16:40:46 +0200
Jacek Anaszewski wrote:
> Parameters delay_on and delay_off of led_trigger_blink_oneshot()
> are pointers, to enable blink interval adjustment by LED class drivers
> of the controllers that implement hardware blinking.
>
> Move ide_blink_delay variable to ledtr
Tracking events describe kernel and threads. They are generated by
reading /proc/kallsyms, /proc/*/maps and /proc/*/task/* during
initialization of 'perf record', serialized into event sequences and put
at the head of 'perf.data'. In case of output switching, each output
file should contain those e
On Monday 18 April 2016 05:55:51 Reizer, Eyal wrote:
> > >
> > > - all wilink family needs special init command for entering wspi mode.
> > > extra clock cycles should be sent after the spi init command while the
> > > cs pin is high.
> > > - switch to controling the cs pin from the spi driver
The cost of buildid cache processing is high: reading all events in
output perf.data, opening each elf file to read buildids then copying
them into ~/.debug directory. In switch output mode, these heavy works
block perf from receiving perf events for too long.
Enable no-buildid and no-buildid-cach
With 'perf record --switch-output' without -a, record__synthesize() in
record__switch_output() won't generate tracking events because there's
no thread_map in evlist. Which causes newly created perf.data doesn't
contain map and comm information.
This patch creates a fake thread_map and directly ca
Yes, it is. Certainly happened while editing patches (sorry about
that), will be fixed on next iteration once I get a bit more feedback.
On Mon, Apr 18, 2016 at 7:46 AM, Joerg Roedel wrote:
> On Fri, Apr 15, 2016 at 03:03:12PM -0700, Thomas Garnier wrote:
>> +#if defined(CONFIG_KASAN)
>> +static
Without this patch, the last output doesn't have timestamp appended if
--timestamp-filename is not explicitly provided. For example:
# perf record -a --switch-output &
[1] 11224
# kill -s SIGUSR2 11224
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.201512262
On Mon, 18 Apr 2016 17:39:01 +0300
Roger Quadros wrote:
> On 18/04/16 17:10, Boris Brezillon wrote:
> > On Mon, 18 Apr 2016 16:48:26 +0300
> > Roger Quadros wrote:
> >
> >> Boris,
> >>
> >> On 18/04/16 16:13, Boris Brezillon wrote:
> >>> Hi Roger,
> >>>
> >>> On Mon, 18 Apr 2016 15:52:58 +0300
Allow 'perf record' to split its output into multiple files.
For example:
# ~/perf record -a --timestamp-filename --switch-output &
[1] 10763
# kill -s SIGUSR2 10763
[ perf record: dump data: Woken up 1 times ]
# [ perf record: Dump perf.data.2015122622314468 ]
# kill -s SIGUSR2 1076
On Sat, 2016-04-16 at 20:20 +0100, Jonathan Cameron wrote:
> On 10/04/16 20:05, Alison Schofield wrote:
> >
> > Driver includes struct regmap and struct device in its global data.
> > Remove the struct device and use regmap API to retrieve device
> > info.
> >
> > Patch created using Coccinelle p
On Sat, 2016-04-16 at 20:24 +0100, Jonathan Cameron wrote:
> On 10/04/16 20:08, Alison Schofield wrote:
> >
> > Driver includes struct regmap and struct device in its global data.
> > Remove the struct device and use regmap API to retrieve device
> > info.
> >
> > Patch created using Coccinelle p
On Mon, 18 Apr 2016 17:32:49 +0300
Roger Quadros wrote:
> Boris,
>
> On 30/03/16 19:14, Boris Brezillon wrote:
> > Implementing the mtd_ooblayout_ops interface is the new way of exposing
> > ECC/OOB layout to MTD users.
> >
> > Signed-off-by: Boris Brezillon
> > ---
> > drivers/mtd/nand/omap2
Hi Sudeep,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c3b46c73264b03000d1e18b22f5caf63332547c9
commit: 8810df37762746657cfe84014a8f30758e8f366a misc: mic: Enable VOP debugfs
and driver build
date: 10 weeks ag
On Mon, Apr 18, 2016 at 04:46:53PM +0200, Michal Marek wrote:
> On 2016-04-08 11:15, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > Avoid forking off a shell to resolve the absolute path of the output
> > directory when make's builtin $(abspath ...) function will do an
> > adequate job.
>
On 03/01/2016 01:45 AM, Hugh Dickins wrote:
> Commit e1534ae95004 ("mm: differentiate page_mapped() from page_mapcount()
> for compound pages") changed the famous BUG_ON(page_mapped(page)) in
> __delete_from_page_cache() to VM_BUG_ON_PAGE(page_mapped(page)): which
> gives us more info when CONFIG_D
Update a tasks's universe when returning from a system call or user
space interrupt, or after handling a signal.
This greatly increases the chances of a patch operation succeeding. If
a task is I/O bound, it can switch universes when returning from a
system call. If a task is CPU bound, it can s
So this is something we have in kGraft for a while (though the actual
implementation in s390's entry.S differs).
The first patch is needed because we want our TIF flag to be part of
_TIF_WORK and s390's tm instruction tests only 8-bits.
The second patch adds a call to klp_update_task_universe() t
From: Jiri Slaby
Signed-off-by: Jiri Slaby
---
arch/s390/include/asm/thread_info.h | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/arch/s390/include/asm/thread_info.h
b/arch/s390/include/asm/thread_info.h
index 2fffc2c27581..8642c1dab382 100644
--- a
This unexports some symbols from head.S that are only used locally.
Signed-off-by: Ard Biesheuvel
---
arch/arm64/kernel/head.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
index b43417618847..ac27d8d937b2 100644
---
Refactor the relocation processing so that the code executes from the
ID map while accessing the relocation tables via the virtual mapping.
This way, we can use literals containing virtual addresses as before,
instead of having to use convoluted absolute expressions.
For symmetry with the secondar
This is a follow up to my series 'arm64: more granular KASLR' [1] that I sent
out about six weeks ago. It also partially supersedes [2].
The first patch is an unrelated cleanup that is completely orthogonal (but
happens to touch head.S as well) and is arbitrarily listed first.
Patches #2 to #5 ad
When booting a relocatable kernel image, there is no practical reason
to refuse an image whose load address is not exactly TEXT_OFFSET bytes
above a 2 MB aligned base address, as long as the physical and virtual
misalignment with respect to the swapper block size are equal, and are
both aligned to
Add __init attribute on a function that is only called from other __init
functions and that is not inlined, at least with gcc version 4.8.4 on an
x86 machine with allyesconfig. Currently, the function is put in the
.text.unlikely segment. Declaring it as __init will cause it to be put in
the .ini
Currently, our KASLR implementation randomizes the placement of the core
kernel at 2 MB granularity. This is based on the arm64 kernel boot
protocol, which mandates that the kernel is loaded TEXT_OFFSET bytes above
a 2 MB aligned base address. This requirement is a result of the fact that
the block
401 - 500 of 919 matches
Mail list logo
