On Sun, 1 Dec 2013 17:23:14 -0700, David Ahern wrote:
> 'perf sched timehist' provides an analysis of scheduling events.
>
> Example usage:
> perf sched record -- sleep 1
> perf sched timehist
>
> By default it shows the individual schedule events, including the time between
> sched-in eve
Hello,
On Wed, Nov 27, 2013 at 01:44:44PM +0100, Boris BREZILLON wrote:
> The clock accuracy is expressed in ppb (parts per billion) and represents
> the possible clock drift.
> Say you have a clock (e.g. an oscillator) which provides a fixed clock of
> 20MHz with an accuracy of +- 20Hz. This accu
Hi David,
On Sun, 1 Dec 2013 17:23:15 -0700, David Ahern wrote:
> Add entry to perf-sched documentation for timehist command and its
> options.
[SNIP]
> +--max-stack::
> +Set the stack depth limit when showing the callchains. Default: 127
Isn't it 5 instead of 127?
Thanks,
Namhyung
--
To u
Hi,
On Tue, Nov 19, 2013 at 3:07 AM, Lee Jones wrote:
> In this patch we do two things. Firstly, instead of open coding the
> store of DMA data in to the DAI for later use, we use the API provided.
> Secondly we create and store similar DMA data for the DT case, only
> this time we use 'struct sn
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
> On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
>> Should be fixed with
>>
>> commit 7c063c725987406d743cc7de7625ff224fab75de
>> Author: Jesse Barnes
>> Date: Tue Nov 26 09:13:41 2013 -0800
>>
>> drm/i915: take mode config lock aro
Hi Srikar,
On Fri, 29 Nov 2013 14:55:21 +0530, Srikar Dronamraju wrote:
> * Namhyung Kim [2013-11-27 15:19:49]:
>> /**
>> * Kprobe event core functions
>> */
>> -struct trace_probe {
>> +struct trace_kprobe {
>> struct list_headlist;
>> struct kretproberp; /* Us
From: Zhouyi Zhou
the text of previous ping message maybe garbled sorry for the trouble
> I do a grep for kmem_cache_zalloc and kmem_cache_alloc
> in kernel tree, and find some code do not handle NULL
> return of kmem_cache_zalloc correctly
> Signed-off-by: Zhouyi Zhou
---
arch/powerpc/kvm/b
>
> > +"ftm0" (module clock),
> > +"ftm0_counter" (counter clock),
> > +- clocks : Must contain a clock specifier for each entry in
> > +clock-names,
> > + See clock/clock-bindings.txt for details of the property values.
>
> Note that the order is significant here, at least from the way
usb: phy-generic: Add GPIO based ChipSelect
The ULPI ISP1504 uses the CHIP_SELECT_N (low active) pin to active the
chip. This patch add support for GPIO based ChipSelect almost the same
way implemented for the Reset feature.
Sample DT configuration:
pinctrl_usbphy2: usbphy-2 {
fsl,pins = <
This patch set add support
* GPIO ChipSelect
* ULPI support to set VBUS flags for EXTVBUSIND,CHRGVBUS
* ULPI support to set VBUS flags from DT
[PATCH 1/3] usb: phy-generic: Add GPIO based ChipSelect
The ULPI ISP1504 uses the CHIP_SELECT_N (low active) pin to active the
chip. This
usb: phy-ulpi: Add EXTVBUSIND,CHRGVBUS flag support
ULPI like ISP1504 support external vbus power indication
used in combination with vbus switches mic2075.
Signed-off-by: Chris Ruehl
---
drivers/usb/phy/phy-ulpi.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
usb: phy-generic: Add ULPI VBUS support
Some platforms need to set the VBUS parameters of the ULPI
like ISP1504 which interact with overcurrent protection and
power switch MIC2575. Therefore it requires to set
* DRVVBUS
* DRVVBUS_EXT
* EXTVBUSIND
* CHRGVBUS
of the ULPI.
This patch add support for
From: Namhyung Kim
The --show-time-info option is for displaying elapsed sampling time
information for each entry.
$ perf record -- perf bench sched messaging
$ perf report --stdio --show-time-info
...
# Samples: 10K of event 'cycles'
# Event count (approx.): 5118793536
# Total sampl
From: Namhyung Kim
It's sometimes useful to see total sampling or elapsed time with
normal performance result. To do that, record first and last sample
time for each evsel and to display it in the header (--stdio only for
now).
$ perf record -a sleep 1
$ perf report --stdio
...
# Sample
Hi,
Sometimes users might want to see time information along with the
performance result but the perf cannot provide it currently.
In this patchset, I added such feature using sample->time. When the
perf processes sample events, it calculate time info and update last
timestamp. It keeps the las
From: Namhyung Kim
Calculate elapsed time for each sample and record it. The elapsed
time is a diff between current sample->time and previous sample->time
which was saved for each evsel and cpu.
Maybe we can use PERF_SAMPLE_READ for the precise result.
Signed-off-by: Namhyung Kim
---
tools/p
On Tuesday 19 November 2013 02:07 PM, Linus Walleij wrote:
> On Thu, Nov 14, 2013 at 1:18 PM, Sricharan R wrote:
>
>> The minimal crossbar driver to track and allocate free GIC lines and
>> configure the
>> crossbar is added here, along with the DT bindings.
>>
>> V4:
>>Addressed a couple of
cpufreq_generic_exit() is empty now and so can be deleted.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/blackfin-cpufreq.c | 1 -
drivers/cpufreq/cpufreq-cpu0.c | 1 -
drivers/cpufreq/cris-artpec3-cpufreq.c | 1 -
drivers/cpufreq/cris-etraxfs-cpufreq.c | 1 -
drivers/cpufreq/davin
Apart from the other patches, here are few minor cleanups for cpufreq core and
drivers. The first two removes per-cpu cpufreq_show_table variable and moves
that information in struct cpufreq_policy. And the last one removes unnecessary
frozen variable/parameters.
Viresh Kumar (3):
cpufreq: add '
We have used 'frozen' variable/function parameter at many places to
differentiate CPU hotplugging on suspend/resume vs sysfs removals. We now have
another variable cpufreq_suspended which can be used in these cases and hence we
can get rid of all those variables or function parameters.
Signed-off-
freq table is not per CPU but per policy and so it makes more sense to keep it
within struct cpufreq_policy instead of a per-cpu variable.
This patch does it. Over that there is no need to set policy->freq_table to NULL
in ->exit(), as policy structure is going to be freed soon.
Signed-off-by: Vi
(2013/12/02 9:07), David Ahern wrote:
> Allow user to specify an address within an executable. This is useful, for
> example, in probing local functions. If the function name begins with 0x
> then try to convert the supplied name to an address. If succuessful then
> treat the function name as the a
Hi Kim,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Saturday, November 30, 2013 9:48 AM
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH] f2fs: remove the own bi_p
Dear Guenter,
In message <529b9152.9090...@roeck-us.net> you wrote:
> On 11/30/2013 07:45 AM, Christophe Leroy wrote:
> > MPC8xx watchdog is enabled at startup by HW.
> > If the bootloader disables it, it cannot be reenabled.
>
> Is that true for all variants of 8xx, especially for 823 ? I am a b
* David Ahern [2013-12-01 17:23:15]:
> Add entry to perf-sched documentation for timehist command and its
> options.
>
> v2: Addressed comments by Namhyung
>
> Signed-off-by: David Ahern
> Cc: Ingo Molnar
> Cc: Frederic Weisbecker
> Cc: Peter Zijlstra
> Cc: Mike Galbraith
> Cc: Jiri Olsa
(2013/12/02 9:07), David Ahern wrote:
> When requesting a function from a userspace library the error message to
> the user is less than helpful. e.g.,
>
> perf probe -x /lib64/libpthread-2.14.90.so -a
> 'lock_full=__pthread_mutex_lock_full'
> no symbols found in /lib64/libpthread-2.14.90
Earlier cpufreq suspend/resume callbacks into drivers were getting called only
for the boot CPU, as by the time callbacks were called non-boot CPUs were
already removed. Because we might still need driver specific actions on
suspend/resume, its better to use earlier infrastructure from the early
su
(2013/12/02 9:07), David Ahern wrote:
> Allow user to specify an address within an executable. This is useful, for
> example, in probing local functions. If the function name begins with 0x
> then try to convert the supplied name to an address. If succuessful then
> treat the function name as the a
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Acked-and-tested-by: Stephen Warren
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/tegra-cpufreq.c | 46 +
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/exynos-cpufreq.c | 96 +++-
1 file
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/s5pv210-cpufreq.c | 49 +++
1 file
Multiple platforms need to set CPU to a particular frequency before suspending
system. And so they need a common infrastructure which is provided by this
patch. Those platforms just need to initialize their ->suspend() pointers with
the generic routine.
Tested-by: Stephen Warren
Signed-off-by: Vi
Recently support for suspending governors has been added in cpufreq and
callbacks are called from dpm_{suspend|resume}_noirq(). The problem here is that
most of the devices (i.e. devices with ->suspend() callbacks) have already been
suspended by now and so if drivers want to change frequency before
This patchset moves cpufreq callbacks to dpm_{suspend|resume}() from
dpm_{suspend|resume}_noirq() for handling suspend/resume of cpufreq governors
and core. This is required for early suspend and late resume of governors as
there are drivers which want to change cpu frequency before suspending gove
(Adding Jonas Bonn to list as he added the macro in the first place...)
On Mon, 2013-12-02 at 13:03 +0900, Jingoo Han wrote:
> On Monday, December 02, 2013 12:56 PM, Guenter Roeck wrote:
> > On 12/01/2013 07:50 PM, Jingoo Han wrote:
> > > On Monday, December 02, 2013 12:46 PM, Guenter Roeck wrote:
In the current code, if we fail during a frequency transition we simply send the
POSTCHANGE notification with old frequency. This isn't enough.
One of the core user of these notifications is the code responsible for keeping
loops_per_jiffy aligned with frequency change. And mostly it is written as
In the current code, if we fail during a frequency transition we simply send the
POSTCHANGE notification with old frequency. This isn't enough.
One of the core user of these notifications is the code responsible for keeping
loops_per_jiffy aligned with frequency change. And mostly it is written as
In the current code, if we fail during a frequency transition we simply send the
POSTCHANGE notification with old frequency. This isn't enough.
One of the core user of these notifications is the code responsible for keeping
loops_per_jiffy aligned with frequency change. And mostly it is written as
This introduces another routine cpufreq_notify_post_transition() which can be
used to send POSTCHANGE notification for new freq with or without both
{PRE|POST}CHANGE notifications for last freq. This is useful at multiple places,
specially for sending transition failure notifications.
Signed-off-b
In the current code, if we fail during a frequency transition we simply send the
POSTCHANGE notification with old frequency. This isn't enough.
One of the core user of these notifications is the code responsible for keeping
loops_per_jiffy aligned with frequency change. And mostly it is written as
Hi all,
Changes since 20131129:
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The sound-asoc tree lost its build failure.
The block tree gained conflicts against the f2fs tree.
Non-merge commits (relative to Linus' tree): 2243
2091 files changed, 81369 insertions(+),
Dear Sir,
Good day!
We had dealing welding materials for many years . And supplied high quality
different type Welding Electrode/Welding Wire/Sintered Flux to our old and new
customers.
Should any of the items be of interest to you, please let me know. We shall be
glad to give you our lowes
On Monday, December 02, 2013 01:10 PM, Peter Chen wrote:
If you have a look into the function hw_write() you will see that there
is no
effect if hw_write(...,sts) is called with sts=0/1, because the mask will
cut
off all bits beside BIT(29).
Yes, it is my careless. I thought sts is PORTCS_
On 1/17/13, Lance Ortiz wrote:
> This header file will define a new trace event that will be triggered when
> a AER event occurs. The following data will be provided to the trace
> event.
>
> char * dev_name - The name of the slot where the device resides
> ([domain:]bus:device.
>
> If you have a look into the function hw_write() you will see that there
> is no
> effect if hw_write(...,sts) is called with sts=0/1, because the mask will
> cut
> off all bits beside BIT(29).
Yes, it is my careless. I thought sts is PORTCS_STS.
> I used BIT(29) rather then PORTCS_STS to m
On 11/30/13 06:59, Masanari Iida wrote:
> Correct spelling typo in Documentation/devicetree
>
> Signed-off-by: Masanari Iida
> Reviewed-By: Levente Kurusa
Has Levente replied to this patch with his Reviewed-by: tag?
You should not add it just because he has reviewed the patch.
It is up to him t
Hi,
Some comments as following.
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Saturday, November 30, 2013 2:26 PM
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH]
Hi Kim,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Friday, November 29, 2013 6:14 PM
> To: Chao Yu
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net; 谭姝
> Subject: Re: [f2fs-dev] [PATCH 2/5] f
On Monday, December 02, 2013 12:56 PM, Guenter Roeck wrote:
> On 12/01/2013 07:50 PM, Jingoo Han wrote:
> > On Monday, December 02, 2013 12:46 PM, Guenter Roeck wrote:
> >> On 12/01/2013 04:07 PM, Jingoo Han wrote:
> >>> On Friday, November 29, 2013 10:34 AM, Jingoo Han wrote:
> On Thursday, N
Hi Jens,
Today's linux-next merge of the block tree got conflicts in
fs/f2fs/data.c and fs/f2fs/segment.c between commits 0626804cd9a6 ("f2fs:
remove the own bi_private allocation") and 899d7625d85a ("f2fs: refactor
bio-related operations") from the f2fs tree and commits 2c30c71bd653
("block: Conv
On 12/01/2013 07:50 PM, Jingoo Han wrote:
On Monday, December 02, 2013 12:46 PM, Guenter Roeck wrote:
On 12/01/2013 04:07 PM, Jingoo Han wrote:
On Friday, November 29, 2013 10:34 AM, Jingoo Han wrote:
On Thursday, November 28, 2013 3:24 PM, Joe Perches wrote:
On Wed, 2013-11-27 at 21:53 -0800
On Monday, December 02, 2013 12:46 PM, Guenter Roeck wrote:
> On 12/01/2013 04:07 PM, Jingoo Han wrote:
> > On Friday, November 29, 2013 10:34 AM, Jingoo Han wrote:
> >> On Thursday, November 28, 2013 3:24 PM, Joe Perches wrote:
> >>> On Wed, 2013-11-27 at 21:53 -0800, 'Greg Kroah-Hartman' wrote:
>
On 12/01/2013 04:07 PM, Jingoo Han wrote:
On Friday, November 29, 2013 10:34 AM, Jingoo Han wrote:
On Thursday, November 28, 2013 3:24 PM, Joe Perches wrote:
On Wed, 2013-11-27 at 21:53 -0800, 'Greg Kroah-Hartman' wrote:
On Wed, Nov 27, 2013 at 09:40:13PM -0800, Joe Perches wrote:
On Thu, 201
On Thu, Nov 28, 2013 at 09:02:58AM +0100, boris brezillon wrote:
> On 27/11/2013 19:10, Mike Turquette wrote:
> >Quoting boris brezillon (2013-11-27 09:19:08)
> >>>On Wed, Nov 27, 2013 at 01:44:45PM +0100, Boris BREZILLON wrote:
...
> >>>I would also prefer to see an unknown accuracy be -1.
> >>I d
ping
> I do a grep for kmem_cache_zalloc and kmem_cache_alloc
> in kernel tree, and find some code do not handle NULL
> return of kmem_cache_zalloc correctly
>
>
> Signed-off-by: Zhouyi Zhou
> ---
> arch/powerpc/kvm/book3s_32_mmu_host.c |5 +
> drivers/iommu/omap-iommu.c|
From: Fabio Estevam
clk_prepare_enable() may fail, so let's check its return value and propagate it
in the case of error.
Signed-off-by: Fabio Estevam
---
drivers/rtc/rtc-mxc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-mxc.c b/drivers/rtc/rtc-mxc.c
From: Fabio Estevam
There is no need to jump to the 'exit_free_pdata' label when devm_clk_get()
fails, as we can directly return the error and simplify the code a bit.
Signed-off-by: Fabio Estevam
---
drivers/rtc/rtc-mxc.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a
Boris,
Sorry for the delay.
On Wed, Nov 27, 2013 at 06:19:08PM +0100, boris brezillon wrote:
> On 27/11/2013 15:56, Jason Cooper wrote:
> >On Wed, Nov 27, 2013 at 01:44:45PM +0100, Boris BREZILLON wrote:
> >>This patch adds support for accuracy retrieval on fixed clocks.
> >>It also adds a new dt
On 11/30/2013 02:25 PM, Jaegeuk Kim wrote:
> This patch integrates redundant bio operations on read and write IOs.
>
> 1. Move bio-related codes to the top of data.c.
> 2. Replace f2fs_submit_bio with f2fs_submit_merged_bio, which handles read
>bios additionally.
> 3. Introduce __submit_merge
On 11/29/13 at 12:50pm, Borislav Petkov wrote:
> No need for the list - I actually meant you simply use a tmp pointer for
> each krealloc invocation - just look around the tree for examples.
>
> Also think about what happens to the pointed-to memory when krealloc
> returns NULL.
Ok, thanks for th
On Mon, Dec 02, 2013 at 10:11:21AM +0800, Ming Lei wrote:
> On Sat, Nov 30, 2013 at 6:23 AM, Tejun Heo wrote:
> > On Tue, Nov 26, 2013 at 12:43:37PM +0800, Ming Lei wrote:
> >> sg_copy_buffer() can't meet demand for some drrivers(such usb
> >> mass storage), so we have to use the sg_miter_* APIs t
On 11/29/13 at 11:59am, Matt Fleming wrote:
> On Fri, 29 Nov, at 12:50:29PM, Borislav Petkov wrote:
> > > I did not add KEXEC because I thought it can be used for debugging
> > > purpose.
> >
> > mfleming is thinking about it :)
>
> I finally finished my thought. The sysfs code should be automat
On Friday, 29 November 2013 09:40:02 UTC+8, Andreas Noever wrote:
> Thunderbolt hotplug is supposed to be implemented by the firmware. But Apple's
> firmeware only initializes devices during boot and ignores hotplugged devices.
> This patch series adds a driver for the Intel Cactus Ridge Thunderbo
On 11/29/13 at 05:46pm, Borislav Petkov wrote:
> On Fri, Nov 29, 2013 at 05:14:16PM +0800, Dave Young wrote:
> > That's reserved for future extension use, who knows if we will need to
> > pass other fields in the future.
>
> Hrrmmm, 8*64 = 64 Bytes?? And you can't change it later because of the
>
> > > > +#define FTM_CNTIN_VAL 0x00
> > >
> > > Do we really need this?
> > >
> >
> > Maybe not, I think that the initial value maybe modified in the future.
> > And this can be more easy to ajust it.
>
> Why would it need to be modified?
>
Well, for the PWM function modifying it make no s
On 11/29/13 at 05:47pm, Borislav Petkov wrote:
> On Fri, Nov 29, 2013 at 04:50:50PM +0800, Dave Young wrote:
> > It's for debugging purpose, I think it's helpful.
>
> Why? The first kernel did dump it already.
As for the efi printk though 1st kernel already printed them out, but kexec
kernel
con
On 11/29/13 at 06:02pm, Borislav Petkov wrote:
> On Fri, Nov 29, 2013 at 04:28:22PM +0800, Dave Young wrote:
> > I think for anyone who are using early_memremap should know this is a
> > normal kernel memory instead of real __iomem
>
> You can never ever assume that people are using kernel interfa
On 12/02/2013 10:26 AM, Dongsheng Yang wrote:
The package required for numa is named numactl-devel in Fedora or RHEL,
and libnuma-devel in OpenSuSE, and libnuma-dev in Ubuntu. This patch
corrects the package name in warning message in feature-libnuma checking.
Thanks (and thanks for correcting
Here is a pile of bug fixes that accumulated while I was in Europe.
1) In fixing kernel leaks to userspace during copying of socket
addresses, we broke a case that used to work, namely the user
providing a buffer larger than the in-kernel generic socket address
structure. This broke Rub
The package required for numa is named numactl-devel in Fedora or RHEL,
and libnuma-devel in OpenSuSE, and libnuma-dev in Ubuntu. This patch
corrects the package name in warning message in feature-libnuma checking.
Signed-off-by: Dongsheng Yang
---
Changes since v1
- Add libnuma-dev for
On Tue, Oct 29, 2013 at 01:42:41PM +0900, Simon Horman wrote:
> On Wed, Oct 09, 2013 at 07:39:18PM +0900, Simon Horman wrote:
> > On Wed, Oct 09, 2013 at 04:29:56PM +0900, Magnus Damm wrote:
> > > Hi Simon,
> > >
> > > On Wed, Oct 9, 2013 at 3:54 PM, Simon Horman wrote:
> > > > On Wed, Oct 09, 20
On Sat, Nov 30, 2013 at 6:23 AM, Tejun Heo wrote:
> On Tue, Nov 26, 2013 at 12:43:37PM +0800, Ming Lei wrote:
>> sg_copy_buffer() can't meet demand for some drrivers(such usb
>> mass storage), so we have to use the sg_miter_* APIs to access
>> sg buffer, then need export sg_miter_skip() for these
Hi Axel,
I am fine to resend it to RMK's patch system, but I am not sure
if Russell would like to host it.
Maybe it is better to push it via Rusty's tree since the change is only
on scripts/, and it doesn't depend on the 1st one.
Rusty, could you pick up the patch with title of
"scripts/link-vml
On 11/30/2013 09:48 AM, Jaegeuk Kim wrote:
> Previously f2fs allocates its own bi_private data structure all the time even
> though we don't use it. But, can we remove this bi_private allocation?
>
> This patch removes such the additional bi_private allocation.
>
> 1. Retrieve f2fs_sb_info from
2013/11/13 Ming Lei :
> Hi Axel,
>
> On Wed, Nov 13, 2013 at 5:58 PM, Axel Lin wrote:
>>
>> Hi Ming,
>> You missed "; then" in the end of if statement in your patch.
>>
>> So I got below error with your patch:
>> scripts/link-vmlinux.sh: line 87: syntax error near unexpected token `fi'
>> make: **
Hi
On Sunday, December 01, 2013 01:28 AM, Sergei Shtylyov wrote:
Hello.
On 30-11-2013 7:51, Chris Ruehl wrote:
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* Set PORTCS_STS only if VUSB_HS_PHY_TYPE > 1
otherwise the register is Rea
On 12/01/2013 08:33 PM, Peter Hurley wrote:
On 12/02/2013 09:11 AM, Dongsheng Yang wrote:
ccing linux-kernel@vger.kernel.org
On 11/29/2013 01:14 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 29, 2013 at 04:05:52PM -0500, Dongsheng Yang escreveu:
The package required for numa is named numactl
On Saturday, November 30, 2013 06:20 PM, Peter Chen wrote:
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* Set PORTCS_STS only if VUSB_HS_PHY_TYPE> 1
otherwise the register is ReadOnly
* Set/Reset correct BIT(28)/BIT(29) for STS
I have a Dell Inspiron N7010 Laptop with Intel graphics. When the dell-laptop
module is loaded,
two backlight device devices are created; dell_backlight, and intel_backlight
from the Intel
graphics driver. The dell_backlight device is non-functional, but the graphics
subsystem uses
it instead of
Reviewed-by: Yijing Wang
On 2013/11/29 16:50, Jiang Liu wrote:
> In function free_dmar_iommu(), it sets IRQ handler data to NULL
> before calling free_irq(), which will cause invalid memory access
> because free_irq() will access IRQ handler data when calling
> function dmar_msi_mask(). So only s
On 2013/11/29 16:50, Jiang Liu wrote:
> Flag irq_remapping_enabled is only set by intel_enable_irq_remapping(),
> which is called after detect_intel_iommu(). So we should check flag
> disable_irq_remap instead of irq_remapping_enabled in function
> detect_intel_iommu().
>
> Signed-off-by: Jiang Li
Hi
On Mon, Dec 2, 2013 at 1:24 AM, Anton Vorontsov wrote:
> On Mon, Dec 02, 2013 at 01:02:40AM +0100, Michael Trimarchi wrote:
>> On Sun, Dec 1, 2013 at 11:37 PM, Anton Vorontsov wrote:
>> > On Mon, Nov 25, 2013 at 08:16:34PM +0100, Michael Trimarchi wrote:
>> > ...
>> >> >> So you can read this
This patch is the same as the last.:)
On 2013/11/29 16:50, Jiang Liu wrote:
> Flag irq_remapping_enabled is only set by intel_enable_irq_remapping(),
> which is called after detect_intel_iommu(). So we should check flag
> disable_irq_remap instead of irq_remapping_enabled in function
> detect_inte
On 2013/11/29 16:50, Jiang Liu wrote:
> Release allocated resources on error recovery path in function
> iommu_init_domains().
>
> Signed-off-by: Jiang Liu
> ---
> drivers/iommu/intel-iommu.c |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iommu/intel-iommu.c b/drivers/iom
Reviewed-by: Yijing Wang
On 2013/11/29 16:50, Jiang Liu wrote:
> Function dmar_parse_dev_scope() should release the PCI device reference
> count gained in function dmar_parse_one_dev_scope() on error recovery,
> otherwise will cause PCI device object leakage.
>
> This patch also introduces dmar_
Tested-and-reviewed-by: Yijing Wang
On 2013/11/29 16:50, Jiang Liu wrote:
> Currently Intel interrupt remapping drivers uses the "present" flag bit
> in remapping entry to track whether an entry is allocated or not.
> It works as follow:
> 1) allocate a remapping entry and set its "present" flag
On 12/02/2013 09:11 AM, Dongsheng Yang wrote:
ccing linux-kernel@vger.kernel.org
On 11/29/2013 01:14 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 29, 2013 at 04:05:52PM -0500, Dongsheng Yang escreveu:
The package required for numa is named numactl-devel in Fedora and RHEL and
libnuma-devel
From: "Michael S. Tsirkin"
Date: Thu, 28 Nov 2013 13:30:55 +0200
> Eric Dumazet noticed that if we encounter an error
> when processing a mergeable buffer, we don't
> dequeue all of the buffers from this packet,
> the result is almost sure to be loss of networking.
>
> Jason Wang noticed that we
From: "Michael S. Tsirkin"
Date: Thu, 28 Nov 2013 13:30:59 +0200
> receive mergeable now handles errors internally.
> Do same for big and small packet paths, otherwise
> the logic is too hard to follow.
>
> Signed-off-by: Michael S. Tsirkin
> Acked-by: Jason Wang
Applied and I fixed the subje
On Sunday, December 01, 2013 02:24:33 AM Rafael J. Wysocki wrote:
> On Saturday, November 30, 2013 02:27:15 PM Yinghai Lu wrote:
> > On Sat, Nov 30, 2013 at 1:37 PM, Rafael J. Wysocki
> > wrote:
> > > On Saturday, November 30, 2013 01:31:33 AM Rafael J. Wysocki wrote:
> > >> On Saturday, November
ccing linux-kernel@vger.kernel.org
On 11/29/2013 01:14 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 29, 2013 at 04:05:52PM -0500, Dongsheng Yang escreveu:
The package required for numa is named numactl-devel in Fedora and RHEL and
libnuma-devel in OpenSuSE. This patch correct the package nam
On Mon, 2 Dec 2013 12:04:37 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drm-intel tree got a conflict in
> drivers/gpu/drm/i915/intel_display.c between commit a1216444283e
> ("drm/i915: use the correct force_wake function at the PC8 code") from
> the drm-intel-fixes tree and
On Sunday, December 01, 2013 12:39:19 PM Michael Chan wrote:
> On Sun, 2013-12-01 at 02:34 +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Modify tg3_chip_reset() and tg3_close() to check if the PCI network
> > adapter device is accessible at all in order to skip poking it or
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_display.c between commit a1216444283e
("drm/i915: use the correct force_wake function at the PC8 code") from
the drm-intel-fixes tree and commit c8d9a5905e45 ("drm/i915: Add power
well arguments to
On Mon, 2013-12-02 at 08:34 +0800, Chen Gang wrote:
> On 12/02/2013 12:17 AM, Bart Van Assche wrote:
> > On 11/27/13 03:29, Chen Gang wrote:
> >> the macro "SP" is too common to make conflict with some architectures,
> >> so recommend to add prefix for it.
> >>
> >> The related warning (with allmod
On 12/02/2013 06:38 AM, Joe Perches wrote:
> On Sun, 2013-12-01 at 10:35 +0100, Johannes Berg wrote:
>> Good try, but no, now ap_sdata isn't even assigned. :)
>
> Right. Oh well. There's no improving this without
> significant rewrite. Even then, there may not be much
> overall improvement.
>
On 12/02/2013 12:17 AM, Bart Van Assche wrote:
> On 11/27/13 03:29, Chen Gang wrote:
>> the macro "SP" is too common to make conflict with some architectures,
>> so recommend to add prefix for it.
>>
>> The related warning (with allmodconfig for hexagon):
>>
>> CC [M] drivers/scsi/scsi_lib.o
>
On Mon, Dec 02, 2013 at 01:02:40AM +0100, Michael Trimarchi wrote:
> On Sun, Dec 1, 2013 at 11:37 PM, Anton Vorontsov wrote:
> > On Mon, Nov 25, 2013 at 08:16:34PM +0100, Michael Trimarchi wrote:
> > ...
> >> >> So you can read this value without any type of synchronization
> >> >> with the power_
Add entry to perf-sched documentation for timehist command and its
options.
v2: Addressed comments by Namhyung
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Mike Galbraith
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Stephane Eranian
Cc: Pekka Enberg
---
'perf sched timehist' provides an analysis of scheduling events.
Example usage:
perf sched record -- sleep 1
perf sched timehist
By default it shows the individual schedule events, including the time between
sched-in events for the task, the task scheduling delay (time between wakeup
and
1 - 100 of 211 matches
Mail list logo
