On 3 May 2014 05:46, Jonghwan Choi wrote:
> Hi. Viresh Kumar
> Your reply is so fast like Usain Bolt.
Heh, that's not true.. See how slow I was this time :)
>> So, create three flags:
>> OPP_TABLE_ORDER_ASCENDING 0
>> OPP_TABLE_ORDER_DESCENDING1
>>
Hello SELinux people, may I have your response?
Miklos Szeredi posted v3 of cross rename patchset at
http://marc.info/?l=linux-fsdevel=138921924707564=4 . In that thread,
I questioned him whether he already explained this proposal to LSM people.
He answered no and explained me what renameat2()
Hi Greg,
Today's linux-next merge of the tty tree got a conflict in
arch/arm64/kernel/early_printk.c between commit f774b7d10e21 ("arm64:
fixmap: fix missing sub-page offset for earlyprintk") from the tree and
commit 8ef0ed95ee04 ("arm64: remove arch specific earlyprintk") from the
tty tree.
I
Signed-off-by: Finn Thain
Cc: Michael Schmitz
---
As requested:
http://marc.info/?l=linux-arm-kernel=139853302724112=2
diff --git a/MAINTAINERS b/MAINTAINERS
index e67ea24..60ea600 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5996,6 +5996,28 @@ M: Petr Vandrovec
S: Odd Fixes
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
arch/arm/mach-berlin/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-berlin/Kconfig b/arch/arm/mach-berlin/Kconfig
index d3c5f14dc142..9c2b569e54ba 100644
--- a/arch/arm/mach-berlin/Kconfig
+++
The Marvell Berlin boards have a group based pinmuxing mechanism. This
adds the core driver support. We actually do not need any information
about the pins here and only have the definition of the groups.
Let's take the example of the uart0 pinmuxing on the BG2Q. Balls BK4 and
BH6 are muxed to
Add the pin-controller driver for the Berlin BG2Q SoC, with definition
of its groups and functions. This uses the core Berlin pinctrl driver.
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
drivers/pinctrl/berlin/Kconfig | 4 +
drivers/pinctrl/berlin/Makefile |
Add the pin-controller driver for the Berlin BG2 SoC, with definition
of its groups and functions. This uses the core Berlin pinctrl driver.
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
drivers/pinctrl/berlin/Kconfig | 4 +
drivers/pinctrl/berlin/Makefile | 1
Add the documentation related to the Berlin pin-controller driver and
explain how to configure this group based controller.
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
.../bindings/pinctrl/marvell,berlin-pinctrl.txt| 45 ++
1 file changed, 45
This series adds support for the Marvell Berlin pin-controller, allowing
to configure the pin muxing from the device tree.
The Berlin pin-controller support is divided into 3 drivers, each
driving one Berlin SoC. These drivers use a Berlin common part.
This series applies on top of patches
Add the pin-controller driver for the Berlin BG2CD SoC, with definition
of its groups and functions. This uses the core Berlin pinctrl driver.
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
drivers/pinctrl/berlin/Kconfig| 4 +
drivers/pinctrl/berlin/Makefile
The uart0 pinmux configuration is in the dtsi because uart0 will always
use uart0-pmux to work, no other possibility. Same thing for uart1 and
uart2 (BG2).
Signed-off-by: Antoine Ténart
Acked-by: Sebastian Hesselbarth
---
arch/arm/boot/dts/berlin2.dtsi | 31 +++
Commit 32e45ff43eaf5c17f changed the default value of
RECLAIM_DISTANCE to 30. However the comment around arch
specifc definition of RECLAIM_DISTANCE is not updated to
reflect the same. Correct the value mentioned in the comment.
Signed-off-by: Preeti U Murthy
Cc: Anton Blanchard
Cc: Benjamin
Hi Rafael,
Thanks for previous comments and suggestions.
I added the acpi_lapic in ia64. However I didn't find ia64 machine to
test it. Could you or anyone please help test this 2 patches?
I don't know how to test UP system running SMP kernel with no LAPIC in
MADT when it's ia64 arch.
Test
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam
Acked-by: Alan Stern
Acked-by: Jingoo Han
Acked-by: Kukjin Kim
---
Changes since v1:
- none
drivers/usb/host/ehci-exynos.c |5 ++---
1 file changed, 2 insertions(+), 3
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam
Acked-by: Alan Stern
Acked-by: Jingoo Han
Acked-by: Kukjin Kim
---
Changes since v1:
- none
drivers/usb/host/ohci-exynos.c | 20 +---
1 file changed, 9
Add support to consume phy provided by Generic phy framework.
Keeping the support for older usb-phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ohci-exynos.
Once we move to new phy in the device nodes for ohci, we can
remove the
From: Kamil Debski
Add the phy provider, supplied by new Exynos-usb2phy using
Generic phy framework.
Keeping the support for older USB phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ehci-exynos.
Once we move to new phy in the
On 05/04/2014 06:11 PM, Rik van Riel wrote:
> On 05/04/2014 07:44 AM, Preeti Murthy wrote:
>> Hi Rik, Mike
>>
>> On Fri, May 2, 2014 at 12:00 PM, Rik van Riel wrote:
>>> On 05/02/2014 02:13 AM, Mike Galbraith wrote:
On Fri, 2014-05-02 at 00:42 -0400, Rik van Riel wrote:
> Whether or
On Sun, 4 May 2014 18:52:43 -0400
Jeff Layton wrote:
> On Sat, May 3, 2014 at 4:15 PM, Fabian Frederick wrote:
> > Replacing all __constant_foo to foo()
> > except in smb2status.h (1700 lines to update).
> >
> > Cc: linux-c...@vger.kernel.org
> > Cc: Steve French
> > Cc: Andrew Morton
> >
In acpi_processor_get_info(), acpi processor info is initialized including
id, namely cpu index. Currently, if on UP system running SMP kerenl with
no LAPIC in MADT, cpu0_initialized is checked if acpi processor id is
initialized.
However this check maybe is not sufficient for kdump kernel. Most
This variable was defined and assigned in x86, is used to indicate
whether LAPIC exists in MADT. Now introduce it into ia64 to help
make correct judgment when get information for acpi processor later.
Signed-off-by: Baoquan He
---
arch/ia64/include/asm/acpi.h | 1 +
arch/ia64/kernel/acpi.c
On 05/04/2014 05:34 PM, Mike Galbraith wrote:
> On Sun, 2014-05-04 at 17:14 +0530, Preeti Murthy wrote:
>> Hi Rik, Mike
>>
>> On Fri, May 2, 2014 at 12:00 PM, Rik van Riel wrote:
>>> On 05/02/2014 02:13 AM, Mike Galbraith wrote:
On Fri, 2014-05-02 at 00:42 -0400, Rik van Riel wrote:
On Fri, May 02, 2014 at 09:29:25PM -0700, Guenter Roeck wrote:
> > > + if (wdd->ops->reboot)
> > > + wdd_reboot_dev = wdd;
> > > +
> >
> > Overall, it looks really great, but I guess we can make it a
> > list. Otherwise, we might end up in a situation where we could not
> > reboot
Hi Dan,
This patch is not a bugfix.
It is a simplification and consistency of coding for both adapter type B and D.
Regards,
Ching
2014-05-02 16:57 GMT+08:00 Dan Carpenter :
> On Wed, Apr 30, 2014 at 07:30:29PM +0800, ching wrote:
>> From: Ching
>>
>> Revise allocation of second
Hi all,
Today's linux-next merge of the tip tree got a conflict in
net/ipv4/tcp_output.c between commit e114a710aa50 ("tcp: fix cwnd limited
checking to improve congestion control") from the tree and commit
4e857c58efeb ("arch: Mass conversion of smp_mb__*()") from the tip tree.
I fixed it up
On Fri, May 02, 2014 at 10:40:48AM -0700, Mark Brown wrote:
> > i2c-dev works great in these cases, because you always have access to
> > all the bus, and all the devices, except if the device is already used
> > by someone. The patch I suggested is an attempt to mimic this.
>
> It seems better
Hi, Rafael
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Monday, May 05, 2014 8:43 AM
>
> On Saturday, May 03, 2014 08:59:14 AM Josh Boyer wrote:
> > On Tue, Apr 29, 2014 at 10:05 PM, Lv Zheng wrote:
> > > The commit
Hi Geert
On Fri, May 02, 2014 at 01:28:26AM +0200, Geert Uytterhoeven wrote:
> Hi Maxime,
>
> On Fri, May 2, 2014 at 12:36 AM, Maxime Ripard
> wrote:
> > But it actually doesn't work in a case where you can't really predict
> > what is on the other side of the bus. Either because, on the board
On 05/01/2014 07:43 PM, Pedro Alves wrote:
> On 04/28/2014 12:00 PM, Anshuman Khandual wrote:
>> The current documentation is bit misleading and does not explicitly
>> specify that iov.len need to be initialized failing which kernel
>> may just ignore the ptrace request and never read from/write
Hi Dan,
In this patch, there are several replace of call readl() or writel()
by direct access to memory.
Because in main memory, we allocated a block of memory for
post_qbuffer and done_qbuffer.
These memory are access by both of CPU and IOP, they are not hardware registers.
This change will not
On Sun, May 4, 2014 at 3:53 PM, Stephen Hemminger
wrote:
> On Mon, 5 May 2014 07:29:34 +1000
> Jon Maxwell wrote:
>
>> There has been a number incidents recently where customers running KVM have
>> reported that VM hosts on different Hypervisors are unreachable. Based on
>> pcap traces we
Currently, we use a rwlock tb_lock to protect concurrent access to
whole zram meta table. However, according to the actual access model,
there is only a small chance for upper user access the same table[index],
so the current lock granularity is too big.
This patch add a atomic state for every
Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> On Tue, 2014-04-22 at 14:12 -0400, Richard Guy Briggs wrote:
> > Questions:
> > Is there a way to link serial numbers of namespaces involved in migration
> > of a
> > container to another kernel? (I had a brief look at CRIU.) Is
Hi,
This serie moves the restart code out of the mach-sunxi directory to
either the watchdog driver or to a new driver in drivers/power/reset.
Since the reset code was pretty much all the code left in the
mach-sunxi directory for all the SoCs but the A31, the only thing left
into mach-sunxi are
2014-05-04 20:35 GMT+08:00 Himangi Saraogi :
> This patch moves data allocated using kzalloc to managed data allocated
> using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> functions.
Acked-by: Lan Tianyu
>
> The following Coccinelle semantic patch was used for making the
Most of the watchdog code is duplicated between the machine restart code and
the watchdog driver. Add the restart hook to the watchdog driver, to be able to
remove it from the machine code eventually.
Signed-off-by: Maxime Ripard
Acked-by: Arnd Bergmann
---
drivers/watchdog/sunxi_wdt.c | 29
Now that the A31 reset code is a driver of its own, we need it in the
defconfig.
Signed-off-by: Maxime Ripard
---
arch/arm/configs/sunxi_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index
On Sat, 2014-05-03 at 19:01 +0200, Sebastian Andrzej Siewior wrote:
> - Mike Galbraith sent a patch which might fix lazy preempt on x86_64.
> Patch applied and my machine still explodes therefore lazy preempt
> remains off on x86_64.
Can you send me your config offline? I'll try to scrape
Now that reset is handled either by the watchdog driver for the sun4i, sun5i
and sun7i, and by a driver of its own for sun6i, we can remove it from the
platform code.
Signed-off-by: Maxime Ripard
Acked-by: Arnd Bergmann
---
arch/arm/mach-sunxi/sunxi.c | 98
That code used to be in the machine code, but it's more fit here with other
restart hooks.
That will allow to cleanup the machine directory, while waiting for a proper
watchdog driver for the A31.
Signed-off-by: Maxime Ripard
Acked-by: Arnd Bergmann
---
drivers/power/reset/Kconfig| 7
Now that the reset code are part of drivers of their own, we need those in the
defconfig.
Signed-off-by: Maxime Ripard
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index
The init_machine hook is now at its default value. We can remove it.
Even though the sun4i and sun7i machines are nothing more than generic machines
now, leave them in so that we won't have to add them back if needed, and so
that the machine is still displayed in /proc/cpuinfo.
Signed-off-by:
On Mon, May 05, 2014 at 10:28:05AM +0800, Wei Yang wrote:
> Hi, all
>
> Anyone has some comment on this?
Did you miss the patch from Grant that is now in Linus's tree that
should resolve this issue?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Nothing particularly unusual going on. 45% drivers (drm, sound, md,
pin-control, acpi etc), 40% arch (mainly powerpc/powernv, but x86 and
arm too), 15% misc (perf tooling, documentation updates, core code).
The appended shortlog gives some kind of overview of the details
without being _too_ big.
Hi, all
Anyone has some comment on this?
On Mon, Apr 21, 2014 at 09:53:22AM +0800, Wei Yang wrote:
>There is one corner case in deferred probe which will lead a device in
>"dream" in the deferred_probe_pending_list.
>
>Suppose we have three devices, Tom, Jerry and Spike. Tom and Jerry have a
Andrew Morton writes:
> On Mon, 07 Apr 2014 14:24:45 +0930 Rusty Russell
> wrote:
>
>> Subject: param: hand arguments after -- straight to init
>>
>> The kernel passes any args it doesn't need through to init, except it
>> assumes anything containing '.' belongs to the kernel (for a module).
Bruno Prémont writes:
> On Tue, 22 April 2014 Rusty Russell wrote:
>> In line with practice for module parameters, we're adding a build-time
>> check that sysfs files aren't world-writable.
>>
>> Cc: Bruno Prémont
>> Signed-off-by: Rusty Russell
>
> Fine with me,
> Acked-by: Bruno Prémont
Hi all,
Today's linux-next merge of the net-next tree got conflicts in
net/sched/sch_api.c and net/sched/cls_api.c between commit 90f62cf30a78
("net: Use netlink_ns_capable to verify the permisions of netlink
messages") from the net tree and commit 4e8bbb819d15 ("net: Allow tc
changes in user
On Wed, Apr 30, 2014 at 11:26:43PM -0700, Brian Norris wrote:
> These defconfigs contain the CONFIG_M25P80 symbol, which is now
> dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to satisfy
> the new dependency.
>
> At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
>
On Wed, Apr 30, 2014 at 02:56:29PM +0200, Sebastian Hesselbarth wrote:
> This adds missing node labels to Kirkwood common and SoC specific nodes
> to allow to reference them more easily.
>
> Signed-off-by: Sebastian Hesselbarth
> ---
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc:
Commit-ID: 7fd44dacdd803c0bbf38bf478d51d280902bb0f1
Gitweb: http://git.kernel.org/tip/7fd44dacdd803c0bbf38bf478d51d280902bb0f1
Author: Mike Frysinger
AuthorDate: Sun, 4 May 2014 20:43:15 -0400
Committer: H. Peter Anvin
CommitDate: Sun, 4 May 2014 17:49:22 -0700
x86, x32: Use compat
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel I've stumbled on the following:
[ 3589.386869] BUG: unable to handle kernel NULL pointer dereference at
01f0
[ 3589.389326] IP: __lock_acquire (kernel/locking/lockdep.c:3070 (discriminator
1))
On Wed, Apr 30, 2014 at 02:56:28PM +0200, Sebastian Hesselbarth wrote:
> Commit 54397d85349f
> ("ARM: kirkwood: Relocate PCIe device tree nodes")
>
> moved the pcie-controller nodes for the Kirkwood SoCs to the mbus
> bus node. For some reason, two boards were not properly converted
> and have
The io_setup takes a pointer to a context id of type aio_context_t.
This in turn is typed to a __kernel_ulong_t. We could tweak the
exported headers to define this as a 64bit quantity for specific
ABIs, but since we already have a 32bit compat shim for the x86 ABI,
let's just re-use that logic.
On Saturday, May 03, 2014 08:59:14 AM Josh Boyer wrote:
> On Tue, Apr 29, 2014 at 10:05 PM, Lv Zheng wrote:
> > The commit of back porting Linux XSDT validation mechanism has introduced
> > a regreession:
> > Commit: 671cc68dc61f029d44b43a681356078e02d8dab8
> > Subject: ACPICA: Back port and
Hi,
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Thursday, May 01, 2014 4:15 AM
>
> On Wed, Apr 30, 2014 at 09:49:23PM +0200, Rafael J. Wysocki wrote:
> > On Wednesday, April 30, 2014 06:08:44 PM Dan Carpenter wrote:
> > > There are sometimes where we know that we are doing an
On Tuesday, April 29, 2014 12:25:39 PM Daniel Lezcano wrote:
> On 04/29/2014 01:11 AM, Rafael J. Wysocki wrote:
> > On Monday, April 28, 2014 01:07:31 PM Daniel Lezcano wrote:
[cut]
> > In my opinion it would be much better to have a knob representing the
> > current
> > relative value of
On Mon, Apr 28, 2014 at 11:12:08PM +0200, Sebastian Hesselbarth wrote:
> Non-DT irq handlers were working through irq causes from most-significant
> to least-significant bit, while DT irqchip driver does it the other way
> round. This revealed some more HW issues on Kirkwood peripheral IP, where
>
It's a debugging message, mark it so.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 241 +-
1 file changed, 121 insertions(+), 120 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 8a3aff7..3828c92 100644
---
It's unused, make it disappear.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 3828c92..8eaba53 100644
--- a/drivers/cdrom/cdrom.c
+++ b/drivers/cdrom/cdrom.c
@@ -339,9 +339,6 @@ do {
It's defined below without being called.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index a570e5f..08abbae 100644
--- a/drivers/cdrom/cdrom.c
+++ b/drivers/cdrom/cdrom.c
@@ -337,8 +337,6
Neaten the spacing too.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 246 +-
1 file changed, 122 insertions(+), 124 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 08abbae..332c3ae 100644
---
Move the function instead.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 193 +-
1 file changed, 97 insertions(+), 96 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 332c3ae..fac603a 100644
---
Move the function to the right spot instead.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 101 +-
1 file changed, 51 insertions(+), 50 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index fac603a..ed3 100644
Macros with hidden control flow aren't nice.
Just use copy_to/from_user directly instead.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 48 +++-
1 file changed, 27 insertions(+), 21 deletions(-)
diff --git a/drivers/cdrom/cdrom.c
Move function to proper location instead.
Fix whitespace and embedded if too.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 94 +--
1 file changed, 47 insertions(+), 47 deletions(-)
diff --git a/drivers/cdrom/cdrom.c
Move static function to the appropriate place to remove
the now unnecessary prototype.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 114 +-
1 file changed, 57 insertions(+), 57 deletions(-)
diff --git a/drivers/cdrom/cdrom.c
Move the function to appropriate locations instead.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 238 +-
1 file changed, 121 insertions(+), 117 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index
Move the function to the proper spot instead.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 71 ++-
1 file changed, 36 insertions(+), 35 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index c8ca342..49ac566
The actual static is defined below it but not used until later.
Signed-off-by: Joe Perches
---
drivers/cdrom/cdrom.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 5a38b56..a570e5f 100644
--- a/drivers/cdrom/cdrom.c
+++
Hey Jens.
I was cleaning up a bunch of old stuff on my computer
and noticed these...
On Mon, 2013-07-22 at 16:08 -0600, Jens Axboe wrote:
> On 07/22/2013 04:08 PM, Joe Perches wrote:
> > Anything going to happen via you with these patches?
> I'll queue them up for 3.12.
Awhile ago these might
Good evening,
Forgive my mistakes, I sent only a few patches yet and I'm still learning.
Nevertheless:
> What is that period in the commit message? And the semicolon?
Semicolons is what one use to ponctuate an enumerated list (at least
in french). In fact, it was their primary use before
On Friday, May 02, 2014 02:44:43 PM Alan Stern wrote:
> On Fri, 2 May 2014, Rafael J. Wysocki wrote:
>
> > Well, I have a second update.
> >
> > It has different flag names and changelog (that should explain things better
> > hopefully) and the purpose of both flags should be more clear now
On 05/04/2014 04:46 PM, Paolo Bonzini wrote:
>
> Your suggested trick of splitting the return paths for IF=0/IF=1 can be
> also done like this:
>
> movq EFLAGS-ARGOFFSET(%rsp), %rdi
> btrq $9, %rdi# Clear IF, save old value in CF
> movq %rdi, (%rsi)
> ...
> popfq
>
Il 02/05/2014 21:51, Linus Torvalds ha scritto:
> Also, are you *really* sure that "popf" has the same one-instruction
> interrupt shadow that "sti" has? Because I'm not at all sure that is
> true, and it's not documented as far as I can tell. In contrast, the
> one-instruction shadow after
On Mon, 5 May 2014 07:29:34 +1000
Jon Maxwell wrote:
> There has been a number incidents recently where customers running KVM have
> reported that VM hosts on different Hypervisors are unreachable. Based on
> pcap traces we found that the bridge was broadcasting the ARP request out
> onto
On Sat, May 3, 2014 at 4:15 PM, Fabian Frederick wrote:
> Replacing all __constant_foo to foo()
> except in smb2status.h (1700 lines to update).
>
> Cc: linux-c...@vger.kernel.org
> Cc: Steve French
> Cc: Andrew Morton
> Signed-off-by: Fabian Frederick
> ---
> fs/cifs/cifsacl.c | 2 +-
>
A few interrupt flags were not cleared in the ISR, resulting in a sytem
trapped in the ISR in cases one of those interrupts occurred. Clear all
flags to avoid such situations.
Signed-off-by: Soren Brinkmann
---
drivers/net/ethernet/cadence/macb.c | 10 ++
1 file changed, 10
Just as commit "net: macb: DMA-unmap full rx-buffer"
(48330e08fa168395b9fd9f369f06cca1df204361), pass the size that
was used for mapping the memory also to the unmap routine to
avoid warnings from the DMA_API.
Signed-off-by: Soren Brinkmann
---
drivers/net/ethernet/cadence/macb.c | 2 +-
1
Coverage data suggests that the unlikely case of receiving data while
the receive handler is running may not be that unlikely.
Coverage data after running iperf for a while:
91320: 891:work_done = bp->macbgem_ops.mog_rx(bp, budget);
91320: 892:if (work_done < budget) {
Under "heavy" RX load, the driver cannot handle the descriptors fast
enough. In detail, when a descriptor is consumed, its used flag is
cleared and once the RX budget is consumed all descriptors with a
cleared used flag are prepared to receive more data. Under load though,
the HW may constantly
When data is received during the driver processing received data the
NAPI is re-scheduled. In that case the RX interrupt should not be
re-enabled.
Signed-off-by: Soren Brinkmann
---
drivers/net/ethernet/cadence/macb.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff
Hi Nicolas,
I think I found the cause of the issue I told you about. Looks like
driver and HW are racing (a few more details in the commit message).
On my way finding that, I found a few more minor issues which are fixed
in the first patches.
The last one is "fixing" the actual race. I don't
On Sun, May 04, 2014 at 09:17:57PM +0200, Oleg Nesterov wrote:
> On 05/04, Paul E. McKenney wrote:
> >
> > On Sat, May 03, 2014 at 06:11:33PM +0200, Oleg Nesterov wrote:
> > >
> > > OK, if we can't rcu_read_unlock() with irqs disabled, then we can at least
> > > cleanup it (and document the
From: Rafael J. Wysocki
If freeze_enter() is called, we want to bypass the current cpuidle
governor and always use the deepest available (that is, not disabled)
C-state, because we want to save as much energy as reasonably possible
then and runtime latency constraints don't matter at that point,
On Friday, May 02, 2014 03:19:55 PM Daniel Lezcano wrote:
> On 05/02/2014 02:20 PM, Rafael J. Wysocki wrote:
> > On Friday, May 02, 2014 10:47:48 AM Daniel Lezcano wrote:
> >> On 04/30/2014 01:16 AM, Rafael J. Wysocki wrote:
> >>> On Tuesday, April 29, 2014 01:28:03 AM Rafael J. Wysocki wrote:
>
On 05/04/2014 02:31 PM, Linus Torvalds wrote:
> On Sun, May 4, 2014 at 12:59 PM, H. Peter Anvin
> wrote:
>>
>> Maybe let userspace sit in a tight loop doing RDTSC, and look for data
>> points too far apart to have been uninterrupted?
>
> That won't work, since Andy's patch improves on the
On Sun, May 04, 2014 at 11:19:28PM +0200, Francois Romieu wrote:
> Darek Marcinkiewicz :
> > On Sun, May 04, 2014 at 08:43:51PM +0200, Francois Romieu wrote:
> [...]
> > > Regarding tx_dnext updates, you may add a short notice in
> > > ec_bhf_start_xmit
> > > and ec_bhf_process_tx explaining
On 05/04/2014 01:27 PM, Greg Kroah-Hartman wrote:
On Sun, May 04, 2014 at 10:19:25AM -0700, Guenter Roeck wrote:
On 05/04/2014 08:38 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.3 release.
There are 158 patches in this series, all will be posted as a
On Sun, May 4, 2014 at 12:59 PM, H. Peter Anvin wrote:
>
> Maybe let userspace sit in a tight loop doing RDTSC, and look for data
> points too far apart to have been uninterrupted?
That won't work, since Andy's patch improves on the "interrupt
happened in kernel space", not on the user-space
There has been a number incidents recently where customers running KVM have
reported that VM hosts on different Hypervisors are unreachable. Based on pcap
traces we found that the bridge was broadcasting the ARP request out onto the
network. However some NICs have an inbuilt switch which on
On Sun, May 04, 2014 at 09:52:09PM +0200, Clément Calmels wrote:
> Remove C99 comment and rewrite lines over 80 characters.
> Warnings and error found by checkpatch.pl script.
>
> Signed-off-by: Clément Calmels
> ---
> drivers/staging/vt6655/tmacro.h | 13 +
> 1 file changed, 9
On Sun, May 4, 2014 at 1:42 PM, Richard Weinberger wrote:
>
> I cannot tell why UML has it's own tlb gather logic, I suspect nobody
> cared so far to clean up the code.
> That said, I've converted it today to the generic gather logic and it works.
> Sadly I'm still facing the same issues (sigh!).
Darek Marcinkiewicz :
> On Sun, May 04, 2014 at 08:43:51PM +0200, Francois Romieu wrote:
[...]
> > Regarding tx_dnext updates, you may add a short notice in ec_bhf_start_xmit
> > and ec_bhf_process_tx explaining that the periodic poller will somehow end
> > working with the right value, whence no
Am 04.05.2014 22:37, schrieb Hugh Dickins:
> On Sat, 3 May 2014, Richard Weinberger wrote:
>> On Thu, May 1, 2014 at 6:20 PM, Richard Weinberger
>> wrote:
>>> On Wed, Apr 16, 2014 at 10:40 PM, Hugh Dickins wrote:
Help!
>>>
>>> Using a trinity as of today I'm able to trigger this bug on
Am 04.05.2014 20:31, schrieb Linus Torvalds:
>> With your patch applied I see lots of BUG: Bad rss-counter state messages on
>> UML (x86_32)
>> when fuzzing with trinity the mremap syscall.
>> And sometimes I face BUG at mm/filemap.c:202.
>
> I'm suspecting that it's some UML bug that is
On Sat, 3 May 2014, Richard Weinberger wrote:
> On Thu, May 1, 2014 at 6:20 PM, Richard Weinberger
> wrote:
> > On Wed, Apr 16, 2014 at 10:40 PM, Hugh Dickins wrote:
> >>
> >> Help!
> >
> > Using a trinity as of today I'm able to trigger this bug on UML within
> > seconds.
> > If you want me to
On Fri, May 2, 2014 at 4:01 PM, Seth Jennings wrote:
> On Sat, Apr 26, 2014 at 04:37:31PM +0800, Weijie Yang wrote:
>> On Sat, Apr 19, 2014 at 11:52 PM, Dan Streetman wrote:
>> > Add zs_shrink() and helper functions to zsmalloc. Update zsmalloc
>> > zs_create_pool() creation function to include
On Sun, May 04, 2014 at 10:19:25AM -0700, Guenter Roeck wrote:
> On 05/04/2014 08:38 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.14.3 release.
> > There are 158 patches in this series, all will be posted as a response
> > to this one. If anyone has any
1 - 100 of 958 matches
Mail list logo
