On Tuesday, January 29, 2013 11:04:57 AM Konstantin Khlebnikov wrote:
> Rafael J. Wysocki wrote:
> > On Monday, January 28, 2013 04:17:42 PM Bjorn Helgaas wrote:
> >> [+cc Rafael]
> >>
> >> On Fri, Jan 18, 2013 at 4:42 AM, Konstantin Khlebnikov
> >> wrote:
> >>> This patch effectively reverts
This field will be used by commands which print
counter deltas on regular timer intervals,
such as perf stat -I.
Signed-off-by: Stephane Eranian
---
tools/perf/util/evsel.c | 26 ++
tools/perf/util/evsel.h |1 +
2 files changed, 27 insertions(+)
diff --git
This patch adds a new printing mode for perf stat.
It allows internval printing. That means perf stat
can now print event deltas at regular time interval.
This is useful to detect phases in programs.
The -I option enables interval printing. It expects
an interval duration in milliseconds. Minimum
This small patchset extends perf stat with the -I option.
The -I option enables interval printing. It expects
an interval duration in milliseconds. Minimum is
100ms. Once, activated perf stat prints events deltas
since last printout. All modes are supported.
$ perf stat -I 1000 -e cycles noploop
On 1/28/2013 6:41 PM, Pantelis Antoniou wrote:
Fix interrupt storm on bone A4 cause by non-by-the-book interrupt handling.
While at it, added a non-NAPI mode (which is easier to debug), plus
some general fixes.
Signed-off-by: Pantelis Antoniou
---
(2013/01/25 13:09), Sasha Levin wrote:
> As to arch_check_optimized_kprobe() and check_kprobe_address_safe(), this
> is simply way too confusing. It doesn't make sense that a function named
> check_[...]() would modify any of it's parameters.
>
> For example, that entire block within
On Tuesday, January 29, 2013 10:09:59 AM Viresh Kumar wrote:
> With the addition of following patch, related_cpus is required to be set by
> cpufreq platform drivers:
>
> commit c1070fd743533efb54e98142252283583f379190
> Author: Viresh Kumar
> Date: Mon Jan 14 13:23:04 2013 +
>
>
Am Dienstag, 29. Januar 2013, 10:15:49 schrieb Russell King - ARM Linux:
> On Mon, Jan 28, 2013 at 02:25:10PM -0800, Andrew Morton wrote:
> > What's this "with enabled unaligned memory access" thing? You mean "if
> > the arch supports CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS"? If so,
> > that's
On 01/29/2013 12:36 PM, Heiko Carstens wrote:
On Tue, Jan 29, 2013 at 08:12:00AM +0100, Hannes Reinecke wrote:
This patch adds a 'timeout' attibute to the DASD driver.
When set to non-zero, the blk_timeout function will
be enabled with the timeout specified in the attribute.
Setting 'timeout'
On Tuesday 29 January 2013 16:22:45 Vivek Gautam wrote:
> This change de-asserts vbus_gpio on suspend and
> re-asserts on resume in order to save power.
> NOTE, this change means no USB charging in suspend
> mode.
What happens if a device on the bus is a source of wakeups?
Regards
On Tue, Jan 29, 2013 at 08:12:00AM +0100, Hannes Reinecke wrote:
> This patch adds a 'timeout' attibute to the DASD driver.
> When set to non-zero, the blk_timeout function will
> be enabled with the timeout specified in the attribute.
> Setting 'timeout' to '0' will disable block timeouts.
>
>
On Tuesday, January 29, 2013 10:58:20 AM fli24 wrote:
>
> At present, the timeout value for freezing tasks is fixed as 20s,
> which is too long for handheld device usage, especially for mobile
> phone.
>
> In order to improve user experience, we enable freeze timeout
> configuration through
On 01/29/2013 12:32 PM, Heiko Carstens wrote:
On Tue, Jan 29, 2013 at 08:11:56AM +0100, Hannes Reinecke wrote:
This patch implements generic block layer timeout handling
callbacks for DASDs. When the timeout expires the respective
cqr is aborted.
With this timeout handler time-critical request
On Tue, Jan 29, 2013 at 08:11:56AM +0100, Hannes Reinecke wrote:
> This patch implements generic block layer timeout handling
> callbacks for DASDs. When the timeout expires the respective
> cqr is aborted.
>
> With this timeout handler time-critical request abort
> is guaranteed as the abort
On Tuesday, January 29, 2013 11:20:44 AM Yasuaki Ishimatsu wrote:
> Hi Rafael,
>
> 2013/01/28 22:01, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Currently, the ACPI namespace scanning code creates platform device
> > objects for ACPI device nodes whose IDs match the contents of
Hello,
A bit analysis in addition to my previous message.
The problem is that we receive NULL pointer dereference errors from inside of
CFS (upstream kernel version 3.2-3.7) while running heavy loaded
kvm-virtualized guests on 2-numa node server.
Null pointers are always met in
Gary,
For arch/arm/ patches, list linux-arm-ker...@lists.infradead.org rather
than linux-kernel@vger.kernel.org should be copied.
One comment blow.
On Tue, Jan 29, 2013 at 03:49:39PM +0800, Gary Zhang wrote:
> in imx6q sabresd board, wm8962 uses CKO1 as MCLK. set ahb as CKO1
> parent clock
On Monday, January 28, 2013 07:35:39 PM Toshi Kani wrote:
> On Mon, 2013-01-28 at 13:59 +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Introduce struct acpi_scan_handler for representing objects that
> > will do configuration tasks depending on ACPI device nodes'
> >
On Mon, Jan 28, 2013 at 10:07:15PM -0200, Marcelo Tosatti wrote:
> On Fri, Jan 25, 2013 at 10:46:31AM +0800, Xiao Guangrong wrote:
> > On 01/25/2013 08:15 AM, Marcelo Tosatti wrote:
> > > On Wed, Jan 23, 2013 at 06:07:20PM +0800, Xiao Guangrong wrote:
> > >> It makes set_spte more clean and
On Thu, 24 Jan 2013 10:00:04 +0530, Srivatsa S. Bhat wrote:
> On 01/24/2013 01:27 AM, Tejun Heo wrote:
>> On Thu, Jan 24, 2013 at 01:03:52AM +0530, Srivatsa S. Bhat wrote:
>>> CPU 0 CPU 1
>>>
>>> read_lock()
>>>
>>> write_lock() //spins,
Am 29.01.2013 11:35, schrieb Alexander Holler:
Am 29.01.2013 01:56, schrieb Alexander Holler:
Am 29.01.2013 01:22, schrieb Andrew Morton:
On Fri, 25 Jan 2013 19:49:27 +0100
Alexander Holler wrote:
When a device was disconnected the driver may hang at waiting for
urbs it never
will get. Fix
On Tue, Jan 29, 2013 at 02:35:16PM +0530, Laxman Dewangan wrote:
> Add DT support for TI PMIC tps65090 regulator driver. The DT of this
> device have node regulator and all regulator's node of this device is
> added under this node.
There doesn't seem to be any dependency on the rest of the
On Mon, Jan 28, 2013 at 02:46:53AM +, Lei Wen wrote:
> On Sat, Sep 8, 2012 at 12:26 AM, Catalin Marinas
> mailto:catalin.mari...@arm.com>> wrote:
> > This patch adds SMP initialisation and spinlocks implementation for
> > AArch64. The spinlock support uses the new load-acquire/store-release
>
There could be a service transport, which is processed by service thread and
racing in the same time with per-net service shutdown like listed below:
CPU#0:CPU#1:
svc_recvsvc_close_net
svc_get_next_xprt (list_del_init(xpt_ready))
> Now I activated the debug messages in em28xx. From the messages I
> see no correlation of the pool exhaustion and lost sync. Also I
> cannot see any error messages from the em28xx driver.
> I see a lot of init_isoc/stop_urbs (maybe EPG scan?) without
> draining the coherent pool (checked with
On Tue, Jan 29, 2013 at 8:38 AM, Vishwanathrao Badarkhe, Manish
wrote:
> Currently, I2C driver gets probed before pinctrl driver.
> To achieve I2C pin muxing via pinctrl driver before I2C
> probe get called, register pinctrl driver in arch_initcall.
> Also, add module_exit to unregister pinctrl
At Tue, 29 Jan 2013 18:24:04 +0800,
Ming Lei wrote:
>
> Hi Takashi,
>
> On Sat, Jan 26, 2013 at 12:05 AM, Takashi Iwai wrote:
> > Since 3.7 kernel, the firmware loader can read the firmware files
> > directly, and the traditional user-mode helper is invoked only as a
> > fallback. This seems
On Tue, Jan 29, 2013 at 3:41 AM, Chanho Min wrote:
> On Mon, Jan 28, 2013 at 5:28 PM, Linus Walleij
> wrote:
>> On Mon, Jan 28, 2013 at 9:15 AM, Chanho Min wrote:
>>> [Russell]
Well, I thought I had explained that I'd prefer to see the poll rate
adjusted with the baud rate, but maybe I
On Tue, Jan 29, 2013 at 09:03:05AM +0100, Ingo Molnar wrote:
>
> * Stephane Eranian wrote:
>
> > On Mon, Jan 28, 2013 at 9:52 PM, Stephane Eranian
> > wrote:
> > > Jiri,
> > >
> > > I don't see part 0/8 of this series. Did you send it to me too?
oops, it went to lkml only, here it is:
On Tue, 29 Jan 2013 02:54:28 -0800 Andrew Morton
wrote:
> On Mon, 28 Jan 2013 11:19:39 -0800 Dave Hansen
> wrote:
>
> > My patch "Fix kvm's use of __pa() on percpu areas" introduced a
> > compile warning:
> >
> > arch/x86/kernel/kvm.c: In function 'kvm_register_steal_time':
> >
On Mon, 28 Jan 2013 11:19:39 -0800 Dave Hansen wrote:
> My patch "Fix kvm's use of __pa() on percpu areas" introduced a
> compile warning:
>
> arch/x86/kernel/kvm.c: In function 'kvm_register_steal_time':
> arch/x86/kernel/kvm.c:302:3: warning: format '%lx' expects argument of type
> 'long
On Tue, Jan 29, 2013 at 11:48:12AM +0100, Borislav Petkov wrote:
> From: Borislav Petkov
>
> a0c17eadf3bf9 ("perf: Add 'perf bench numa mem' NUMA performance
> measurement suite") added -lnuma to the EXTLIBS but we use those when
> checking for other libraries like libelf, libunwind, etc and the
From: Borislav Petkov
It should be
make -C tools/ _install
Signed-off-by: Borislav Petkov
---
tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/Makefile b/tools/Makefile
index 1f9a529fe544..798fa0ef048e 100644
--- a/tools/Makefile
+++ b/tools/Makefile
From: Borislav Petkov
a0c17eadf3bf9 ("perf: Add 'perf bench numa mem' NUMA performance
measurement suite") added -lnuma to the EXTLIBS but we use those when
checking for other libraries like libelf, libunwind, etc and the checks
failed even when the dev libraries are installed on the system:
On Mon, Jan 28, 2013 at 3:23 PM, Mathias Nyman
wrote:
> Add ability to handle ACPI events signalled by GPIO interrupts.
>
> ACPI5 platforms can use GPIO signaled ACPI events. These GPIO interrupts are
> handled by ACPI event methods which need to be called from the GPIO
> controller's interrupt
Hi
No exactly sure which patch did it - but when I'm now checking 3.8-rc5 kernel,
I cannot use anymore this 'undock' command:
echo 1 >/sys/devices/platform/dock.0/undock
which works ok with 3.7 kernel - to properly undock my T61 before suspend.
Dmesg shows this:
[ 2657.087414] ACPI:
On Mon, Jan 28, 2013 at 05:07:15PM -0800, Hugh Dickins wrote:
> On Mon, 28 Jan 2013, Andrew Morton wrote:
> > On Fri, 25 Jan 2013 17:53:10 -0800 (PST)
> > Hugh Dickins wrote:
> >
> > > Here's a KSM series
> >
> > Sanity check: do you have a feeling for how useful KSM is?
> > Performance/space
This change de-asserts vbus_gpio on suspend and
re-asserts on resume in order to save power.
NOTE, this change means no USB charging in suspend
mode.
Signed-off-by: Vivek Gautam
CC: Doug Anderson
---
Based on 'usb-next'.
drivers/usb/host/ehci-s5p.c | 29 ++---
1
The nr_busy_cpus field of the sched_group_power is sometime different from 0
whereas the platform is fully idle. This serie fixes 3 use cases:
- when some CPUs enter idle state while booting all CPUs
- when a CPU is unplug and/or replug
Change since V1:
- remove the patch for SCHED softirq on
On my smp platform which is made of 5 cores in 2 clusters,I have the
nr_busy_cpu field of sched_group_power struct that is not null when the
platform is fully idle. The root cause seems to be:
During the boot sequence, some CPUs reach the idle loop and set their
NOHZ_IDLE flag while waiting for
The function nohz_kick_needed modifies NOHZ_IDLE flag that is used to update
the nr_busy_cpus of the sched_group.
When the sched_domain are updated (during the boot or because of the unplug of
a CPUs as an example) a null_domain is attached to CPUs. We have to test
likely(!on_null_domain(cpu)
On Fri, 2013-01-25 at 16:30 +0100, Stephane Eranian wrote:
> On Fri, Jan 25, 2013 at 10:01 AM, Ingo Molnar wrote:
> >
> > Would be nice to get feedback from PowerPC folks to see how well
> > this matches their memory profiling hw capabilities?
> >
> I agree, I tried to remain as generic as
On Tue, Jan 29, 2013 at 06:22:53AM +0200, Thomas Backlund wrote:
>
> [tmb@tmb linux-3.8-rc5]$ make -C tools/perf -s V=1
> HAVE_CPLUS_DEMANGLE=1 prefix=%{_prefix} all
>
> ...
>
> /tmp/ccJEJv6m.o: In function `main':
> :(.text+0x14): undefined reference to `strlcpy'
> collect2: ld returned 1 exit
Am 29.01.2013 01:56, schrieb Alexander Holler:
Am 29.01.2013 01:22, schrieb Andrew Morton:
On Fri, 25 Jan 2013 19:49:27 +0100
Alexander Holler wrote:
When a device was disconnected the driver may hang at waiting for urbs it never
will get. Fix this by using a timeout while waiting for the
On Fri, Jan 25, 2013 at 09:54:07AM +0100, Maxime Ripard wrote:
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/boot/dts/imx28-cfa10049.dts | 99
> ++
> arch/arm/mach-mxs/mach-mxs.c | 22
> 2 files changed, 121 insertions(+)
>
Applied,
Hi Takashi,
On Sat, Jan 26, 2013 at 12:05 AM, Takashi Iwai wrote:
> Since 3.7 kernel, the firmware loader can read the firmware files
> directly, and the traditional user-mode helper is invoked only as a
> fallback. This seems working pretty well, and the next step would be
> to reduce the
On 01/28/2013 07:27 PM, Seth Jennings wrote:
> Yes, I prototyped a shrinker interface for zswap, but, as we both
> figured, it shrinks the zswap compressed pool too aggressively to the
> point of being useless.
Can't you advertise a smaller number of objects that you actively have?
Since the
Hi Srivatsa,
On Tue, 22 Jan 2013 13:04:54 +0530, Srivatsa S. Bhat wrote:
> @@ -246,15 +291,21 @@ struct take_cpu_down_param {
> static int __ref take_cpu_down(void *_param)
> {
> struct take_cpu_down_param *param = _param;
> - int err;
> + unsigned long flags;
> + int err = 0;
On Mon, 2012-11-05 at 11:58 +0100, Paul Bolle wrote:
> Building advansys.o triggers this warning:
> drivers/scsi/advansys.c:71:2: warning: #warning this driver is still not
> properly converted to the DMA API [-Wcpp]
>
> This warning can be traced back to a patch called "advansys: add
On Fri, Jan 25, 2013 at 7:22 PM, Maxim V. Patlasov
wrote:
> Make fuse think that when writeback is on the inode's i_size is always
> up-to-date and not update it with the value received from the userspace.
> This is done because the page cache code may update i_size without letting
> the FS know.
On Tue, Jan 29, 2013 at 09:17:04AM +0100, Peter Ujfalusi wrote:
> On 01/28/2013 10:01 PM, Thierry Reding wrote:
> > On Tue, Jan 22, 2013 at 02:39:53PM +0100, Peter Ujfalusi wrote:
> >> It is expected that board files would have:
> >> static unsigned int bl_levels[] = { 0, 50, 100, 150, 200, 250,
On Mon, Jan 28, 2013 at 02:25:10PM -0800, Andrew Morton wrote:
> What's this "with enabled unaligned memory access" thing? You mean "if
> the arch supports CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS"? If so,
> that's only x86, which isn't really in the target market for this
> patch, yes?
>
> It's
On Tue, Jan 29, 2013 at 12:08:23PM +0200, Roger Quadros wrote:
> On 01/29/2013 11:57 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
> >> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> >> library and put it out
On Tue, Jan 29, 2013 at 12:13:46PM +0530, Santosh Shilimkar wrote:
> To avoid the server latency, we didn't do continuous sync. The time was
> synced in the beginning and after 62.5 hours (#ntpd -qg) and the drift
> of about 174 ms was observed. As you said this could be because of
> server sync
On 01/29/2013 11:57 AM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
>> For each port that is in PHY mode we obtain a PHY device using the USB PHY
>> library and put it out of suspend.
>>
>> It is up to platform code to associate the PHY to the
On Mon, Jan 28, 2013 at 06:06:38PM +0800, Zhang Rui wrote:
> On Mon, 2013-01-28 at 09:31 +0100, Daniel Vetter wrote:
> > On Mon, Jan 28, 2013 at 3:36 AM, Zhang Rui wrote:
> > >> Given that this essentially requires users to manually set this module
> > >> option to make stuff work I don't like
Previously the alarm event was not propagated into the RTC subsystem.
By adding a call to rtc_update_irq, this fixes a timeout problem with
the hwclock utility.
Signed-off-by: Jan Luebbe
---
drivers/rtc/rtc-isl1208.c |3 +++
1 file changed, 3 insertions(+)
diff --git
Hi Vineet,
>> arm64 also adds dtbs and $(dtb-y) to targets (at least in linux-next). I
>> think this makes sure that they don't get rebuilt unless they've
>> actually changed. I've also copied this for metag.
>
> Did you verify that it makes a difference - at least at my end it's not - the
>
On Mon, 2012-10-29 at 13:45 +0100, Paul Bolle wrote:
> On Mon, 2012-10-29 at 12:17 +, James Bottomley wrote:
> > mvsas has a maintainer: poke them harder
>
> According to MAINTAINERS that's you. Is Xiangliang Yu perhaps the actual
> maintainer?
Building the mvsas driver triggers identical
On Tue, Jan 29, 2013 at 10:57 AM, Takashi Iwai wrote:
> At Tue, 29 Jan 2013 10:53:50 +0100,
> Daniel Vetter wrote:
>>
>> On Tue, Jan 29, 2013 at 09:29:17AM +0100, Takashi Iwai wrote:
>> > Add a new option, bpp, to specify the default bpp value.
>> >
>> > Signed-off-by: Takashi Iwai
>> > ---
>> >
On Tue, Jan 22, 2013 at 02:39:56PM +0100, Peter Ujfalusi wrote:
> When booting with DT make it possible to use the whole range of the PWM when
> controlling the backlight in a same way it is possible when the kernel is
> booted in non DT mode.
> A new property "max-brightness-level" can be used to
Hi,
On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> library and put it out of suspend.
>
> It is up to platform code to associate the PHY to the controller's
> port and it is upto the PHY driver to
On Mon, 28 Jan 2013, si...@mungewell.org wrote:
> >> I'm happy to change it; However Steelseries' other devices are all
> >> keyboards/mice intended for/marketed at gamers. Since other Steelseries
> >> devices are unlikely to have the same structure (OK I'm just guessing on
> >> that) is it
On Mon, 2012-10-08 at 11:15 -0500, Saurav Kashyap wrote:
> Acked-by: Saurav Kashyap
>
> Thanks,
> ~Saurav
>
> >Compiling qla_gs.o (part of the qla2xxx module) triggers two GCC
> >warnings:
> >drivers/scsi/qla2xxx/qla_gs.c: In function Œqla2x00_fdmi_rhba¹:
> >
At Tue, 29 Jan 2013 10:53:50 +0100,
Daniel Vetter wrote:
>
> On Tue, Jan 29, 2013 at 09:29:17AM +0100, Takashi Iwai wrote:
> > Add a new option, bpp, to specify the default bpp value.
> >
> > Signed-off-by: Takashi Iwai
> > ---
> >
> > This patch is applied on the top of previous two patches.
Hi James,
On Monday 28 January 2013 03:51 PM, James Hogan wrote:
> Hi Vineet,
>
> On 24/01/13 10:50, Vineet Gupta wrote:
>> diff --git a/arch/arc/Makefile b/arch/arc/Makefile
>> index 4d52a3b..90570f9 100644
>> --- a/arch/arc/Makefile
>> +++ b/arch/arc/Makefile
>> @@ -83,6 +83,9 @@ head-y
On Mon, 14 Jan 2013, Steve Wise wrote:
> Reviewed-by: Steve Wise
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, Jan 28, 2013 at 05:49:53PM +0100, Stephen Warren wrote:
> On 01/28/2013 08:54 AM, Peter De Schrijver wrote:
> > The tegra peripheral clock type uses struct clk_mux directly, so it needs to
> > be updated to handle the new mask and table fields. Also the macros need
> > to be updated
>
>
On Tue, Jan 29, 2013 at 09:29:17AM +0100, Takashi Iwai wrote:
> Add a new option, bpp, to specify the default bpp value.
>
> Signed-off-by: Takashi Iwai
> ---
>
> This patch is applied on the top of previous two patches.
> I couldn't find an easy way to specify the default bpp, so I cooked
>
For each port that is in PHY mode we obtain a PHY device using the USB PHY
library and put it out of suspend.
It is up to platform code to associate the PHY to the controller's
port and it is upto the PHY driver to manage the PHY's resources.
Also remove wired spacing around declarations we come
'max77693_extcon_cable' is used only in this file. Hence
make it static.
Signed-off-by: Sachin Kamat
---
drivers/extcon/extcon-max77693.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/extcon/extcon-max77693.c b/drivers/extcon/extcon-max77693.c
index
'break' after 'return' is never executed and hence can be deleted.
Signed-off-by: Sachin Kamat
---
drivers/extcon/extcon-max8997.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/extcon/extcon-max8997.c b/drivers/extcon/extcon-max8997.c
index 7039541..d16090d
Commit-ID: 5dcd14ecd41ea2b3ae3295a9b30d98769d52165f
Gitweb: http://git.kernel.org/tip/5dcd14ecd41ea2b3ae3295a9b30d98769d52165f
Author: H. Peter Anvin
AuthorDate: Tue, 29 Jan 2013 01:05:24 -0800
Committer: H. Peter Anvin
CommitDate: Tue, 29 Jan 2013 01:22:17 -0800
x86, boot: Sanitize
'max8997_extcon_cable' is used only in this file. Hence make it static.
Signed-off-by: Sachin Kamat
---
drivers/extcon/extcon-max8997.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/extcon/extcon-max8997.c b/drivers/extcon/extcon-max8997.c
index
On Tuesday, January 29, 2013 03:10:38 AM Yinghai Lu wrote:
> On Mon, Jan 28, 2013 at 5:11 PM, H. Peter Anvin wrote:
> >> So I guess the final patch should be:
> >>- Add a new e820 type:
> >> E820_KDUMP_RESERVED /* Originally usable memory where the crashed
> >>
Hi Paul,
On Fri, Jan 25, 2013 at 17:48:22, Mohammed, Afzal wrote:
> On Fri, Jan 25, 2013 at 13:48:11, Paul Walmsley wrote:
> > like MPU CPUFreq. I'd suggest reverting
> > 241d3a8dca239610d3d991bf58d4fe38c2d86fd5 or using a similar approach.
> As you prefer reverting the above commit, I will
Daniele Palmas writes:
> 2013/1/28 Bjørn Mork :
>
>> Thanks for adding this device. But the patch doesn't apply to the
>> current "net" tree. Care to rebase it?
>>
>
> Sure. Should I use the following git repository
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/net-next.git
>
> ?
No,
On Thu, Jan 24, 2013 at 01:25:46PM +0200, Jussi Kivilinna wrote:
>
> Maybe it would be cleaner to not mess with pfkeyv2.h at all, but instead mark
> algorithms that do not support pfkey with flag. See patch below.
>
As nobody seems to have another opinion, we could go either with your
> From: Libo Chen
>
> On 2013-1-29 4:23, Kirill Tkhai wrote:
>
>> Just switched pinned task is not able to be pushed. If the rq had had
>> several RT tasks before they have already been considered as candidates
>> to be pushed (or pulled).
>>
>> Signed-off-by: Kirill V Tkhai
>> CC: Steven
* nan chen wrote:
> > #define spin_lock_mutex(lock, flags)\
> > do {\
> > struct mutex *l = container_of(lock, struct mutex,
> > wait_lock); \
> > \
>
On Tue, Jan 29, Jan Beulich wrote:
> >>> On 28.01.13 at 18:44, Stefano Stabellini
> >>> wrote:
> > I think that Olaf made his point very clear: a feature A should only be
> > enabled if the corresponding flag A is set.
> > In fact it seems to me that this patch is correct on its own merits,
> >
Hi Fabio, Samuel,
> This patch adds support for the ux500_wdt watchdog that is found in
> ST-Ericsson Ux500 platform. The driver is based on PRCMU APIs.
>
> Acked-by: Linus Walleij
> Acked-by: Lee Jones
> Signed-off-by: Fabio Baltieri
Acked-by: Wim Van Sebroeck
Kind regards,
Wim.
--
To
Hello Emmanuel,
On Tue, Jan 29, 2013 at 8:16 AM, Grumbach, Emmanuel
wrote:
> Please try this one:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=c3e5d7181afb66657393066bccce0956fab09ab3
>
> as you can see, it is in mainline already.
Ha, that was fast! I'll check
* Yuanhan Liu wrote:
> On Tue, Jan 29, 2013 at 09:44:00AM +0100, Ingo Molnar wrote:
> >
> > * Yuanhan Liu wrote:
> >
> > > [...]
> >
> > Very nice measurements and analysis, thanks!
> >
> > > As stated above, anybody can have a chance to own the lock in
> > > mutex once somebody release
Since schedule balance map provide the approach to get proper sd directly,
simplify the code of select_task_rq_fair() is possible.
The new code is designed to reserve most of the old logical, but get rid
of those 'for' by using the schedule balance map to locate proper sd
directly.
In order to get rid of the complex code in select_task_rq_fair(),
approach to directly get sd on each level with proper flag is
required.
Schedule balance map is the solution, which record the sd according
to it's flag and level.
For example, cpu_sbm->sd[wake][l] will locate the sd of cpu which
This patch will build schedule balance map as designed, now
cpu_sbm->sd[f][l] can directly locate the sd of cpu on level 'l'
with flag 'f' supported.
In order to quickly locate the lower sd while changing the base cpu,
the level with empty sd in map will be filled with the lower sd.
Commit-ID: 2b9b6d8c715b23fa119261c32ad360681f4464a9
Gitweb: http://git.kernel.org/tip/2b9b6d8c715b23fa119261c32ad360681f4464a9
Author: David Woodhouse
AuthorDate: Mon, 28 Jan 2013 17:49:50 +
Committer: H. Peter Anvin
CommitDate: Mon, 28 Jan 2013 16:59:55 -0800
x86: Require MOVBE
Add device tree support for the TI PMIC TPS65090.
The device can be registered through platform or DT.
Add device tree binding document for this device.
Signed-off-by: Laxman Dewangan
---
Changes from V1:
- Remove non-required code from the change for checking the match.
- Remove pdata
v3 change log:
Fix small logical issues (Thanks to Mike Galbraith).
Change the way of handling WAKE.
This patch set is trying to simplify the select_task_rq_fair() with
schedule balance map.
After get rid of the complex code and reorganize the logical, pgbench show
the
The tps65090 mfd driver implement the suspend/resume callbacks
which just disable and enable irqs in suspend/resume respectively.
This operation is already done in irq suspend and irq_resume and
hence it is not require to implement the same in the driver.
Remove this non-require code.
When device is get added through DT then irq_base is 0 (zero)
and in this case regmap_irq_chip_get_base() generates warning.
The interrupt of this device get added through irq_domain_add_linear()
when irq_base is 0.
Hence pass the irq domain in place of base_irq when calling
mfd_add_devices().
Add DT support for TI PMIC tps65090 regulator driver. The DT of this
device have node regulator and all regulator's node of this device is
added under this node.
The device tree binding document has the required information for
adding this device on DTS file.
Signed-off-by: Laxman Dewangan
---
The patch series add DT support on TPS65090 device.
Also remove the suspend/resume implementation as it duplicates with
irq_suspend/irq_resume().
Changes from V1:
- Remove non-required code from the change for checking the match.
- Remove pdata allocation on mfd driver.
- renames some of the
* Joerg Roedel wrote:
> Hi Ingo,
>
> On Fri, Jan 25, 2013 at 11:49:15AM +0100, Ingo Molnar wrote:
> > Hm, there are some not so trivial looking conflicts in
> > io_apic.c, due to the MSI patches I applied yesterday:
> >
> > 5ca72c4f7c41 AHCI: Support multiple MSIs
> > 08261d87f7d1 PCI/MSI:
Commit-ID: 83a57a4de1a222c351667ef9a0fedaac1295e85b
Gitweb: http://git.kernel.org/tip/83a57a4de1a222c351667ef9a0fedaac1295e85b
Author: David Woodhouse
AuthorDate: Thu, 20 Dec 2012 01:16:20 +
Committer: H. Peter Anvin
CommitDate: Mon, 28 Jan 2013 08:48:57 -0800
x86: Enable
On Tue, Jan 29, 2013 at 09:44:00AM +0100, Ingo Molnar wrote:
>
> * Yuanhan Liu wrote:
>
> > [...]
>
> Very nice measurements and analysis, thanks!
>
> > As stated above, anybody can have a chance to own the lock in
> > mutex once somebody release the lock. Well, there is only one
> > to own
* nan chen wrote:
> 2013/1/25 Ingo Molnar
>
> >
> > * nan chen wrote:
> >
> > > 2013/1/25 Ingo Molnar
> > >
> > > >
> > > > * Andrew Morton wrote:
> > > >
> > > > > On Thu, 24 Jan 2013 17:22:45 +0800
> > > > > Yuanhan Liu wrote:
> > > > >
> > > > > > Use spin_[un]lock instead of
This patch adds support for the ux500_wdt watchdog that is found in
ST-Ericsson Ux500 platform. The driver is based on PRCMU APIs.
Acked-by: Linus Walleij
Acked-by: Lee Jones
Signed-off-by: Fabio Baltieri
---
Changes from v1:
- changed timeout as unsigned in both module parameter and pdata
-
This change fixes a deadlock when the multiplexer is closed while there
are still client side ports open.
When the multiplexer is closed and there are active tty's it tries to
close them with tty_vhangup. This has a problem though, because
tty_vhangup needs the tty_lock. This patch changes it to
601 - 700 of 1454 matches
Mail list logo
