This is to prevent missing symbol build error if OTG is
enabled (built-in) and HCD core (CONFIG_USB) is module.
Signed-off-by: Roger Quadros
Acked-by: Peter Chen
---
drivers/usb/common/usb-otg-fsm.c | 6 --
drivers/usb/phy/phy-fsl-usb.c| 2 ++
include/linux/usb/otg-fsm.h | 1 +
3
If usb/otg-fsm.h and usb/composite.h are included together
then it results in the build warning [1].
Prevent that by using dev_vdbg() instead.
Also get rid of MPC_LOC which doesn't seem to be used
by anyone.
[1] - warning fixed by this patch:
In file included from
Hi,
This series centralizes OTG/Dual-role functionality in the kernel.
As of now I've got Dual-role functionality working pretty reliably on
dra7-evm and am437x-gp-evm.
DWC3 controller and platform related patches will be sent separately.
Series is based on Greg's usb-next tree.
Changelog:
struct otg_fsm is the interface to the OTG state machine.
Document the input, output and internal state variables.
Definations are taken from Table 7-2 and Table 7-4 of
the USB OTG & EH Specification Rev.2.0
Re-arrange some of the members as per use case for more
clarity.
Signed-off-by: Roger
+benh
On Mon, Aug 24, 2015 at 7:30 AM, Zhen Lei wrote:
> If use of_platform_populate to scan dt-nodes and add devices, the
> subnode of root(such as /smmu), when being scanned and invoke
You should have a bus as the sub-node of root rather than devices
directly off of root. You still have a
On Mon, Aug 24, 2015 at 01:39:11PM +0100, Qais Yousef wrote:
> Signed-off-by: Qais Yousef
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc: Ian Campbell
> Cc: Kumar Gala
> Cc: devicet...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
>
On Mon, Aug 24, 2015 at 6:15 PM, Marc Zyngier wrote:
> On 24/08/15 13:30, Ganapatrao Kulkarni wrote:
>> Hi Marc,
>>
>> thanks for the review comments.
>>
>> On Mon, Aug 24, 2015 at 3:47 PM, Marc Zyngier wrote:
>>> Hi Robert,
>>>
>>> Just came back from the Seattle madness, so picking up patches
On Fri, Aug 21, 2015 at 02:13:51PM +0800, Peng Sun wrote:
>
> patches based on commit f0359ead9129821e4b3b5486e7837d3001a95574
> linux-next next-20150820
you have almost similar subject for all patches in the series and please
mention which coding style you have changed.
regards
sudip
--
To
After analysis done by Yingjoe Chen, the timer appears to have a pending
interrupt when it is enabled.
Fix this by acknowledging the pending interrupt when enabling the timer
interrupt.
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/mtk_timer.c | 13 +++--
1 file changed, 3
On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
I am in the middle of implementing lock on fault this way, but I cannot
see how we will hanlde mremap of a lock on fault region. Say we have
the following:
addr = mmap(len, MAP_ANONYMOUS, ...);
mlock(addr, len, MLOCK_ONFAULT);
Eugene Shatokhin writes:
> 19.08.2015 15:31, Bjørn Mork пишет:
>> Eugene Shatokhin writes:
>>
>>> The problem is not in the reordering but rather in the fact that
>>> "dev->flags = 0" is not necessarily atomic
>>> w.r.t. "clear_bit(EVENT_RX_KILL, >flags)", and vice versa.
>>>
>>> So the
On 24/08/15 14:02, Qais Yousef wrote:
> On 08/24/2015 01:49 PM, Thomas Gleixner wrote:
>> On Mon, 24 Aug 2015, Qais Yousef wrote:
>>
>>> Some drivers might require to send ipi to other cores. So export it.
>> Which IPIs do you need to send from a driver which are not exposed by
>> the SMP
On 08/19/2015 04:12 PM, california.l.sulli...@intel.com wrote:
> From: California Sullivan
>
> The debug UART on the Bay Trail is buggy and will sometimes enter a
> state where there is a Character Timeout interrupt, but the Data
> Ready bit in the Line Status Register is not set, despite there
On 8/24/15 19:32, Michal Hocko wrote:
> On Mon 24-08-15 00:59:39, gang.chen.5...@qq.com wrote:
>>> From: Chen Gang
>>>
>>> When failure occurs and return, vma->vm_pgoff is already set, which is
>>> not a good idea.
> Why? The vma is not inserted anywhere and the failure path is supposed
> to
On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
> 2)
>
> What happens if the boot CPU is offlined? (under
> CONFIG_BOOTPARAM_HOTPLUG_CPU0=y)
>
> I don't see CPU hotplug callbacks fixing up the housekeeping_mask if the boot
> CPU
> is offlined.
We have
Hi Santosh,
All the patches except this one are in linux-next.
On 07/22/2015 11:17 AM, santosh shilimkar wrote:
> On 7/22/2015 5:32 AM, Franklin S Cooper Jr wrote:
>> Add ti,keystone-spi to the compatible field for the SPI node. This new
>> entry insures that the proper prescaler limit is used
On Mon, Aug 24, 2015 at 5:17 AM, Mark Rutland wrote:
> On Wed, Aug 05, 2015 at 05:51:20PM +0100, Mark Rutland wrote:
>> Rob,
>>
>> Do you have any objections to this, or are you happy to take this patch?
>>
>> There's a user of this binding (the GICv3 ITS) queued for v4.3 already in
>> the tip
Hi,
On Mon, Aug 24, 2015 at 04:31:13PM +0800, yalin wang wrote:
>
> i only submit the bit reverse patch for arm / arm64 arch,
yes, saw later git blaming it on you :)
> > Not for this case, but once measured on ARM, iirc, a 32-bit asm bit
> > reversal as compared to doing it in C was taking 1
On Mon, Aug 24, 2015 at 3:15 PM, Russell King - ARM Linux
wrote:
> On Tue, Jul 21, 2015 at 11:27:56PM +0200, Linus Walleij wrote:
>> On Tue, Jul 21, 2015 at 4:27 PM, Andrey Ryabinin
>> wrote:
>>
>> > I used vexpress. Anyway, it doesn't matter now, since I have an update
>> > with a lot of stuff
> "Ingo" == Ingo Molnar writes:
Ingo> * George Spelvin wrote:
>> First, an actual, albeit minor, bug: initializing both vmap_info_gen
>> and vmap_info_cache_gen to 0 marks the cache as valid, which it's not.
Ingo> Ha! :-) Fixed.
>> vmap_info_gen should be initialized to 1 to force an
On 23 August 2015 at 16:09, Robert Jarzmik wrote:
> Robert Jarzmik writes:
>
>> Ezequiel Garcia writes:
>>
>>> On 11 Aug 09:57 PM, Robert Jarzmik wrote:
Add verbose debug for register accesses. This enables easier debugging
by following where and how hardware is stimulated, and how it
On 24/08/15 14:27, Ganapatrao Kulkarni wrote:
> On Mon, Aug 24, 2015 at 6:15 PM, Marc Zyngier wrote:
> static void its_enable_cavium_thunderx(void *data)
> {
> - struct its_node *its = data;
> + struct its_node __maybe_unused *its = data;
>
> - its->flags |=
On Mon, Aug 17, 2015 at 1:30 PM, Eric Anholt wrote:
> Stephen Warren writes:
>
>> On 08/12/2015 06:56 PM, Eric Anholt wrote:
>>> Signed-off-by: Eric Anholt
>>
>> This one definitely needs a patch description, since someone might not
>> know what a VC4 is, and "git log" won't show the text from
On Mon, Aug 24, 2015 at 02:37:59PM +0100, Rob Herring wrote:
> On Mon, Aug 24, 2015 at 5:17 AM, Mark Rutland wrote:
> > On Wed, Aug 05, 2015 at 05:51:20PM +0100, Mark Rutland wrote:
> >> Rob,
> >>
> >> Do you have any objections to this, or are you happy to take this patch?
> >>
> >> There's a
On 08/24/2015 02:26 PM, Mark Rutland wrote:
On Mon, Aug 24, 2015 at 01:39:11PM +0100, Qais Yousef wrote:
Signed-off-by: Qais Yousef
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
On Fri, Aug 21, 2015 at 02:16:12PM -0400, cp...@redhat.com wrote:
> From: Stephen Chandler Paul
>
> Most of the time this isn't an issue since hotplugging an adaptor will
> trigger a crtc mode change which in turn, causes the driver to probe
> every DisplayPort for a dpcd. However, in cases
On 08/06/2015 05:19 AM, Punnaiah Choudary Kalluri wrote:
[...]
> +Optional properties:
> +- xlnx,include-sg: Indicates the controller to operate in simple or scatter
> +gather dma mode
> +- xlnx,ratectrl: Scheduling interval in terms of clock cycles for
> + source AXI
checkpatch complains when a variable comparison to NULL is written as:
variable == NULL or variable != NULL.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/most/aim-cdev/cdev.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
Ingo Molnar writes:
> * Peter Zijlstra wrote:
>
>> On Fri, Jul 24, 2015 at 02:45:55PM +0300, Alexander Shishkin wrote:
>> > Hi Peter and Ingo and everybody,
>> >
>> > Here's my second stab at improving perf's error reporting by attaching
>> > arbitrary strings to the integer error codes. This
On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
> On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>>>
>>>
>>> I am in the middle of implementing lock on fault this way, but I cannot
>>> see how we will hanlde mremap of a lock on fault region. Say we have
>>> the following:
>>>
>>>
On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > > here it's fully set - triggering the bug I'm worried about. So what am I
> > > missing, what prevents CONFIG_NO_HZ_FULL_ALL from crashing?
> >
> > The boot CPU is excluded from
Hi,
This time the pull-request comes a bit early, since I'm on vacation from
tomorrow until 2015-09-10 without any internet connection. In addition
to the git.infradead.org based repository used so far, I also pushed the
tag to git.kernel.org.
-- Sebastian
The following changes since commit
On Wed, 08 Jul 2015, Vaibhav Hiremath wrote:
> During probe, inside fn device_800_init(), submodule init is
> happening and the same error message is getting printed in both
> the places, _init() and inside device_800_init().
>
> So this patch gets rid of dev_err from _init() fns.
>
>
On Wed, 08 Jul 2015, Vaibhav Hiremath wrote:
> Currently the device_xxx_init() fns take pdata as an input parameter to
> the fn, but the cleaner approach would be to use dev_get_platdata() to
> get the pdata.
> So this patch changes the code accordingly.
>
> Signed-off-by: Vaibhav Hiremath
>
On Wed, 08 Jul 2015, Vaibhav Hiremath wrote:
> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
> (page 0) controls the method of clearing interrupt
> status of 88pm800 family of devices;
>
> 0: clear on read
> 1: clear on write
>
> If pdata is not coming from board file, then set
On Sat, 22 Aug 2015, Qipeng Zha wrote:
> IRQ control registers of Intel Broxton Whisky Cove PMIC are
> separated in two parts, so add secondary IRQ chip.
> And the new member of device will be used in PMC IPC regmap APIs.
>
> Signed-off-by: Qipeng Zha
> ---
> include/linux/mfd/intel_soc_pmic.h
This patch fix following warnings.
.//net/core/skbuff.c:407: warning: No description found
for parameter 'len'
.//net/core/skbuff.c:407: warning: Excess function parameter
'length' description in '__netdev_alloc_skb'
.//net/core/skbuff.c:476: warning: No description found
for parameter 'len'
On Wed, Aug 12, 2015 at 7:56 PM, Eric Anholt wrote:
> Signed-off-by: Eric Anholt
> ---
> .../devicetree/bindings/gpu/brcm,bcm-vc4.txt | 83
> ++
> 1 file changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpu/brcm,bcm-vc4.txt
>
> diff
On Mon 24-08-15 21:34:25, Chen Gang wrote:
> On 8/24/15 19:32, Michal Hocko wrote:
> > On Mon 24-08-15 00:59:39, gang.chen.5...@qq.com wrote:
> >>> From: Chen Gang
> >>>
> >>> When failure occurs and return, vma->vm_pgoff is already set, which is
> >>> not a good idea.
> > Why? The vma is not
On Sat, 22 Aug 2015, Qipeng Zha wrote:
> Add MFD core driver for Intel Broxton Whiskey Cove PMIC,
> which is specially accessed by hardware IPC, not a generic
> I2C device
>
> Signed-off-by: Qipeng Zha
> ---
> change in v5
> Fix issues in code style, espcially make error messages readable;
>
On Thu, 20 Aug 2015, Javier Martinez Canillas wrote:
> The Documentation/devicetree/bindings/mfd/stmpe.txt DT binding doc lists
> "st,stmpe[610|801|811|1601|2401|2403]" as valid compatible strings but
> the corresponding driver does not have an OF match table. Add the table
> to the driver so the
On Thu, 20 Aug 2015, Javier Martinez Canillas wrote:
> The Documentation/devicetree/bindings/mfd/cros-ec.txt DT binding doc lists
> "google,cros-ec-spi" as a compatible string but the corresponding driver
> does not have an OF match table. Add the table to the driver so the SPI
> core can do an
On Mon, 2015-08-24 at 15:36 +0200, Frederic Weisbecker wrote:
> On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
> > 2)
> >
> > What happens if the boot CPU is offlined? (under
> > CONFIG_BOOTPARAM_HOTPLUG_CPU0=y)
> >
> > I don't see CPU hotplug callbacks fixing up the
On Thu, 20 Aug 2015, Matt Redfearn wrote:
> The mask cache must be initialised in the generic IRQ chip,
> otherwise enabling one channel will actually enable all
> channels when the empty mask cache is written.
>
> Signed-off-by: Matt Redfearn
> ---
> drivers/mfd/jz4740-adc.c | 3 ++-
> 1 file
On 2015/8/24 18:01, Heiko Stuebner wrote:
Hi Shawn,
Am Montag, 24. August 2015, 16:27:43 schrieb Shawn Lin:
mmc host controller's IO input/output timing is unpredictable if
bootloader execute tuning for HS200 mode. It might make kernel failed
to initialize mmc card in identification mode. The
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes based on the information. The most features are available
from hypervisor
On Mon, Aug 24, 2015 at 06:50:18AM -0700, Paul E. McKenney wrote:
> On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney wrote:
> >
> > > > here it's fully set - triggering the bug I'm worried about. So what am
> > > > I
> > > > missing, what prevents
> -Original Message-
> From: Jerome Glisse [mailto:j.gli...@gmail.com]
> Sent: Monday, August 24, 2015 9:48 AM
> To: cp...@redhat.com
> Cc: Deucher, Alexander; Koenig, Christian; David Airlie; dri-
> de...@lists.freedesktop.org; linux-kernel@vger.kernel.org; Jerome Glisse;
> Benjamin
On Mon, 24 Aug 2015 11:29:29 +0800
Jason Wang wrote:
> On 08/21/2015 05:29 PM, Cornelia Huck wrote:
> > On Fri, 21 Aug 2015 16:03:52 +0800
> > Jason Wang wrote:
> >> @@ -850,9 +845,15 @@ kvm_assign_ioeventfd(struct kvm *kvm, struct
> >> kvm_ioeventfd *args)
> > Unfortunately snipped by diff,
On 08/21/2015 04:00 AM, Changsheng Liu wrote:
On 08/20/201515:41, Vlastimil Babka wrote:
On 08/20/2015 09:28 AM, Changsheng Liu wrote:
From: Changsheng Liu
When memory is hot added, should_add_memory_movable() always returns 0
because the movable zone is empty, so the memory that was hot
Fix autoloading ipmi modules when using device tree.
Signed-off-by: Brijesh Singh
---
drivers/char/ipmi/ipmi_si_intf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
index 8a45e92..cddc7b0 100644
---
2015-08-24 16:45 GMT+03:00 Linus Walleij :
> On Mon, Aug 24, 2015 at 3:15 PM, Russell King - ARM Linux
> wrote:
>> On Tue, Jul 21, 2015 at 11:27:56PM +0200, Linus Walleij wrote:
>>> On Tue, Jul 21, 2015 at 4:27 PM, Andrey Ryabinin
>>> wrote:
>>>
>>> > I used vexpress. Anyway, it doesn't matter
On 08/19/2015 06:01 PM, Stefan Fausser wrote:
> Dear all,
>
> attached are two patches for the "isci" module (CONFIG_SCSI_ISCI).
>
> Both patches apply to the current Linux kernel, retrieved by GIT (4.2.0-rc7).
>
> The first patch (init.patch) is for reproducing the problem with the
>
On 08/24/2015 08:50 AM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>>
>> * Denys Vlasenko wrote:
>>
>>> I propose the table to be commented like shown below:
>>>
>>> /*Opcode: d8 d9da db dc dd de df */
>>> /*c0..f*/ fadd__, fld_i_, fcmovb, fcmovnb,
On Fri, Aug 21, 2015 at 05:27:43PM -0300, Leonidas S Barbosa wrote:
>
> In build time vadduqm opcode is not being mapped
> correctly.
>
> Adding a new map in ppc-xlate to do this.
>
> Signed-off-by: Leonidas S Barbosa
Applied.
--
Email: Herbert Xu
Home Page:
Hi Stephen,
On Sun, Aug 23, 2015 at 7:16 PM, Stephen Rothwell wrote:
> Hi Trond,
>
> On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
> wrote:
>>
>> After merging the nfs tree, today's linux-next build (x86_64 allmodconfig)
>> failed like this:
>>
>>
On Mon, Aug 24, 2015 at 02:22:49PM +0100, Jon Hunter wrote:
>
> On 24/08/15 10:22, Vinod Koul wrote:
> > On Mon, Aug 24, 2015 at 09:47:13AM +0100, Jon Hunter wrote:
> >>
> >> On 23/08/15 15:17, Vinod Koul wrote:
> >>> On Tue, Aug 18, 2015 at 02:49:09PM +0100, Jon Hunter wrote:
> >>>
> @@
From: Vineet Gupta
With all features in place, the ARC HS pct block can now be effectively
allowed to be probed/used
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Vineet Gupta
Signed-off-by: Alexey Brodkin
---
No changes since v2.
Compared to v1:
[1] MAINTAINERS file
From: Vineet Gupta
The number of counters in PCT can never be more than 32 (while
countable conditions could be 100+) for both ARCompact and ARCv2
And while at it update copyright dates.
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Vineet Gupta
Signed-off-by: Alexey
* split off pmu info into singleton and per-cpu bits
* setup PMU on all cores
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Alexey Brodkin
---
No changes since v2.
Compared to v1:
[1] Rebase on top of previos patches hence changes in patch itself
[2] Cosmetics
Cc: Peter Zijlstra
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Alexey Brodkin
---
No changes since v2.
No changes since v1.
arch/arc/include/asm/perf_event.h | 3 +++
arch/arc/kernel/perf_event.c | 16 ++--
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git
>
> On Fri, Aug 21, 2015 at 08:25:24PM +, Liang, Kan wrote:
>
> SNIP
>
> > >
> > > we need global topology information in perf.data and use the mapping
> > > from there, we can't use current server info
> > >
> > > we currently store core_siblings_list and thread_siblings_list, in
> > >
In times of ARC 700 performance counters didn't have support of
interrupt an so for ARC we only had support of non-sampling events.
Put simply only "perf stat" was functional.
Now with ARC HS we have support of interrupts in performance counters
which this change introduces support of.
ARC
Hi Peter,
This mini-series adds perf support for ARCv2 based cores, which brings in
overflow interupts and SMP. Additionally now raw events are supported as well.
Please review !
Compared to v2 this series has:
[1] Removed patch with raw-events support.
It needs some rework and let's then
This generalization prepares for support of overflow interrupts.
Hardware event counters on ARC work that way:
Each counter counts from programmed start value (set in
ARC_REG_PCT_COUNT) to a limit value (set in ARC_REG_PCT_INT_CNT) and
once limit value is reached this timer generates an
On Mon, 2015-08-24 at 09:51 +0200, Daniel Lezcano wrote:
> On 08/21/2015 04:39 PM, Yingjoe Chen wrote:
>
> [ ... ]
>
> >>- Does the spurious interrupt occurs *every* time ? at each boot ?
> >
> > Yes. If you applied this series to enable mtk timer without this fix on
> > mt8173 or mt8135 you
On Mon, Aug 24, 2015 at 11:21:15AM +0200, Maxime Ripard wrote:
> Just like for the XDMAC, the SoCs that embed the HDMAC don't have any kind
> of GPU, and need to accelerate a few framebuffer-related operations through
> their DMA controller.
>
> However, unlike the XDMAC, the HDMAC doesn't have
This patch configure correctly the MMC-0 clock for STiH418 platform.
Signed-off-by: Gabriel Fernandez
Acked-by: Maxime Coquelin
---
arch/arm/boot/dts/stih418.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/stih418.dtsi b/arch/arm/boot/dts/stih418.dtsi
index
On 08/24/2015 02:32 PM, Marc Zyngier wrote:
On 24/08/15 14:02, Qais Yousef wrote:
On 08/24/2015 01:49 PM, Thomas Gleixner wrote:
On Mon, 24 Aug 2015, Qais Yousef wrote:
Some drivers might require to send ipi to other cores. So export it.
Which IPIs do you need to send from a driver which
On Mon, Aug 24, 2015 at 02:22:08PM +, Liang, Kan wrote:
> >
> > On Fri, Aug 21, 2015 at 08:25:24PM +, Liang, Kan wrote:
> >
> > SNIP
> >
> > > >
> > > > we need global topology information in perf.data and use the mapping
> > > > from there, we can't use current server info
> > > >
> >
The HOWTO document needed updating for the new kernel versioning.
Signed-off-by: Mario Carrillo
---
Documentation/HOWTO | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 93aa860..21152d3 100644
---
Hi Peter and Ingo and everybody,
Here's an update of my extended error reporting patchset, addressing
review comments and adding a few more error messages to PT and BTS
drivers.
Changes since v1:
* addressed Peter's comments,
* added perf_err() annotation to intel_pt and intel_bts drivers;
If kernel debugging is enabled, include additional information to extended
syscall error reports: file name and line number, to make error hunting even
easier.
And in really desperate times, this allows for such things (a variation on
Hugh Dickins' trick [1]):
#undef EINVAL
On Monday 24 August 2015 07:50 PM, Alexey Brodkin wrote:
> Cc: Peter Zijlstra
> Cc: Arnaldo Carvalho de Melo
> Signed-off-by: Alexey Brodkin
> ---
>
> No changes since v2.
>
> No changes since v1.
>
>
> }
>
> + hwc->config = 0;
> +
> + if (is_isa_arcv2()) {
> +
It has been pointed several times out that perf syscall error reporting
leaves a lot to be desired [1].
This patch introduces a fairly simple extension that allows call sites
to annotate their error codes with arbitrary strings, which will then
be copied to userspace (if they asked for it) along
On Fri, 2015-08-21 at 16:39 -0300, Danilo Cesar Lemes de Paula wrote:
> Using pandoc as the Markdown engine cause some minor side effects as
> pandoc includes main tags for almost everything.
> Original Markdown support approach removes those main tags, but it
> caused
> some inconsistencies
On Mon, 2015-08-24 at 15:30 +0200, Daniel Lezcano wrote:
> After analysis done by Yingjoe Chen, the timer appears to have a pending
> interrupt when it is enabled.
>
> Fix this by acknowledging the pending interrupt when enabling the timer
> interrupt.
>
> Signed-off-by: Daniel Lezcano
Hi
This patch annotates a few semi-random error paths in perf core to
illustrate the extended error reporting facility. Most of them can
be triggered from perf tools.
Signed-off-by: Alexander Shishkin
---
kernel/events/core.c | 20 +++-
1 file changed, 11 insertions(+), 9
This patch annotates a few x86-specific error paths with perf's extended
error reporting facility.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/cpu/perf_event.c | 8 ++--
arch/x86/kernel/cpu/perf_event_intel_lbr.c | 2 +-
2 files changed, 7 insertions(+), 3 deletions(-)
On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
I am in the middle of implementing lock on fault this way, but I cannot
see how we will hanlde mremap of a lock on fault region.
If intel_bts events would conflict with other events that are active in
the system, provide an extended error message to the user along with the
usual EBUSY.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/cpu/perf_event_intel_bts.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Event attribute validation is one of the biggest sources of EINVALs around
perf_event_open() syscall. This patch annotates error checks with extended
error reporting macros to provide the user with more details on what they
are doing wrong.
Signed-off-by: Alexander Shishkin
---
On Mon, 24 Aug 2015, Ramneek Mehresh wrote:
> > On Thu, 20 Aug 2015, Ramneek Mehresh wrote:
> >
> > > > > --- a/drivers/usb/host/ehci-fsl.h
> > > > > +++ b/drivers/usb/host/ehci-fsl.h
> > > > > @@ -63,4 +63,22 @@
> > > > > #define UTMI_PHY_EN (1<<9)
> > > > > #define
On 08/24/15 04:52, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150821:
>
on x86_64:
drivers/built-in.o: In function `print_avi_infoframe':
tc358743.c:(.text.unlikely+0x7849): undefined reference to
`hdmi_infoframe_unpack'
tc358743.c:(.text.unlikely+0x787e): undefined reference to
On 2015-07-24 07:18, Masahiro Yamada wrote:
> Masahiro Yamada (2):
> kbuild: fixdep: optimize code slightly
> kbuild: fixdep: drop meaningless hash table initialization
>
> scripts/basic/fixdep.c | 26 --
> 1 file changed, 4 insertions(+), 22 deletions(-)
Applied to
The asm macros for setting up and restoring the frame pointer aren't
currently being used. However, they will be needed soon to help asm
functions to comply with stackvalidate.
Rename FRAME/ENDFRAME to FRAME_BEGIN/FRAME_END for more symmetry. Also
make the code more readable and improve the
swsusp_arch_suspend() and restore_registers() are callable non-leaf
functions which don't honor CONFIG_FRAME_POINTER, which can result in
bad stack traces. Also they aren't annotated as ELF callable functions
which can confuse tooling.
Create a stack frame for them when CONFIG_FRAME_POINTER is
Thunk functions are callable non-leaf functions that don't honor
CONFIG_FRAME_POINTER, which can result in bad stack traces. Also they
aren't annotated as ELF callable functions which can confuse tooling.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled and
add the ELF function
efi_call() is a callable non-leaf function which doesn't honor
CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Reviewed-by: Matt Fleming
---
arch/x86/platform/efi/efi_stub_64.S | 3 +++
If a PVOP call macro is inlined at the beginning of a function, gcc can
insert the call instruction before setting up a stack frame, which
breaks frame pointer convention if CONFIG_FRAME_POINTER is enabled and
can result in a bad stack trace.
Force a stack frame to be created if
do_suspend_lowlevel() is a callable non-leaf function which doesn't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Acked-by: Pavel Machek
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Hello!
On Aug 24, 2015, at 10:17 AM, Trond Myklebust wrote:
> Hi Stephen,
>
> On Sun, Aug 23, 2015 at 7:16 PM, Stephen Rothwell
> wrote:
>> Hi Trond,
>>
>> On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
>> wrote:
>>>
>>> After merging the nfs tree, today's linux-next build (x86_64
stackvalidate reports the following warning:
stackvalidate: arch/x86/crypto/aesni-intel_asm.o: _aesni_inc_init(): can't
find starting instruction
stackvalidate gets confused when it tries to disassemble the following
data in the .text section:
.Lbswap_mask:
.byte 15, 14, 13, 12,
clmul_ghash_mul() and clmul_ghash_update() are callable non-leaf
functions which don't honor CONFIG_FRAME_POINTER, which can result in
bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Cc: Herbert Xu
Cc: "David S. Miller"
---
This adds a CONFIG_STACK_VALIDATION option which enables a host tool
named stackvalidate which runs at compile time. It analyzes every .o
file and ensures the validity of its stack metadata. It enforces a set
of rules on asm code and C inline assembly code so that stack traces can
be reliable.
On Mon, Aug 24, 2015 at 7:57 AM, Russell King - ARM Linux
wrote:
> On Sun, Aug 23, 2015 at 06:23:14PM -0500, Rob Herring wrote:
>> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
>> > + -analogix,color-depth:
>> > + number of bits per colour component.
>> > +
A function created with the PV_CALLEE_SAVE_REGS_THUNK macro doesn't set
up a new stack frame before the call instruction, which breaks frame
pointer convention if CONFIG_FRAME_POINTER is enabled and can result in
a bad stack trace. Also, the thunk functions aren't annotated as ELF
callable
Hello, Jan.
On Mon, Aug 24, 2015 at 11:19:59AM +0200, Jan Kara wrote:
> > which shows unmount being the next writeback event queued and
> > executed after the IO completions have come in (that missed the
> > log). What is missing is the specific queue/exec events for
> > sync_sb_inodes() from the
aesni-intel_asm.S has several callable non-leaf functions which don't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Cc: Herbert Xu
Cc: "David S. Miller"
---
stackvalidate reports the following warning:
stackvalidate: arch/x86/crypto/crc32c-pcl-intel-asm_64.o: crc_pcl()+0x11dd:
can't decode instruction
It gets confused when trying to decode jump_table data. Move jump_table
to the .rodata section which is a more appropriate home for read-only
1301 - 1400 of 1850 matches
Mail list logo
