On 29.05.2013 09:08, Eric Dumazet wrote:
On Tue, 2013-05-28 at 18:31 -0700, Paul E. McKenney wrote:
On Tue, May 28, 2013 at 05:34:53PM -0700, Eric Dumazet wrote:
On Tue, 2013-05-28 at 13:10 +0400, Roman Gushchin wrote:
On 28.05.2013 04:12, Eric Dumazet wrote:
About your earlier question, I
> > > So, if I apply this series, I do see the PCIe bridge and Ethernet
> > > device get enumerated, but I don't see the USB3 controller get
> > > enumerated. I believe that is a PCIe device behind the same bridge
> > > on the
> > same Tegra PCIe port.
> > > Shouldn't this device show up?
> > I hav
On Tue, May 28, 2013 at 10:33 AM, Stephane Eranian wrote:
> On Mon, May 27, 2013 at 3:12 PM, Peter Zijlstra wrote:
>>
>>
>> I already queued your v6, however Ingo was ill last week so it didn't
>> get merged. It says nothing changed, so I left whatever I had in my
>> queue.
>>
> Thanks.
>> Please
Hi Jean,
Le 24/05/2013 14:20, Jean Delvare a écrit :
> On Fri, 24 May 2013 11:52:54 +0200, Mylene Josserand wrote:
>> - an audio codec tlv320aic3204 : There is a driver for this device but
>> for some reasons, we did not use it. Did not find a "SMBus compliant" in
>> its datasheet.
>
> The tlv320a
On Mon, May 27, 2013 at 07:09:00PM +0200, Andrew Jones wrote:
> Commit 316ad248307fb ("sched/x86: Rewrite set_cpu_sibling_map()") broke
> the construction of sibling maps, which also broke the booted_cores
> accounting.
>
> Before the rewrite, if smt was present, then each map was updated for
> ea
From: Terje Bergstrom
The firewall was reinitialised for each gather. Because the filter
was reinitialised, it did not track the class over gather boundaries.
This allowed the user application to set host1x class to one class
in one gather and use that class in another gather without firewall
hav
client_managed field in syncpoint structure was defined as an
integer. The field holds, however, only a boolean value. This patch
modifies the type to boolean.
Signed-off-by: Arto Merilainen
---
drivers/gpu/host1x/drm/gr2d.c | 2 +-
drivers/gpu/host1x/syncpt.c | 8
drivers/gpu/host1x/
This patch merges host1x_syncpt_cpu_incr to host1x_syncpt_incr() as
they are in practise doing the same thing. host1x_syncpt_incr() is
also modified to return error codes. User space interface is modified
accordingly to pass return values.
Signed-off-by: Arto Merilainen
---
drivers/gpu/host1x/de
This patch fixes a bad memory access in syncpoint request code. If
no syncpoints were available, the code accessed unreserved memory
area causing unexpected behaviour.
Signed-off-by: Arto Merilainen
---
drivers/gpu/host1x/syncpt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --g
The firewall verified gather buffers before copying them. This
allowed a malicious application to rewrite the buffer content by
timing the rewrite carefully.
This patch makes the buffer validation occur after copying the
buffers.
Signed-off-by: Arto Merilainen
Signed-off-by: Terje Bergstrom
---
The firewall assumed that the user space always delivers a relocation
table when it is accessing address registers. If userspace did not
deliver a relocation table and tried to access the address registers,
the code performed bad memory accesses.
This patch modifies the firewall to check correctly
This patch series fixes two issues in the host1x driver: First, the
command buffer validation routine had vulnerabilities that were not
detected in earlier testing. Second, the return codes of some
functions were misleading or completely missing. This caused the
driver to give wrong return codes al
From: Terje Bergstrom
The firewall code used a wrong loop condition (pointer to a
structure) while checking INCR opcode. This patch fixes the code to
use correct loop condition (number of words remaining).
Signed-off-by: Terje Bergstrom
Signed-off-by: Arto Merilainen
---
drivers/gpu/host1x/jo
To reduce cpufreq maintenance load on Rafael, ARM specific patches would be
Applied by me now. Rafael will pull in these changes from time to time (at
rc's). Additionally I would be sending him pull request for every merge window
and rc's (for fixes).
Web interface of my tree is present here:
htt
On Wed, 2013-05-29 at 16:10 +0530, Viresh Kumar wrote:
> ARM specific patches would be
> Applied by me now. Rafael will pull in these changes from time to time (at
> rc's).
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -2216,6 +2216,7 @@ L: cpuf...@vger.kernel.org
[]
> T: git://git.ke
When sending message in send_secondary_console_msg(), the length is not
include the NUL byte, and also not copy NUL to 'ipc_buffer'.
When receive message in recv_secondary_console_msg(), the 'cnt' also
excludes NUL.
So when get string from ipc_buffer, it may not be NUL terminated.
Then use memc
On 29 May 2013 16:17, Joe Perches wrote:
> On Wed, 2013-05-29 at 16:10 +0530, Viresh Kumar wrote:
>> ARM specific patches would be
>> Applied by me now. Rafael will pull in these changes from time to time (at
>> rc's).
> []
>> diff --git a/MAINTAINERS b/MAINTAINERS
> []
>> @@ -2216,6 +2216,7 @@ L:
On Monday 27 May 2013 05:44 PM, Andy Shevchenko wrote:
Accordingly to dma_cookie_status() description locking is not required.
I think we need lock here:
From isr handler, we call dma_cookie_complete() which is in
spin-locked. This function updates tx->chan->completed_cookie = tx->cookie;
In
On Wed, 29 May 2013, Stephen Rothwell wrote:
> Hi Stefano,
>
> After merging the xen-arm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> kernel/sched/cputime.c:8:26: fatal error: asm/paravirt.h: No such file or
> directory
> #include
>
I don't think anyone really has an issue with things like max_mV.
And whilst nS et al. may not be SI standard, at least it's clear
what they represent.
Signed-off-by: Phil Carmody
---
scripts/checkpatch.pl |1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/checkpatch.pl b/scripts/che
Peter et. al,
I am coming again with this series, hoping this is a better time for you all to
look at it.
I am *not* going as far as marking cpuacct deprecated, because I think it
deserves a special discussion (even though my position in this matter is widely
known), but all the infrastructure to
Commit 8f618968 changed stop_task to do the same bookkeping as the
other classes. However, the call to cpuacct_charge() doesn't affect
the scheduler decisions at all, and doesn't need to be moved over.
Moreover, being a kthread, the migration thread won't belong to any
cgroup anyway, rendering thi
The CPU cgroup is so far, undocumented. Although data exists in the
Documentation directory about its functioning, it is usually spread,
and/or presented in the context of something else. This file
consolidates all cgroup-related information about it.
Signed-off-by: Glauber Costa
---
Documentati
We already track multiple tick statistics per-cgroup, using
the task_group_account_field facility. This patch accounts
guest_time in that manner as well.
Signed-off-by: Glauber Costa
CC: Peter Zijlstra
CC: Paul Turner
---
kernel/sched/cputime.c | 10 --
1 file changed, 4 insertions(+),
From: Peter Zijlstra
In order to avoid having to do put/set on a whole cgroup hierarchy
when we context switch, push the put into pick_next_task() so that
both operations are in the same function. Further changes then allow
us to possibly optimize away redundant work.
[ glom...@openvz.org: incor
On Tue, 28 May 2013, Konrad Rzeszutek Wilk wrote:
> On Tue, May 28, 2013 at 06:54:29PM +0100, Stefano Stabellini wrote:
> > Signed-off-by: Stefano Stabellini
> > Acked-by: Ian Campbell
> > CC: konrad.w...@oracle.com
> >
> > Changes in v2:
> > - leave do_stolen_accounting in arch/x86/xen/time.c;
This patch changes the calculation of nr_context_switches. The variable
"nr_switches" is now used to account for the number of transition to the
idle task, or stop task. It is removed from the schedule() path.
The total calculation can be made using the fact that the transitions to
fair and rt cla
The file cpu.stat_percpu will show various scheduler related
information, that are usually available to the top level through other
files.
For instance, most of the meaningful data in /proc/stat is presented
here. Given this file, a container can easily construct a local copy of
/proc/stat for int
Context switches are, to this moment, a property of the runqueue. When
running containers, we would like to be able to present a separate
figure for each container (or cgroup, in this context).
The chosen way to accomplish this is to increment a per cfs_rq or
rt_rq, depending on the task, for each
For sending message:
*(unsigned int *)&cpu->ipc_buffer[0] = len;
cp1 = (char *) &cpu->ipc_buffer[1];
But for receive message:
cnt = cpu->ipc_buffer[0] >> 32;
...
cp1 = (char *) &cpu->ipc_buffer[11];
They are not pairs, it i
exec_clock already provides per-group cpu usage metrics, and can be
reused by cpuacct in case cpu and cpuacct are comounted.
However, it is only provided by tasks in fair class. Doing the same for
rt is easy, and can be done in an already existing hierarchy loop. This
is an improvement over the in
On Wed, May 29, 2013 at 12:26:01PM +0200, Andrew Jones wrote:
> On Mon, May 27, 2013 at 07:09:00PM +0200, Andrew Jones wrote:
> > Commit 316ad248307fb ("sched/x86: Rewrite set_cpu_sibling_map()") broke
> > the construction of sibling maps, which also broke the booted_cores
> > accounting.
> >
> >
On Tue, May 28, 2013 at 06:43:07PM -0500, Jacob Shin wrote:
> > Anyway, this whole Kconfig microcode section could use a simplification
> > but this is not the subject of this patchset - I'll try to address it
> > after this, as stated in another mail.
>
> Yes, I'll simplify the Kconfig as you sug
Hanjun Guo wrote:
> On 2013-5-29 7:30, Rafael J. Wysocki wrote:
>> On Thursday, May 23, 2013 08:44:26 PM Hanjun Guo wrote:
>>> In acpi_processor_add(), get_cpu_device() will return NULL sometimes,
>>> although the chances are small, I think it should be fixed.
>>>
>>> Signed-off-by: Hanjun Guo
>>
From: Tejun Heo
cpuacct being on a separate hierarchy is one of the main cgroup
related complaints from scheduler side and the consensus seems to be
* Allowing cpuacct to be a separate controller was a mistake. In
general multiple controllers on the same type of resource should be
avoided,
All the information we have that is needed for cpuusage (and
cpuusage_percpu) is present in schedstats. It is already recorded
in a sane hierarchical way.
If we have CONFIG_SCHEDSTATS, we don't really need to do any extra
work. All former functions become empty inlines.
Signed-off-by: Glauber Cos
From: Tejun Heo
When cgroup files are created, cgroup core automatically prepends the
name of the subsystem as prefix. This patch adds CFTYPE_NO_PREFIX
which disables the automatic prefix.
This will be used to deprecate cpuacct which will make cpu create and
serve the cpuacct files.
Signed-off
* Peter Zijlstra wrote:
> On Wed, May 29, 2013 at 12:26:01PM +0200, Andrew Jones wrote:
> > On Mon, May 27, 2013 at 07:09:00PM +0200, Andrew Jones wrote:
> > > Commit 316ad248307fb ("sched/x86: Rewrite set_cpu_sibling_map()") broke
> > > the construction of sibling maps, which also broke the boo
On Tue, May 28, 2013 at 03:30:35PM -0400, Sasha Levin wrote:
> On 05/22/2013 05:17 AM, Peter Zijlstra wrote:
> > On Wed, May 15, 2013 at 11:15:34PM -0400, Sasha Levin wrote:
> >> --- /dev/null
> >> +++ b/tools/lib/lockdep/uinclude/linux/lockdep.h
> >> @@ -0,0 +1,55 @@
> >> +#ifndef _LIBLOCKDEP_LOCK
On Tue, May 28, 2013 at 03:33:51PM -0400, Sasha Levin wrote:
> On 05/22/2013 05:22 AM, Peter Zijlstra wrote:
> > They will however then also want all the 'normal' lockdep annotations to
> > deal with that like:
> >
> > liblockdep_pthread_mutex_lock_nested()
> > liblockdep_pthread_mutex_lock_nest_l
On Tue, May 28, 2013 at 03:35:36PM -0400, Sasha Levin wrote:
> On 05/22/2013 05:24 AM, Peter Zijlstra wrote:
> > Do we still need this with the glibc __pthread_* static initialization?
>
> Sadly we do.
>
> We need to deal with the two things that cause allocation in our code (because
> they loop
On Tue, May 28, 2013 at 03:38:38PM -0400, Sasha Levin wrote:
> On 05/22/2013 05:27 AM, Peter Zijlstra wrote:
> > I guess that begs the question do we really want to support !glibc?
>
> I assumed we didn't want to give up on that based on your patch. I think that
> if we plan to get it into tools/l
On Tuesday, May 28, 2013 08:46:11 PM Yinghai Lu wrote:
> On Tue, May 28, 2013 at 5:30 PM, Rafael J. Wysocki wrote:
> > On Tuesday, May 28, 2013 05:01:41 PM Yinghai Lu wrote:
> >
> > Please attach your .config for comparison and maybe Greg will have an idea
> > about what's up with udev vs that co
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy
---
v7 - Update headli
On Wed, 2013-05-29 at 14:02 +0300, Phil Carmody wrote:
> I don't think anyone really has an issue with things like max_mV.
> And whilst nS et al. may not be SI standard, at least it's clear
> what they represent.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -2940,6 +2940,
On Tue, May 28, 2013 at 12:17:28PM -0500, Suravee Suthikulanit wrote:
> On 5/28/2013 7:18 AM, Joerg Roedel wrote:
> >That implementation is very basic. Any reason for not using the event
> >reporting mechanism of the IOMMU? You could implement a nice perf
> >iommutop or something to see which devi
On Wed, May 29, 2013 at 01:26:01PM +0300, Arto Merilainen wrote:
> This patch series fixes two issues in the host1x driver: First, the
> command buffer validation routine had vulnerabilities that were not
> detected in earlier testing. Second, the return codes of some
> functions were misleading or
Supporting the second channel in the driver.
Offset is 0x8 and both channnels share the same
IRQ.
Signed-off-by: Michal Simek
---
drivers/gpio/gpio-xilinx.c | 93 --
1 file changed, 81 insertions(+), 12 deletions(-)
diff --git a/drivers/gpio/gpio-xili
Describe gpio-xilinx binding.
Signed-off-by: Michal Simek
---
.../devicetree/bindings/gpio/gpio-xilinx.txt | 43 ++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xilinx.txt
diff --git a/Documentation/devicetree/binding
Hi Hans,
any comment on this?
Thanks,
Michal
On 05/23/2013 04:01 PM, Michal Simek wrote:
> - Remove Userspace I/O platform driver without IRQ support
> but add this functionality to genirq driver
> - Remove code duplication from OF binding
>
> Signed-off-by: Michal Simek
> ---
> The main rea
On Wed, May 29, 2013 at 12:07 PM, Chen Gang wrote:
> The 'name' length in decode_address() may be 255, after call d_path()
> successfully.
>
> So for decode_address(), the input 'buf' need be more than 256, or may
> memory overflow.
>
> For simply thinking of, use 'namebuf[512]' instead of 'namebu
On 05/29/2013 02:21 PM, Thierry Reding wrote:
* PGP Signed by an unknown key
* Arto Merilainen wrote:
[...]
diff --git a/drivers/gpu/host1x/job.c b/drivers/gpu/host1x/job.c
[...]
@@ -553,7 +549,6 @@ int host1x_job_pin(struct host1x_job *job, struct device
*dev)
if (!err)
Hi,
Improve Kconfig so that the relevant PHY driver can be explicitely
selected by the controller driver instead of relying on the user
to do so.
Detailed description in patch 1.
cheers,
-roger
Roger Quadros (5):
USB: PHY: Make PHY driver selection possible by controller drivers
USB: ehci-o
Convert PHY Drivers from menuconfig to menu so that the PHY drivers
can be explicitely selected by the controller drivers.
USB_PHY is no longer a user visible option. It is upto to the PHY
drivers to select it if needed. This patch does so for the existing
PHY drivers that use the USB_PHY library.
ehci-omap needs NOP_USB_XCEIV PHY driver to function
properly, so select it. As the USB PHY drivers no longer
depend on USB_PHY, it is safe to select the PHY drivers.
Signed-off-by: Roger Quadros
---
drivers/usb/host/Kconfig |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --g
As the USB PHY drivers no longer depend on USB_PHY but
select it if needed, the controller drivers need not
depend on USB_PHY. They can safely select the necessary
PHY driver i.e. USB_MSM_OTG in this case.
Signed-off-by: Roger Quadros
CC: Pavankumar Kondeti
---
drivers/usb/host/Kconfig |1 -
As the USB PHY drivers no longer depend on USB_PHY but
select it if needed, the controller drivers need not
depend on USB_PHY. They can safely select the necessary
PHY driver i.e. USB_ISP1301 in this case.
Signed-off-by: Roger Quadros
CC: Roland Stigge
---
drivers/usb/gadget/Kconfig |1 -
1
As the USB PHY drivers no longer depend on USB_PHY but
select it if needed, the controller drivers need not
depend on USB_PHY. They can safely select the necessary
PHY driver i.e. ISP1301_OMAP in this case.
Signed-off-by: Roger Quadros
---
drivers/usb/gadget/Kconfig |1 -
1 files changed, 0
From: Nikolay Balandin
Use devm_regulator_bulk_get to make cleanup paths simpler
Signed-off-by: Nikolay Balandin
---
drivers/misc/lis3lv02d/lis3lv02d_i2c.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/misc/lis3lv02d/lis3lv02d_i2c.c
b/drivers/misc/lis
On 05/29/2013 01:22 AM, Dan Carpenter wrote:
> I introduced a new temporary variable "info" instead of
> "m->m_info[mds]". Also I reversed the if condition and pulled
> everything in one indent level.
Looks good. I will apply this for you.
Reviewed-by: Alex Elder
>
> Signed-off-by: Dan Carpe
On Tue, 28 May 2013 09:55:01 -0400
Vivek Goyal wrote:
> On Sat, May 25, 2013 at 02:52:17PM +0200, Michael Holzheu wrote:
[snip]
> > Besides of the newmem mechanism, for completeness, we also
> > implemented the oldmem ELF header mechansim in kexec. But this is
> > disabled by default.
> >
> >
On Mon, May 27, 2013 at 11:27:35PM +0800, Runzhen Wang wrote:
> commit 0a720538e5dd3f424bfcc15c1e4af09df0becf92
> and
> commit 93cbb3985d5de867fb32e6e130fcfb1b5de4142b
> move some contents of Makefile from perf/Makefile to
> perf/config/Makefile.
hi,
so you based on latest acme's perf/core, right?
On Tue, May 28, 2013 at 6:27 PM, Felipe Balbi wrote:
> On Wed, May 15, 2013 at 07:18:01PM +0200, Linus Walleij wrote:
>> I can't merge any of this without Felipes ACKs in any
>> case.
>
> Do you want to take this yourself ? I haven't fully read the series yet,
> but seems like this depends on the
On Wednesday 29 May 2013 14:43:26 Roger Quadros wrote:
>
> Improve Kconfig so that the relevant PHY driver can be explicitely
> selected by the controller driver instead of relying on the user
> to do so.
>
> Detailed description in patch 1.
I think you have to fold patches 3-5 into patch 1, oth
* Arto Merilainen wrote:
[...]
> diff --git a/drivers/gpu/host1x/job.c b/drivers/gpu/host1x/job.c
[...]
> @@ -553,7 +549,6 @@ int host1x_job_pin(struct host1x_job *job, struct device
> *dev)
>
> if (!err)
> err = do_waitchks(job, host, g->bo);
> -
>
On 05/29/2013 11:01 AM, Olof Johansson wrote:
>> There are a total of 6 patches on top of
>> v3.10-rc3. 3 of them (a, b, d) are queued for 3.10-rc4 and another patch
>> (c) is just a defconfig hack to get Arndale booting. Remaining 2 patches
>> (e, f) are required to reset the hub during EHCI initi
On 05/29/2013 02:59 PM, Arnd Bergmann wrote:
> On Wednesday 29 May 2013 14:43:26 Roger Quadros wrote:
>>
>> Improve Kconfig so that the relevant PHY driver can be explicitely
>> selected by the controller driver instead of relying on the user
>> to do so.
>>
>> Detailed description in patch 1.
>
>
On 05/29/2013 07:30 PM, Geert Uytterhoeven wrote:
>> void show_regs(struct pt_regs *fp)
>> > {
>> > - char buf[150];
>> > + char buf[512];
> This will increase stack usage a lot. And this function calls
> decode_address(),
> which allocates another buffer on the stack.
>
Can it hav
On 29/05/13 01:18, John Stultz wrote:
> On 05/13/2013 10:56 AM, David Vrabel wrote:
>> From: David Vrabel
>>
>> All the virtualized platforms (KVM, lguest and Xen) have persistent
>> wallclocks that have more than one second of precision.
>>
>> read_persistent_wallclock() and update_persistent_wal
On 03/06/2013 08:56 PM, Matt Porter wrote:
> Add a dmaengine API to retrieve slave SG transfer limits.
>
> The API is optionally implemented by dmaengine drivers and when
> unimplemented will return a NULL pointer. A client driver using
> this API provides the required dma channel, address width,
On Fri, May 24, 2013 at 1:50 PM, Christian Ruppert
wrote:
> I haven't understood how to associate GPIOs to
> other functions, however: Our hardware pin controller makes GPIO pins
> available depending on the configuration of the non-GPIO interfaces.
> This means that in many configurations, GPIO
The vsyscall related pvclock entries can only ever be used on x86-64,
and hence they shouldn't even get allocated for 32-bit kernels (the
more that it is there where address space is relatively precious).
Signed-off-by: Jan Beulich
Cc: Marcelo Tosatti
---
arch/x86/include/asm/fixmap.h |2 +
On Mon, 2013-05-27 at 10:10 +0200, Richard Weinberger wrote:
> Hi!
>
> Am 27.05.2013 10:02, schrieb Thomas Weber:
> > Signed-off-by: wang bo
> >
> > [fix whitespace errors]
> >
> > Tested with linux-v3.10-rc3 on Devkit8000.
> > Signed-off-by: Thomas Weber
> >
> > The discussion about this patch
Am 29.05.2013 14:27, schrieb Artem Bityutskiy:
On Mon, 2013-05-27 at 10:10 +0200, Richard Weinberger wrote:
Hi!
Am 27.05.2013 10:02, schrieb Thomas Weber:
Signed-off-by: wang bo
[fix whitespace errors]
Tested with linux-v3.10-rc3 on Devkit8000.
Signed-off-by: Thomas Weber
The discussion a
It being static causes over a dozen instances to be scattered across
the kernel image, with non of them ever being referenced in any way.
Making the variable extern without ever defining it works as well - all
we need is to have the compiler think the variable is being accessed.
Signed-off-by: Jan
Signed-off-by: Jan Beulich
---
drivers/xen/xen-pciback/pci_stub.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- 3.10-rc3/drivers/xen/xen-pciback/pci_stub.c
+++ 3.10-rc3-xen-pciback-MSI-X-cap/drivers/xen/xen-pciback/pci_stub.c
@@ -106,7 +106,7 @@ static void pcistub_device_rel
On 05/28, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > proc_task_readdir() verifies that the result of get_proc_task()
> > is pid_alive() and thus its ->group_leader is fine too. However
> > this is not necessarily true after rcu_read_unlock(), we need
> > to recheck this after first_t
On Thu, 2013-05-02 at 15:56 +0200, Laurent Navet wrote:
> Replace a call to deprecated devm_request_and_ioremap by
> devm_ioremap_resource.
>
> Found with coccicheck and this semantic patch:
> scripts/coccinelle/api/devm_request_and_ioremap.cocci.
>
> Signed-off-by: Laurent Navet
Pushed to l2
On Thu, 2013-05-02 at 17:09 +0200, Laurent Navet wrote:
> Replace a call to deprecated devm_request_and_ioremap by
> devm_ioremap_resource.
>
> Found with coccicheck and this semantic patch:
> scripts/coccinelle/api/devm_request_and_ioremap.cocci.
>
> Signed-off-by: Laurent Navet
We already h
On Tue, May 28, 2013 at 11:02:09PM +0800, Xiao Guangrong wrote:
> On 05/28/2013 08:18 AM, Marcelo Tosatti wrote:
> > On Mon, May 27, 2013 at 10:20:12AM +0800, Xiao Guangrong wrote:
> >> On 05/25/2013 04:34 AM, Marcelo Tosatti wrote:
> >>> On Thu, May 23, 2013 at 03:55:53AM +0800, Xiao Guangrong wro
On Wed, May 29, 2013 at 11:03:19AM +0800, Xiao Guangrong wrote:
> >>> the pages since other vcpus may be doing locklessly shadow
> >>> page walking
> >
> > Ah, yes, i agree with you.
> >
> > We can introduce a list, say kvm->arch.obsolte_pages, to link all of the
> > zapped-page, the page-shrink
On Tue, May 28, 2013 at 10:51:38PM +0800, Xiao Guangrong wrote:
> On 05/28/2013 08:13 AM, Marcelo Tosatti wrote:
> > On Thu, May 23, 2013 at 03:55:58AM +0800, Xiao Guangrong wrote:
> >> It is only used to zap the obsolete page. Since the obsolete page
> >> will not be used, we need not spend time t
binutils prior to 2.18 (e.g. the ones found on SLE10) don't support
assembling PEXTRD, so a macro based approach like the one for PCLMULQDQ
in the same file should be used.
This requires making the helper macros capable of recognizing 32-bit
general purpose register operands.
Signed-off-by: Jan B
On Sun, May 19, 2013 at 10:51:45AM -0700, Kent Overstreet wrote:
> Sorry for the delay - been vacationing. Reproduced the original bug,
> here's a patch that fixes it:
>
>
> commit 402f5db3708b2062795a384a3d8397cf702e27bc
> Author: Kent Overstreet
> Date: Sun May 19 10:27:07 2013 -0700
>
>
On Wednesday 29 May 2013, Daniel Tang wrote:
> On 27/05/2013, at 8:31 PM, Arnd Bergmann wrote:
>
> > On Monday 27 May 2013, Daniel Tang wrote:
> >>> The one remaining bit that sticks out is the clcd platform data. As I
> >>> said before, I won't require you to convert that to DT in order to
> >>>
Commit 316ad248307fb ("sched/x86: Rewrite set_cpu_sibling_map()") broke
the construction of sibling maps, which also broke the booted_cores
accounting.
Before the rewrite, if smt was present, then each map was updated for
each smt sibling. After the rewrite only cpu_sibling_mask gets updated,
as t
zap_pte_range loops from @addr to @end. In the middle, if it runs out of
batching slots, TLB entries needs to be flushed for @start to @interim,
NOT @interim to @end.
Since ARC port doesn't use page free batching I can't test it myself but
this seems like the right thing to do.
Observed this when
On Wed, 2013-05-29 at 09:39 +0300, Eliezer Tamir wrote:
> Adds a napi_id and a hashing mechanism to lookup a napi by id.
> This will be used by subsequent patches to implement low latency
> Ethernet device polling.
> Based on a code sample by Eric Dumazet.
>
> Signed-off-by: Eliezer Tamir
> ---
On Wed, May 29 2013, Richard W.M. Jones wrote:
>
> On Sun, May 19, 2013 at 10:51:45AM -0700, Kent Overstreet wrote:
> > Sorry for the delay - been vacationing. Reproduced the original bug,
> > here's a patch that fixes it:
> >
> >
> > commit 402f5db3708b2062795a384a3d8397cf702e27bc
> > Author: K
On Mon 27-05-13 19:13:08, Michal Hocko wrote:
[...]
> Nevertheless I have encountered an issue while testing the huge number
> of groups scenario. And the issue is not limitted to only to this
> scenario unfortunately. As memcg iterators use per node-zone-priority
> cache to prevent from over recla
On Wed 29 May 2013 04:41:30 PM CST, Vineet Gupta wrote:
> Hi Jiang,
>
> On 05/08/2013 09:21 PM, Jiang Liu wrote:
>> Prepare for removing num_physpages and simplify mem_init().
>>
>> Signed-off-by: Jiang Liu
>> Cc: Vineet Gupta
>> Cc: James Hogan
>> Cc: Rob Herring
>> Cc: linux-kernel@vger.kerne
Added musb_restart() API, used for restart of the musb controller by
the glue layer, when there is babble condition occured on the bus.
During babble condition, the musb controller will remove the session
and no longer in host-mode. As part of recovery this API can be used
to restart the musb cont
Adding babble recovery mechanism for dsps platform and as part
of babble recovery the controller will be restarted.
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c | 34 +-
1 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/mus
Adding babble_recovery operation as part of musb->ops, used
to recover from babble condition during babble interrupt.
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_core.c |6 ++
drivers/usb/musb/musb_core.h |7 +++
2 files changed, 13 insertions(+), 0 deletions(-)
diff --gi
During the babble condition on usb bus, the musb controller removes the
session and stops host mode functionality. All the devices connected
to root port will be disconnected due to this babble event.
As part of recovery of babble bus condition, restarting the
controller is needed as all
On 05/29/2013 07:11 PM, Marcelo Tosatti wrote:
> On Tue, May 28, 2013 at 11:02:09PM +0800, Xiao Guangrong wrote:
>> On 05/28/2013 08:18 AM, Marcelo Tosatti wrote:
>>> On Mon, May 27, 2013 at 10:20:12AM +0800, Xiao Guangrong wrote:
On 05/25/2013 04:34 AM, Marcelo Tosatti wrote:
> On Thu, Ma
> > Adds a napi_id and a hashing mechanism to lookup a napi by id.
Is this one of the places where the 'id' can be selected
so that the 'hash' lookup never collides?
David
N�r��yb�X��ǧv�^�){.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~i���z��w���?�&�)ߢf��^j
Hi Max,
This patch - acked by you then, got lost in the mist of time. Care to take it in
via xtensa tree for 3.11
Thx,
-Vineet
Original Message
Subject: [PATCH 2/2] xtensa: Flat DeviceTree copy not future-safe
Date: Fri, 22 Feb 2013 00:09:22 +0530
From: Vineet Gupta
To: Andre
On Wed, 29 May 2013, Peter Zijlstra wrote:
> Hurm.. I don't suppose you have an easy reproducer handy eh? I'll go
> stare at it. At least the current state is better than before, but
> clearly we're not quite there yet.
I've been working on a reproducible test case. Simple modifications to
the
On 05/29/2013 08:39 PM, Marcelo Tosatti wrote:
> On Wed, May 29, 2013 at 11:03:19AM +0800, Xiao Guangrong wrote:
> the pages since other vcpus may be doing locklessly shadow
> page walking
>>>
>>> Ah, yes, i agree with you.
>>>
>>> We can introduce a list, say kvm->arch.obsolte_pages, to li
1 - 100 of 722 matches
Mail list logo