On 03/21/2014 12:31 AM, Pavel Emelyanov wrote:
On 03/20/2014 01:39 PM, Janani Venkataraman wrote:
Getting number of threads and their respective IDs through /proc/pid/stat and
/proc/pid/task.
The threads are then seized and interrupted. After the dump is taken they are
detached.
Signed-off-by
Thanks
Acked-by: Xuetao Guan
- Chen Gang 写道：
> Add generic definition just like another architectures have done, or
> can not pass compiling with allmodconfig, the related error:
>
> CC kernel/profile.o
> kernel/profile.c: In function ‘profile_tick’:
> kernel/profile.c:419: er
Kirill A. Shutemov with the commit 96bacfe542 introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
Based on his workload runs, suggested FAULT_AROUND_ORDER
(knob to control the numbers of pages to map) is 4.
This patch
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory) is below. Fault around order (FAO)
value of 3 looks more advantageous.
FAULT_AROUND_ORDER Baseline1 3 4
5 7
Li
Hi,
>From: Lee Jones
>
>Hi Brian,
>
>Firstly I'd like to thank you for supporting the inclusion of ST's SPI
>NOR (FSM) driver. As promised I will convert it over to the new
>framework once it has been applied by your good self.
>
>In the meantime however, I have a NAND driver which I need to
>subm
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
(2014/03/24 23:59), Steven Rostedt wrote:
> On Mon, 24 Mar 2014 20:26:05 +0900
> Masami Hiramatsu wrote:
>
>
>> Thank you for reporting with this pretty backtrace :)
>> Steven, I think this is not the kprobe bug but ftrace (and perhaps, module).
>
> Looks to be more of a module issue than a ftr
the vma range size is always page size aligned in mmap, while the
real io space range may not be page aligned, thus leading to range
check failure in the uio_mmap_physical().
for example, in a case of io range size "mem->size == 1KB", and we
have (vma->vm_end - vma->vm_start) == 4KB, due to "len"
> -Original Message-
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Tuesday, March 25, 2014 1:46 AM
> To: netdev
> Cc: Shahed Shaikh; Dept-HSG Linux NIC Dev; linux-kernel
> Subject: [PATCH net-next 4/7] qlcnic: Remove casts of pointer to same type
>
> Casting a pointer to a pointer
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> And, if you are willing to take it, one late-breaking commit. This one
> was requested for 3.15 by Peter Zijlstra. [...]
No objections at all, looks like a useful facility!
> [...] It is low risk because it adds a new in-kernel API with
> minimal
On 03/24/2014 01:51 PM, Hidetoshi Seto wrote:
> (2014/03/24 16:45), Preeti Murthy wrote:
>> Hi Hidetoshi,
>>
>> The patch looks good to me except the comments around the monotonicity
>> of the return value of the idle stats observer. I am unable to relate them
>> to the dependency on nr_iowait_cpu.
Quoting Gabriel FERNANDEZ (2014-02-27 07:24:14)
> +/**
> + * DOC: Clock mux with a programmable divider on each of its three inputs.
> + * The mux has an input setting which effectively gates its output.
> + *
> + * Traits of this clock:
> + * prepare - clk_(un)prepare only ensures parent is (
Hi, Sandeep Gopalpet
I am a developer. Now I confronted an interesting phenomena. When I used
linux kernel 2.6.34.15 on freescale-p2020, I can not receive raw and
vlan packets on gfar-enet nic. But with e1000e nic, we can make vlan and
raw packets work well. I looked into the source code and f
There were just a handful of more while loops in this file that need timeouts,
and this patch takes care of them, using comedi_timeout(). A couple of new
callbacks are introduced, but there was one case where the appropriate callback
function was already defined; in this case I have just used that
Set error bit for incomplete buffers when end of buffer is detected by
FID toggling (for example when last transaction with EOF is lost).
This prevents passing incomplete buffers to the userspace.
Signed-off-by: Anton Leontiev
---
drivers/media/usb/uvc/uvc_video.c | 21 +++--
1 f
From: Stephen Rothwell
Date: Tue, 25 Mar 2014 13:04:47 +1100
> Today's linux-next merge of the net-next tree got a conflict in
> net/core/netpoll.c between commit c27f0872a344 ("netpoll: fix the skb
> check in pkt_is_ns") from the net tree and commit 9c62a68d1311 ("netpoll:
> Remove dead packet r
On Mon, Mar 24, 2014 at 8:11 PM, wrote:
> From: Dirk Brandewie
>
> Ensure that no timer callback is running since we are about to free
> the timer structure. We cannot guarantee that the call back is called
> on the CPU where the timer is running.
>
> Reported-by: Thomas Gleixner
> Signed-off-
Hello, Ingo,
And, if you are willing to take it, one late-breaking commit. This one
was requested for 3.15 by Peter Zijlstra. It is low risk because it adds
a new in-kernel API with minimal changes to the existing code. Those
minimal changes are the addition of memory barriers and ACCESS_ONCE()
Hi Tomi,
Today's linux-next merge of the omap_dss2 tree got a conflict in
drivers/video/fbdev/exynos/Kconfig between commit 2e4e678aa8a4
("drm/exynos: Move dp driver from video/ to drm/") from the drm tree and
commits 07e521b66cf0 ("video: exynos: Remove OF dependency for Exynos
DP") and 844901bae
On 03/24/2014 08:08 PM, David Lang wrote:
> On Fri, 21 Mar 2014, Matias Bjorling wrote:
>
>> On 03/21/2014 02:06 AM, Joe Thornber wrote:
>>> Hi Matias,
>>>
>>> This looks really interesting and I'd love to get involved. Do you
>>> have any recommendations for what hardware I should pick up?
>>
>>
On 03/24/2014 07:22 PM, Akira Hayakawa wrote:
> Hi, Matias,
>
> Sorry for jumping in. I am interested in this new feature, too.
>
>>> Does it even make sense to expose the underlying devices as block
>>> devices? It surely would help to send this together with a driver
>>> that you plan to use i
On 2014/3/25 11:00, Zheng Li wrote:
> In bond mode tlb and alb, inactive slaves should keep inactive flag to
> 1 to refuse to receive broadcast packets. Now, active slave send broadcast
> packets
> (for example ARP requests) which will arrive inactive slaves on same host
> from switch,
> but inac
On 03/23/2014 11:13 PM, Bart Van Assche wrote:
> On 03/21/14 16:37, Christoph Hellwig wrote:
>> Just curious: why do you think implementing this as a block remapper
>> inside device mapper is a better idea than as a blk-mq driver?
>>
>> At the request layer you already get a lot of infrastructure
Ping..
On 03/10/2014 10:01 PM, Xiao Guangrong wrote:
> This patchset is splited from my previous patchset:
> [PATCH v3 00/15] KVM: MMU: locklessly write-protect
> that can be found at:
> https://lkml.org/lkml/2013/10/23/265
>
> Changelog v4 :
> - add more comments for patch 5 and thank for M
On Fri, 21 Mar 2014, Matias Bjorling wrote:
On 03/21/2014 02:06 AM, Joe Thornber wrote:
Hi Matias,
This looks really interesting and I'd love to get involved. Do you
have any recommendations for what hardware I should pick up?
Hi Joe,
The most easily available platform is OpenSSD
(http://w
Hi Rusty,
After merging the modules tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/thread_info.h:11:0,
from arch/x86/include/asm/preempt.h:6,
from include/linux/preempt.h:18,
from includ
On Sat, 2014-03-22 at 22:01 +0100, Andreas Sturmlechner wrote:
> Original Message from: Ben Hutchings
> >
> > Andreas, could you test whether this regression is also present in
> > 3.2.55? This patch is based on my backport for 3.2.y.
> >
>
> 3.2.55 is OK here.
One piece of my backport to 3.2
In bond mode tlb and alb, inactive slaves should keep inactive flag to
1 to refuse to receive broadcast packets. Now, active slave send broadcast
packets
(for example ARP requests) which will arrive inactive slaves on same host from
switch,
but inactive slave's inactive flag is zero that cause br
I delayed things a day from my normal schedule, hoping I'd feel more
comfortable doing a 3.14 release, but that was not to be. So here's an
rc8, and I expect to do the final 3.14 release next weekend.
There wasn't that much scary stuff going on, but there's a few vfs
fixes still pending, and we di
On 03/24/2014 06:38 PM, Greg KH wrote:
On Mon, Mar 24, 2014 at 05:12:09PM -0600, Shuah Khan wrote:
Fix commit - 88fa1ebfa21b5deaaad2dc88ecd9f6af91796cf7
What do you mean by this line?
Nothing really. Sloppiness on my part. I was keeping notes as I was
chasing the problem and those ended up
> From: nickkra...@sympatico.ca
> To: a...@lxorguk.ukuu.org.uk
> CC: linux-m...@linux-mips.org; linux-kernel@vger.kernel.org;
> r...@linux-mips.org
> Subject: RE: PATCH[60485 Bug adding breakpoint]
> Date: Mon, 24 Mar 2014 00:19:29 +
>
>
>
>
>
> Here
Hi, Matias,
Sorry for jumping in. I am interested in this new feature, too.
> > Does it even make sense to expose the underlying devices as block
> > devices? It surely would help to send this together with a driver
> > that you plan to use it on top of.
> >
>
> Agree, an underlying driver is
On Sun, Mar 23, 2014 at 1:16 AM, Sebastian Andrzej Siewior
wrote:
> d->mask contains exact the same information as BIT(bit) so we could save
> a few cycles here.
>
> Signed-off-by: Sebastian Andrzej Siewior
> ---
> drivers/gpio/gpio-dwapb.c | 25 -
> 1 file changed, 12 in
On 03/25/2014 01:39 AM, Chris Metcalf wrote:
The problem is that audit_is_compat() is a dynamic test that the compiler
can't optimize away, so you end with an undefined reference to
audit_classify_compat_syscall().
For some reason audit_classify_compat_syscall() is declared as __weak
in ; usuall
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/core/netpoll.c between commit c27f0872a344 ("netpoll: fix the skb
check in pkt_is_ns") from the net tree and commit 9c62a68d1311 ("netpoll:
Remove dead packet receive code (CONFIG_NETPOLL_TRAP)") from the net-next
tree.
I
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
Documentation/devicetree/bindings/net/micrel-ks8851.txt between commit
ebf4ad955d3e ("net: micrel : ks8851-ml: add vdd-supply support") from
the tree and commit e8f08ee0ad86 ("DT: net: document Ethernet bindings
in one place"
On Mon, Mar 24, 2014 at 08:00:03PM -0400, Santosh Shilimkar wrote:
> On Monday 24 March 2014 07:55 PM, Stephen Rothwell wrote:
> > Hi Santosh,
> >
> > Today's linux-next merge of the keystone tree got a conflict in
> > arch/arm/boot/dts/Makefile between commit ba5a37e52194 ("ARM: mvebu: Move
> > k
Hi Vinod, and all
Could you please teach me current status of this patch ??
> From: Kuninori Morimoto
>
> Add support Audio DMAC peri peri driver
> for Renesas R-Car Gen2 SoC, using 'shdma-base'
> DMA driver framework.
>
> Signed-off-by: Kuninori Morimoto
> ---
> v2 -> v3
>
> - modiry copy
Joe Perches wrote:
> On Tue, 2014-03-25 at 01:24 +0100, Mathieu Maret wrote:
> > Fix the following spare warning
>
> sparse
>
> > drivers/staging/android/binder.c:2691:21: warning: incorrect type in
> > argument 1 (different address spaces)
> []
> > diff --git a/drivers/staging/android/binder.c
On Tue, 2014-03-25 at 01:24 +0100, Mathieu Maret wrote:
> Fix the following spare warning
sparse
> drivers/staging/android/binder.c:2691:21: warning: incorrect type in argument
> 1 (different address spaces)
[]
> diff --git a/drivers/staging/android/binder.c
> b/drivers/staging/android/binder.c
Just to clarify: the current vfs tree from Al works for you, no new issues?
I was delaying the release first a day, and now I think I'll just do
an rc8 after all (and do the final 3.14 next weekend), but I'd like to
be sure what the status of Al's tree is.
Al, can you send a new pull request with
On 03/24/2014 05:48 PM, Jan Kara wrote:
>[ 339.948946] ** 4194304 8805ac03ba38 [eventpoll] 8806ec051fe0
>[eventpoll] 84666040 88056c73e7b0 (null)
OK, great. So finally we have something useful. We know we have problems
with [eventpoll] dentry. That is actually a
On Mon, Mar 24, 2014 at 05:12:09PM -0600, Shuah Khan wrote:
> Fix commit - 88fa1ebfa21b5deaaad2dc88ecd9f6af91796cf7
What do you mean by this line?
> This commit added return value check for sscanf() that parses the
> input buffer for four input items. However, the return value check
> is incorrec
This is a RFC to add Keystone pcie driver. I had some earlier discussion on
the pcie mailing about this driver and at that time I didn't have the driver
ported to dw core driver. I now have a driver working with intel's e1000e
ethernet driver and want to review this RFC on this list.
Kestone PCIE
keystone pcie hardware is based on designware hw version 3.65.
There is no support for ATU port and have registers in
application space to configure inbound/outbound access. Also
doesn't support PCI PVM option. So the MSI IRQ registers available
in application space is used to mask/unmask/enable th
keystone pcie hardware is based on designware version 3.65. This
doesn't support standard MSI controller and ATU port available
on newer version of the designware hardware. In keystone dw hardware
the application register space implements the legacy and MSI
irq controller registers and has register
Add pcie related options by default for keystone architecture
CC: Jingoo Han
CC: Bjorn Helgaas
CC: Kukjin Kim
CC: Richard Zhu
CC: Shawn Guo
CC: Mohit Kumar
CC: Santosh Shilimkar
Signed-off-by: Murali Karicheri
---
arch/arm/mach-keystone/Kconfig |2 ++
1 file changed, 2 insertions(+)
keystone pcie hardware is based on designware hw version 3.65.
There is no support for ATU port and have registers in
application space to configure inbound/outbound access. Also
doesn't support PCI PVM option. So the MSI IRQ registers available
in application space is used to mask/unmask/enable th
Add pcie related options by default for keystone architecture
CC: Jingoo Han
CC: Bjorn Helgaas
CC: Kukjin Kim
CC: Richard Zhu
CC: Shawn Guo
CC: Mohit Kumar
CC: Santosh Shilimkar
Signed-off-by: Murali Karicheri
---
arch/arm/mach-keystone/Kconfig |2 ++
1 file changed, 2 insertions(+)
This is a RFC to add Keystone pcie driver. I had some earlier discussion on
the pcie mailing about this driver and at that time I didn't have the driver
ported to dw core driver. I now have a driver working with intel's e1000e
ethernet driver and want to review this RFC on this list.
Kestone PCIE
keystone pcie hardware is based on designware version 3.65. This
doesn't support standard MSI controller and ATU port available
on newer version of the designware hardware. In keystone dw hardware
the application register space implements the legacy and MSI
irq controller registers and has register
Signed-off-by: Mathieu Maret
---
drivers/staging/android/binder.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
index 9418086..4e51034 100644
--- a/drivers/staging/android/binder.c
+++ b/drivers/staging/an
Fix the following spare warning
drivers/staging/android/binder.c:2691:21: warning: incorrect type in argument 1
(different address spaces)
Signed-off-by: Mathieu Maret
---
drivers/staging/android/binder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/androi
On Tuesday, March 25, 2014 12:54 AM, Alexandre Belloni wrote:
> On 21/03/2014 at 09:51:16 +0900, Jingoo Han wrote :
> > On Wednesday, March 19, 2014 11:23 PM, Hans-Christian Egtvedt wrote:
> > > Around Wed 19 Mar 2014 14:03:27 +0100 or thereabout, Alexandre Belloni
> > > wrote:
> > > > The atmel-p
Quoting Krzysztof Kozlowski (2014-03-21 05:18:17)
> If parent device does not have of_node set the s2mps11_clk_parse_dt()
> returned NULL. This NULL was later passed to of_clk_add_provider() which
> dereferenced it in pr_debug() call.
>
> Signed-off-by: Krzysztof Kozlowski
I've taken both of the
On Monday 24 March 2014 07:55 PM, Stephen Rothwell wrote:
> Hi Santosh,
>
> Today's linux-next merge of the keystone tree got a conflict in
> arch/arm/boot/dts/Makefile between commit ba5a37e52194 ("ARM: mvebu: Move
> kirkwood DT boards into mach-mvebu") from the arm-soc tree and commit
> 400550ae
Ian made some late comments about the grant mapping series, I incorporated the
functional outcomes into this patch:
- use callback_param macro to shorten access to pending_tx_info in
xenvif_fill_frags() and xenvif_tx_submit()
- print an error message in xenvif_idx_unmap() before panic
Signed-of
Ian made some late comments about the grant mapping series, I incorporated the
non-functional outcomes into this patch:
- typo fixes in a comment of xenvif_free(), and add another one there as well
- typo fix for comment of rx_drain_timeout_msecs
- remove stale comment before calling xenvif_grant_
Since the early days TX stops if there isn't enough free pending slots to
consume a maximum sized (slot-wise) packet. Probably the reason for that is to
avoid the case when we don't have enough free pending slot in the ring to finish
the packet. But if we make sure that the pending ring has the sam
Hi Santosh,
Today's linux-next merge of the keystone tree got a conflict in
arch/arm/boot/dts/Makefile between commit ba5a37e52194 ("ARM: mvebu: Move
kirkwood DT boards into mach-mvebu") from the arm-soc tree and commit
400550ae7e77 ("ARM: dts: Build all keystone dt blobs") from the keystone
tree.
Hi Joe, thanks for the patch.
On Mon, Mar 24, 2014 at 3:15 PM, Joe Perches wrote:
> Casting a pointer to a pointer of the same type is pointless,
> so remove these unnecessary casts.
>
> Done via coccinelle script:
>
> $ cat typecast_2.cocci
> @@
> type T;
> T *foo;
> @@
>
> - (T *)foo
> +
From: Andrey Vagin
Date: Fri, 21 Mar 2014 17:32:58 +0400
> Currently connections only in the TCP_ESTABLISHED state can be dumped and
> restored. This series allows to restore connections in the FIN_WAIT_1,
> FIN_WAIT_2, LAST_ACK, CLOSE_WAIT or CLOSING states.
>
> For restoring closing states we
Am Montag, 24. März 2014, 23:36:01 schrieb Beniamino Galvani:
> The correct value of .mux_offset for rk3188 seems to be 0x60
> instead of 0x68.
Executive summary: the offset-change itself is correct, therefore
Reviewed-by: Heiko Stuebner
That is what one gets when the only source is a vendor
Fix commit - 88fa1ebfa21b5deaaad2dc88ecd9f6af91796cf7
This commit added return value check for sscanf() that parses the
input buffer for four input items. However, the return value check
is incorrect, as it checks for one input item instead of four which
is what it is expecting in the input buffer.
Hi,
On Mon, Mar 24, 2014 at 10:46:49PM +0100, Daniel Vetter wrote:
> On Mon, Mar 24, 2014 at 9:40 PM, Mikulas Patocka wrote:
> > If someone understands the locking issues I pointed out above, it could be
> > easy to fix.
>
> The locking issue isn't your problem, the real issue is that putting a
On Mon, Mar 24, 2014 at 05:42:34PM +0900, Alexandre Courbot wrote:
[...]
> diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nve0.c
> b/drivers/gpu/drm/nouveau/core/engine/device/nve0.c
[...]
> + /* TODO will need an implementation for this at some point... */
Do we? If so the c
On Mon, Mar 24, 2014 at 05:42:33PM +0900, Alexandre Courbot wrote:
> GK20A does not embed a dedicated COPY engine and thus cannot allocate
> the copy channel that nouveau_accel_init() attempts to create. It also
> lacks any display hardware, so the creation of a software channel does
> not apply ne
On Mon, Mar 24, 2014 at 05:42:31PM +0900, Alexandre Courbot wrote:
> Pad the microcode to a multiple of 0x40, otherwise firmware will fail to
> run from non-prepadded firmware files.
Perhaps this (and the comment in the code) should mention a unit. In
this case it's 0x40 words. Also, I think using
On Mon, Mar 24, 2014 at 08:22:12AM +0100, Jakub Sitnicki wrote:
> acl.c has not been (directly) using the interface defined by
> linux/capability.h header since commit 3bd858ab1c451725c07a
> ("Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid
> check"). Remove it.
>
> Signed-off-by: Ja
> [...]
> Shortlog:
> Al Viro (6):
> make prepend_name() work correctly when called with negative
*buflen
A proper attribution for the above fix would have been nice. Tracking
down the bug was the main thing after all:
https://lkml.org/lkml/2014/3/12/620
--Imre
--
To unsubscribe from this
On Mon, Mar 24, 2014 at 05:42:30PM +0900, Alexandre Courbot wrote:
[...]
> diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c
> b/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c
> index 6ef8bf181b2d..f997a18f5760 100644
> --- a/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c
> +++ b/d
Dear RT Folks,
I'm pleased to announce the 3.4.84-rt105 stable release.
This release is just an update to the new stable 3.4.84 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.
Use the more common kernel coding style.
Signed-off-by: Fabian Mewes
---
applies to next-20140324
v1..v2: improve commit message as suggested by Joe
drivers/staging/line6/driver.c | 1 +
drivers/staging/line6/playback.c | 5 +
drivers/staging/line6/toneport.c | 1 +
3 files changed, 7
> @@ -2375,7 +2378,7 @@ void tcp_sock_destruct(struct sock *sk)
> static inline bool tcp_can_repair_sock(const struct sock *sk)
> {
> return ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN) &&
> - ((1 << sk->sk_state) & (TCPF_CLOSE | TCPF_ESTABLISHED));
> + (sk->sk_s
The correct value of .mux_offset for rk3188 seems to be 0x60
instead of 0x68.
Signed-off-by: Beniamino Galvani
---
drivers/pinctrl/pinctrl-rockchip.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-rockchip.c
b/drivers/pinctrl/pinctrl-rockchip.c
in
On Mon, Mar 24, 2014 at 05:42:28PM +0900, Alexandre Courbot wrote:
[...]
> diff --git a/drivers/gpu/drm/nouveau/core/subdev/ibus/nvea.c
> b/drivers/gpu/drm/nouveau/core/subdev/ibus/nvea.c
[...]
> +#include
> +
> +struct nvea_ibus_priv {
> + struct nouveau_ibus base;
> +};
> +
> +static void
>
Dear RT Folks,
I'm pleased to announce the 3.10.34-rt34 stable release.
This release is just an update to the new stable 3.10.34 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
Hi Joe,
Thanks for the patch.
> Casting a pointer to a pointer of the same type is pointless,
> so remove these unnecessary casts.
>
> Done via coccinelle script:
>
> $ cat typecast_2.cocci
> @@
> type T;
> T *foo;
> @@
>
> - (T *)foo
> + foo
>
> Signed-off-by: Joe Perches
Acked-by:
On Mon, Mar 24, 2014 at 05:42:27PM +0900, Alexandre Courbot wrote:
> GK20A's FIFO is compatible with NVE0, but only features 128 channels and
> 1 runlist.
>
> Signed-off-by: Alexandre Courbot
> ---
> drivers/gpu/drm/nouveau/Makefile | 1 +
> drivers/gpu/drm/nouveau/core/engine
On Mon, Mar 24, 2014 at 05:42:25PM +0900, Alexandre Courbot wrote:
> Some chips that use system memory exclusively (e.g. GK20A) do not
> expose 2 BAR regions. For them only BAR1 exists, and it should be used
> for USERD mapping. Do not map BAR3 if its resource does not exist.
>
> Signed-off-by: Al
On Mon, Mar 24, 2014 at 05:42:26PM +0900, Alexandre Courbot wrote:
[...]
> diff --git a/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c
> b/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c
[...]
> static int
> -nvc0_bar_ctor(struct nouveau_object *parent, struct nouveau_object *engine,
> -
On Sat, Mar 22, 2014 at 9:18 AM, Andy Lutomirski wrote:
> On Fri, Mar 21, 2014 at 9:37 AM, Bjorn Helgaas wrote:
>> On Fri, Mar 21, 2014 at 9:49 AM, Andy Lutomirski wrote:
>>> On Fri, Mar 21, 2014 at 7:41 AM, Alex Deucher wrote:
On Thu, Mar 20, 2014 at 10:17 PM, Andy Lutomirski
wrote
Quoting Maxime Coquelin (2014-03-21 07:09:26)
> Hi Mike,
>
> On 03/21/2014 02:45 AM, Mike Turquette wrote:
> > Quoting Sylwester Nawrocki (2014-03-20 05:42:33)
> >> Hi Maxime,
> >>
> >> On 06/03/14 14:45, Maxime Coquelin wrote:
> >>> Hi Sylwester,
> >>>
> >>>I like the principle of your im
On Mon, Mar 24, 2014 at 05:42:24PM +0900, Alexandre Courbot wrote:
> GK20A's timer is directly attached to the system timer and cannot be
> calibrated. Skip the calibration phase on that chip since the
> corresponding registers do not exist.
>
> Signed-off-by: Alexandre Courbot
> ---
> drivers/g
01f795f9e0d67a
("ext4: add online resizing support for meta_bg and 64-bit file systems")
removed the last use of MAX_32_NUM
Signed-off-by: Fabian Frederick
---
fs/ext4/ioctl.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c
index a2a837f..ea5dace 100644
---
Quoting Maxime Ripard (2014-03-13 08:14:13)
> Callers of clk_put must disable the clock first. This also means that as long
> as the clock is enabled the driver should hold a reference to that clock.
> Hence, the call to clk_put here are bogus and should be removed.
>
> Signed-off-by: Maxime Ripar
On Mon, Mar 24, 2014 at 05:42:23PM +0900, Alexandre Courbot wrote:
> Add a missing newline at the end of a DRM_INFO message.
>
> Signed-off-by: Alexandre Courbot
> ---
> drivers/gpu/drm/nouveau/nouveau_drm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thierry Reding
On Mon 24-03-14 10:42:25, Sasha Levin wrote:
> On 03/10/2014 10:13 AM, Sasha Levin wrote:
> >On 03/10/2014 06:43 AM, Jan Kara wrote:
> >> By garbage, do you mean that it is a poison, completely random data or
> >> does
> >>inode->i_sb look like a valid pointer but just superblock isn't where it
On Mon, Mar 24, 2014 at 9:40 PM, Mikulas Patocka wrote:
>> > > -> All hell breaks loose if Xorg dies and takes all it's mappings with it
>> > > (in master_destroy, since the Xorg /dev fd is the master) and leaves the
>> > > driver hanging in the air if there's an interrupt still pending (or
>> > >
On Mon, 2014-03-24 at 21:51 +0100, Fabian Mewes wrote:
> This patch is part of eudyptula challenge task 10
>
> Signed-off-by: Fabian Mewes
Hi Fabian.
The patch seems fine, but please do not use something
like the above as a commit message.
It would be better to describe _why_ the change should
On Mon, Mar 24, 2014 at 2:33 AM, Arend van Spriel wrote:
> On 23/03/14 23:31, anish singh wrote:
>>
>> Many a time i have got a crash and it is difficult
>> to find out the exact function which crashed
>> because the crash stack doesn't show the "real"
>> function because gcc inlines many function
On Mon, 24 Mar 2014, Anders Berg wrote:
> The fixmap area was hard coded to 224 pages which was only enough for 14
> CPU:s.
> Now the area adapts to the configured number of CPU:s (NR_CPUS). We still have
> a hard limit of 30 CPU:s since we only have a single pte-chunk (512 pte:s).
>
> Signed-of
I would like to know if it would be possible to use a 64 bit futex
call? If not, I would like to request it be added. (It is acknowledged
in the manpages that it must be added eventually anyway.)
I am programming a C++11+ library. One of the constructed features is
a "locking pointer". Unfortunate
Hi,
While working of platform support for the LSI AXM5516 SoC (a 16 x A15 device)
we ran into this limitation in fixmap.h where there is not enough room for the
per-cpu pages if NR_CPUS is set to 16.
The following patch avoids the overlap by lowering the base address according to
the values of NR
The fixmap area was hard coded to 224 pages which was only enough for 14 CPU:s.
Now the area adapts to the configured number of CPU:s (NR_CPUS). We still have
a hard limit of 30 CPU:s since we only have a single pte-chunk (512 pte:s).
Signed-off-by: Anders Berg
Signed-off-by: Fredrik Markström
-
On Mon, 24 Mar 2014, Daniel Vetter wrote:
> On Mon, Mar 24, 2014 at 01:17:12PM -0400, Mikulas Patocka wrote:
> > > > > Hmm, given that Mikulas in
> > > > > https://lkml.org/lkml/2014/2/26/537
> > > > > offered a diff of linux-3.13.5 files, it truly seems (shock! ack!
> > > > > noo!)
> > > > >
This patch is part of eudyptula challenge task 10
Signed-off-by: Fabian Mewes
---
applies to next-20140324
drivers/staging/line6/driver.c | 1 +
drivers/staging/line6/playback.c | 5 +
drivers/staging/line6/toneport.c | 1 +
3 files changed, 7 insertions(+)
diff --git a/drivers/staging
Have the netlink per-protocol optional bind function return an int error code
rather than void to signal a failure.
This will enable netlink protocols to perform extra checks including
capabilities and permissions verifications when updating memberships in
multicast groups.
In netlink_bind() and
Fixes these sparse warnings:
drivers/staging/lustre/lustre/lmv/lproc_lmv.c:202:51: warning: Using plain
integer as NULL pointer
drivers/staging/lustre/lustre/lmv/lproc_lmv.c:203:51: warning: Using plain
integer as NULL pointer
drivers/staging/lustre/lustre/lmv/lproc_lmv.c:204:51: warning: Using p
In order for the c2c tool to work correctly, it needs to properly
sort all the records on uniquely identifiable data addresses. These
unique addresses are converted from virtual addresses provided by the
hardware into a kernel address using an mmap2 record as the decoder.
Once a unique address is
1 - 100 of 445 matches
Mail list logo
