On Sat, Jan 10, 2015 at 09:32:33PM -0800, Joe Perches wrote:
> On Sat, 2015-01-10 at 21:24 -0800, Greg Kroah-Hartman wrote:
> > On Sat, Jan 10, 2015 at 08:55:21PM -0800, Joe Perches wrote:
> > > On Sat, 2015-01-10 at 20:13 -0800, Greg Kroah-Hartman wrote:
> > > > On Sat, Jan 10, 2015 at 07:09:02PM
On 10/01/2015 08:48, Jerome Glisse wrote:
> On Thu, Jan 08, 2015 at 01:05:41PM +0200, Haggai Eran wrote:
>> On 06/01/2015 00:44, j.gli...@gmail.com wrote:
>>> + /* fence_wait() - to wait on device driver fence.
>>> +*
>>> +* @fence: The device driver fence struct.
>>> +* Returns: 0
On Sat, Jan 10, 2015 at 08:09:52PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, January 07, 2015 3:49 AM
> > To: Chao Yu
> > Cc: Changman Lee; linux-f2fs-de...@lists.sourceforge.net;
> >
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde [mailto:m...@pengutronix.de]
> Sent: Wednesday, January 07, 2015 5:59 PM
> To: Appana Durga Kedareswara Rao; w...@grandegger.com; Michal Simek;
> grant.lik...@linaro.org
> Cc: linux-...@vger.kernel.org; net...@vger.kernel.org; linux-
On Sat, 2015-01-10 at 21:24 -0800, Greg Kroah-Hartman wrote:
> On Sat, Jan 10, 2015 at 08:55:21PM -0800, Joe Perches wrote:
> > On Sat, 2015-01-10 at 20:13 -0800, Greg Kroah-Hartman wrote:
> > > On Sat, Jan 10, 2015 at 07:09:02PM -0800, Joe Perches wrote:
> > > > Use the normal logging facility
On Sat, Jan 10, 2015 at 08:08:33PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, January 07, 2015 3:44 AM
> > To: Chao Yu
> > Cc: Changman Lee; linux-f2fs-de...@lists.sourceforge.net;
> >
On Sat, Jan 10, 2015 at 08:55:21PM -0800, Joe Perches wrote:
> On Sat, 2015-01-10 at 20:13 -0800, Greg Kroah-Hartman wrote:
> > On Sat, Jan 10, 2015 at 07:09:02PM -0800, Joe Perches wrote:
> > > Use the normal logging facility instead of a new macro.
> > >
> > > Miscellanea:
> > >
> > > o
On Sat, 2015-01-10 at 20:13 -0800, Greg Kroah-Hartman wrote:
> On Sat, Jan 10, 2015 at 07:09:02PM -0800, Joe Perches wrote:
> > Use the normal logging facility instead of a new macro.
> >
> > Miscellanea:
> >
> > o Realign arguments
> > o Remove unnecessary alloc error messages as alloc failures
On Sat, Jan 10, 2015 at 07:09:02PM -0800, Joe Perches wrote:
> Use the normal logging facility instead of a new macro.
>
> Miscellanea:
>
> o Realign arguments
> o Remove unnecessary alloc error messages as alloc failures
> already emits a generic OOM message with a dump_stack
> o Add missing
From: "David A. Long"
Certain instructions are hard to execute correctly out-of-line (as in
kprobes). Test functions are added to insn.[hc] to identify these. The
instructions include any that use PC-relative addressing, change the PC,
or change interrupt masking. For efficiency and simplicity
From: Sandeepa Prabhu
Add support for basic kernel probes(kprobes) and jump probes
(jprobes) for ARM64.
Kprobes will utilize software breakpoint and single step debug
exceptions supported on ARM v8.
Software breakpoint is placed at the probe address to trap the
kernel execution into kprobe
From: Sandeepa Prabhu
Add support for AArch64 instruction simulation in kprobes.
Kprobes needs simulation of instructions that cannot be stepped
from different memory location, e.g.: those instructions
that uses PC-relative addressing. In simulation, the behaviour
of the instruction is
From: Sandeepa Prabhu
AArch64 ISA does not have instructions to pop the PC register
value from the stack(like ARM v7 has ldmia {...,pc}) without using
one of the general purpose registers. This means return probes
cannot return to the actual return address directly without
modifying register
From: "David A. Long"
This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches,
first
seen in October 2013. This version attempts to address concerns raised by
reviewers and also fixes problems discovered during testing, particularly during
SMP testing.
This patchset adds
From: Sandeepa Prabhu
Add info prints in sample kprobe handlers for ARM64
Signed-off-by: Sandeepa Prabhu
---
samples/kprobes/kprobe_example.c | 8
1 file changed, 8 insertions(+)
diff --git a/samples/kprobes/kprobe_example.c b/samples/kprobes/kprobe_example.c
index 366db1a..51d459c
From: "David A. Long"
Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64.
Signed-off-by: David A. Long
---
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/ptrace.h | 29 +
arch/arm64/include/uapi/asm/ptrace.h | 36 +++
arch/arm64/kernel/ptrace.c
Hi,
This patch set adds AEAD and RNG support to the AF_ALG interface
exported by the kernel crypto API. By extending AF_ALG with AEAD and RNG
support, all cipher types the kernel crypto API allows access to are
now accessible from userspace.
Both, AEAD and RNG implementations are stand-alone and
This patch adds the AEAD support for AF_ALG.
The implementation is based on algif_skcipher, but contains heavy
modifications to streamline the interface for AEAD uses.
To use AEAD, the user space consumer has to use the salg_type named
"aead".
The AEAD implementation includes some overhead to
Enable compilation of the AEAD AF_ALG support and provide a Kconfig
option to compile the AEAD AF_ALG support.
Signed-off-by: Stephan Mueller
---
crypto/Kconfig | 9 +
crypto/Makefile | 1 +
2 files changed, 10 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index
At Fri, 9 Jan 2015 09:59:10 -0800,
Guenter Roeck wrote:
>
> On Fri, Jan 09, 2015 at 11:30:32AM +0100, Jiri Slaby wrote:
> > This is the start of the stable review cycle for the 3.12.36 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If anyone
On Sat, Jan 10, 2015 at 11:41 PM, Borislav Petkov wrote:
> On Sat, Jan 10, 2015 at 11:35:58PM +0100, Denys Vlasenko wrote:
>> I don't know either... it seems to be used after push_cfi
>> *sometimes*, not always:
>>
>> .macro op_safe_regs op
>> ENTRY(\op\()_safe_regs)
>> CFI_STARTPROC
>>
Added git url for UIO section.
Signed-off-by: Mandeep Sandhu
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddb9ac8..13fa3b7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10146,6 +10146,7 @@ USERSPACE I/O (UIO)
M: "Hans J. Koch"
M:
Added git url for UIO section.
Mandeep Sandhu (1):
MAINTAINERS: add git url entry for UIO
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Use the normal logging facility instead of a new macro.
Miscellanea:
o Realign arguments
o Remove unnecessary alloc error messages as alloc failures
already emits a generic OOM message with a dump_stack
o Add missing newlines to these messages to avoid interleaving
o Spelling/typo fixes in
Rich Felker writes:
> On Sat, Jan 10, 2015 at 04:27:23PM -0600, Eric W. Biederman wrote:
>> Rich Felker writes:
>>
>> > On Sat, Jan 10, 2015 at 04:14:57AM +, Al Viro wrote:
>>
>> >> Except that if your interpreter does stat(2) (or access(2), or
>> >> getxattr(2),
>> >> etc.) before
Thomas,
Here's a round of fixes for v3.19. Nothing too exciting or
controversial (other than I'm a bit behind due to the holidays and
such).
Please pull.
thx,
Jason.
The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
cpu_is_at91* are not used in any driver outside mach-at91. Remove those useless
definitions.
Signed-off-by: Alexandre Belloni
---
Hans-Christian,
If you want, I guess that one could go through the at91 tree. Unless you have
more material and you want to do a pull request for 3.20.
Regards,
I'm wondering if there is a need for this to be a platform driver at
all. Could we, instead, tear down any unlocked IMRs at boot as part of the IMR
driver itself, as well as lock the kernel .text. Firmware has the option of
making an IMR mandatory by locking it. If it isn't locked, what use is
On Sun, Jan 11, 2015 at 01:33:35AM +, Carlos R. Mafra wrote:
> I think the problem with wmnet is not that it was expecting the fields
> to be aligned because it never had problems before (when definitely more
> than 10 megabytes were received, wmnet is crappy but not _that_ crappy).
>
> I
On 01/09/2015 08:03 AM, Bartosz Golaszewski wrote:
This attribute allows to configure the update interval of ina226. Although
the bus and shunt voltage conversion times remain hardcoded to 1.1 ms, we can
now modify said interval by changing the averaging rate.
While we're at it - add an
On Sun, 11 Jan 2015 at 1:00:36 +, Al Viro wrote:
> On Sun, Jan 11, 2015 at 12:27:06AM +, Al Viro wrote:
> > On Sat, Jan 10, 2015 at 11:25:18PM +, Carlos R. Mafra wrote:
> > > [mafra@linux-g29b:wmnet]$ cat net_dev_bad.txt
> > > Inter-| Receive
On Sat, Jan 10, 2015 at 04:27:23PM -0600, Eric W. Biederman wrote:
> Rich Felker writes:
>
> > On Sat, Jan 10, 2015 at 04:14:57AM +, Al Viro wrote:
>
> >> Except that if your interpreter does stat(2) (or access(2), or getxattr(2),
> >> etc.) before bothering with open(2), you'll get
On 01/10/2015 10:41 AM, Alexandre Belloni wrote:
On 09/01/2015 at 16:39:21 -0800, Guenter Roeck wrote :
On 01/09/2015 01:51 AM, Alexandre Belloni wrote:
/* .
*/
@@ -204,6 +201,7 @@ static struct miscdevice
On Sun, Jan 11, 2015 at 12:27:06AM +, Al Viro wrote:
> On Sat, Jan 10, 2015 at 11:25:18PM +, Carlos R. Mafra wrote:
> > [mafra@linux-g29b:wmnet]$ cat net_dev_bad.txt
> > Inter-| Receive| Transmit
> > face |bytespackets errs drop fifo
On Sun, 11 Jan 2015 at 0:27:06 +, Al Viro wrote:
> On Sat, Jan 10, 2015 at 11:25:18PM +, Carlos R. Mafra wrote:
> > [mafra@linux-g29b:wmnet]$ cat net_dev_bad.txt
> > Inter-| Receive| Transmit
> > face |bytespackets errs drop fifo
If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
unplugged, an -ENODEV (19) error will be produced after it gives up
trying to resubmit a read.
usb_serial_generic_submit_read_urb - usb_submit_urb failed: -19
Add -ENODEV as one of the permanent errors along with -EPERM that
If a USB serial device is unplugged while there is an active program
using the device it will spam the logs with -EPROTO (71) messages as it
attempts to retry.
Most serial usb drivers (metro-usb, pl2303, mos7840, ...) only output
these messages for debugging. The generic driver treats these as
(Jan 15) Just a resend of v2 [1].
[1]: https://lkml.org/lkml/2014/12/20/16
If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
unplugged, a bunch of -ENODEV and -EPROTO errors will be produced in the
logs. This patch set quiets these messages without changing the
original
On Sat, Jan 10, 2015 at 11:25:18PM +, Carlos R. Mafra wrote:
> [mafra@linux-g29b:wmnet]$ cat net_dev_bad.txt
> Inter-| Receive| Transmit
> face |bytespackets errs drop fifo frame compressed multicast|bytes
> packets errs drop fifo
Commit 45e2a9d4701d8c624d4a4bcdd1084eae31e92f58 ("x86, mm: Set NX across
entire PMD at boot") has been backported to many stable branches:
v3.10.62: 0b15c16c4f4a x86, mm: Set NX across entire PMD at boot
v3.12.35: 868b19cb0314 x86, mm: Set NX across entire PMD at boot
v3.14.26: 1a829c59816e x86,
Hi,
On Mon, 11 Aug 2014 06:45:24 + wrote:
> Would you please try this patch. If it does work, we will submit it to
> upstream kernel.
I own a Lenovo Thinkpad T440s as well just as the original bug submitter
(Philipp) and that patch by Wei does not fix the problem for me (I applied it
to a
On Sat, Jan 10, 2015 at 11:57:04PM +, Scot Doyle wrote:
> Steven, are you planning to resubmit the patch as suggested by Borislav?
I think he did resubmit:
https://lkml.kernel.org/r/1415227938-16927-1-git-send-email-stevenhoney...@gmail.com
but it seems it has been forgotten. I'll pick it
On Sat, 10 Jan 2015, Joe Perches wrote:
> On Sat, 2015-01-10 at 22:21 +, Scot Doyle wrote:
> > Call printk twice since this log entry has two lines and headings.
> >
> > [0.009285] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
> > Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB
> From: Yunzhi Li [mailto:l...@rock-chips.com]
> Sent: Saturday, January 10, 2015 8:07 AM
>
> 在 2015/1/9 10:15, Paul Zimmerman 写道:
> >> [...]
> >>/*
> >> - * Attempt to find a generic PHY, then look for an old style
> >> - * USB PHY, finally fall back to pdata
> >> + * If platform probe
On Sat, Jan 10, 2015 at 2:27 PM, Linus Torvalds
wrote:
> On Sat, Jan 10, 2015 at 2:13 PM, Andy Lutomirski wrote:
>>
>> I'll make the same change to my pending entry work, and hopefully we
>> can avoid conflicts.
>
> That's not how conflicts work.
>
> Either there is no overlap between the
I use a dockapp called 'wmnet' [1] to monitor the speed of
my internet connection and after the kernel v3.18 it does no
longer work properly (it still doesn't work in v3.19-rc3)
I bisected the problem and the culprit is this commit:
commit 6e094bd805a9b6ad2f5421125db8f604a166616c
Author: Rafał
On Sat, Jan 10, 2015 at 11:25:39PM +0100, Martin Steigerwald wrote:
> > ... and this, boys and girls, is why quite a few of us have loathed udev
> > way before it got merged into even nastier shitpile. Still do, for that
> > matter.
>
> You mean systemd by that?
Yes, I do. Has it been merged
Hi,
On Sat, Jan 10, 2015 at 09:18:05PM +, Al Viro wrote:
> On Sat, Jan 10, 2015 at 09:13:35PM +0200, Aaro Koskinen wrote:
> > On Sat, Jan 10, 2015 at 06:39:20PM +0100, Pavel Machek wrote:
> > > N900 has real problems on 3.19, and 2.6.28 should be very well
> > > debugged version. Getting it
On Sat 2015-01-10 21:18:05, Al Viro wrote:
> On Sat, Jan 10, 2015 at 09:13:35PM +0200, Aaro Koskinen wrote:
> > Hi,
> >
> > On Sat, Jan 10, 2015 at 06:39:20PM +0100, Pavel Machek wrote:
> > > N900 has real problems on 3.19, and 2.6.28 should be very well
> > > debugged version. Getting it to
On Sat, Jan 10, 2015 at 02:41:07PM -0800, Linus Torvalds wrote:
> On Sat, Jan 10, 2015 at 2:35 PM, Borislav Petkov wrote:
> >
> > Haha, Linus just made you maintainer of entry_64.S :-)
>
> Just going by
>
> git shortlog --no-merges --since=6.months arch/x86/kernel/entry_64.S
>
> and
On Sat, Jan 10, 2015 at 11:35:58PM +0100, Denys Vlasenko wrote:
> I don't know either... it seems to be used after push_cfi
> *sometimes*, not always:
>
> .macro op_safe_regs op
> ENTRY(\op\()_safe_regs)
> CFI_STARTPROC
> pushl_cfi %ebx
> pushl_cfi %ebp
> pushl_cfi
On Sat, Jan 10, 2015 at 2:35 PM, Borislav Petkov wrote:
>
> Haha, Linus just made you maintainer of entry_64.S :-)
Just going by
git shortlog --no-merges --since=6.months arch/x86/kernel/entry_64.S
and looking at the kind of changes are going on, I really think a
"tag, you're it" to Andy
On Sat, Jan 10, 2015 at 2:27 PM, Linus Torvalds
wrote:
>
> So the only way to avoid a conflict is to not touch the same code, or
> to touch it *exactly* the same way in all respects.
.. with the caveat that the exact definition of "overlap" can end up
being somewhat fuzzy with the whole conflict
On Sat, Jan 10, 2015 at 11:07 PM, Linus Torvalds
wrote:
> On Sat, Jan 10, 2015 at 2:00 PM, Denys Vlasenko wrote:
>> + pushq_cfi %rdi
>> + CFI_REL_OFFSET rdi, 0
>> + pushq_cfi %rsi
>> + CFI_REL_OFFSET rsi, 0
>> + pushq_cfi %rdx
>> + CFI_REL_OFFSET rdx, 0
> ..
>
On Sat, 2015-01-10 at 22:21 +, Scot Doyle wrote:
> Call printk twice since this log entry has two lines and headings.
>
> [0.009285] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
> Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
>
> Signed-off-by: Scot Doyle
> ---
>
On Sat, Jan 10, 2015 at 02:27:06PM -0800, Linus Torvalds wrote:
> I I do actually agree with you taking the fixes (and maybe you should
> *entirely* take ownership of all the entry_64.S changes, so that there
> is no "other side" to conflict with at all!). I just wanted to point
> out the actual
On 01/10/2015 12:59 PM, Linus Torvalds wrote:
On Fri, Jan 9, 2015 at 9:54 AM, Jens Axboe wrote:
Please pull!
You've completely screwed up your pull request. You ask me to pull,
but you don't mention where from!
Oops, looks like I cut a line too much from the request-pull output.
This is
Rich Felker writes:
> On Sat, Jan 10, 2015 at 04:14:57AM +, Al Viro wrote:
>> Except that if your interpreter does stat(2) (or access(2), or getxattr(2),
>> etc.) before bothering with open(2), you'll get screwed.
>
> Yes, but I think that would be very bad interpreter design.
>
On Sat, Jan 10, 2015 at 2:13 PM, Andy Lutomirski wrote:
>
> I'll make the same change to my pending entry work, and hopefully we
> can avoid conflicts.
That's not how conflicts work.
Either there is no overlap between the changes at all, in which case
it doesn't matter if you then also have
Am Samstag, 10. Januar 2015, 21:18:58 schrieb Al Viro:
> On Sat, Jan 10, 2015 at 10:17:10AM -0800, Greg KH wrote:
> > > > Yes, 3.18, please use that instead.
> > >
> > > Can't, sorry. My goal is to get 3.18/3.19 working, but I really need
> > > working kernel to debug userland (and then use that
Call printk twice since this log entry has two lines and headings.
[0.009285] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
Signed-off-by: Scot Doyle
---
arch/x86/kernel/cpu/common.c | 10 +-
1 file changed, 5
On 07/01/15 16:03, Opensource [Adam Thomson] wrote:
> On January 4, 2015 17:22, Jonathan Cameron wrote:
>
>> On 22/12/14 16:51, Adam Thomson wrote:
>>> This patch adds support for DA9150 Charger & Fuel-Gauge IC GPADC.
>>>
>>> Signed-off-by: Adam Thomson
>> One last query from me.
>>
>> Using the
Hi Moritz,
On Fri, Jan 09, 2015 at 12:59:29AM +0100, Moritz Fischer wrote:
> +static struct platform_driver e3x0_button_driver = {
> + .driver = {
> + .name = "e3x0-button",
> + .of_match_table = of_match_ptr(e3x0_button_match),
You forgot to assign .pm
On Sat, Jan 10, 2015 at 2:00 PM, Denys Vlasenko wrote:
> The values of these two constants are the same, the meaning is different.
Acked-by: Andy Lutomirski
I'll make the same change to my pending entry work, and hopefully we
can avoid conflicts.
--Andy
>
> Signed-off-by: Denys Vlasenko
>
On Sat, Jan 10, 2015 at 2:00 PM, Denys Vlasenko wrote:
> A define, two macros and an unreferenced bit of assembly are gone.
Acked-by: Andy Lutomirski
>
> Signed-off-by: Denys Vlasenko
> Acked-by: Borislav Petkov
> CC: Linus Torvalds
> CC: Oleg Nesterov
> CC: "H. Peter Anvin"
> CC:
On 08/01/15 10:47, Lars-Peter Clausen wrote:
> On 01/07/2015 07:36 PM, Karol Wrona wrote:
>> There was a need for non triggered software buffer type. It can be used when
>> triggered model does not fit and INDIO_BUFFER_HARDWARE causes confusion
>> because
>> the data stream can be obtained not
On 01/11/2015 12:05 AM, Oded Gabbay wrote:
>
>
> On 01/10/2015 11:50 PM, Eric Dumazet wrote:
>> On Sat, 2015-01-10 at 23:30 +0200, Oded Gabbay wrote:
>>
>>> Yes, no problem.
>>> I will update on the result.
>>
>> Please try this more complete patch, solving the TX pressure problem as
>> well,
To support dynamic addition and removal of
me clients we add reference counter.
Update kdoc with locking requirements.
Signed-off-by: Tomas Winkler
---
V2: add locking requirements to kdoc
V3: fix warning: 'cb/me_cl' may be used uninitialized in this function
drivers/misc/mei/amthif.c | 14
Hi Omar,
On Thu, Jan 8, 2015 at 4:18 AM, Omar Sandoval wrote:
> Most filesystems prevent truncation of an active swapfile by way of
> inode_newsize_ok, called from inode_change_ok. NFS doesn't call either
> from nfs_setattr, presumably because most of these checks are expected
> to be done
On Sat, Jan 10, 2015 at 2:00 PM, Denys Vlasenko wrote:
> + pushq_cfi %rdi
> + CFI_REL_OFFSET rdi, 0
> + pushq_cfi %rsi
> + CFI_REL_OFFSET rsi, 0
> + pushq_cfi %rdx
> + CFI_REL_OFFSET rdx, 0
..
Ugh.
This is too ugly, it needs to die.
Why doesn't pushq_cfi do
On 01/10/2015 11:50 PM, Eric Dumazet wrote:
> On Sat, 2015-01-10 at 23:30 +0200, Oded Gabbay wrote:
>
>> Yes, no problem.
>> I will update on the result.
>
> Please try this more complete patch, solving the TX pressure problem as
> well, and not lying about NAPI budget. thanks !
>
>
> diff
On Sat, Jan 10, 2015 at 2:00 PM, Borislav Petkov wrote:
> On Sat, Jan 10, 2015 at 09:14:03PM +0100, Denys Vlasenko wrote:
>> From 2f636e0a92db898f2bdb592027aa302fcb32a326 Mon Sep 17 00:00:00 2001
>> From: Denys Vlasenko
>> To: linux-kernel@vger.kernel.org
>> Subject: [PATCH 3/4] x86: open-code
On Sat, Jan 10, 2015 at 11:00 PM, Borislav Petkov wrote:
>> --- a/arch/x86/lib/thunk_64.S
>> +++ b/arch/x86/lib/thunk_64.S
>> @@ -17,9 +17,27 @@
>> CFI_STARTPROC
>>
>> /* this one pushes 9 elems, the next one would be %rIP */
>> - SAVE_ARGS
>> + pushq_cfi %rdi
>> +
On Sat, Jan 10, 2015 at 09:14:03PM +0100, Denys Vlasenko wrote:
> From 2f636e0a92db898f2bdb592027aa302fcb32a326 Mon Sep 17 00:00:00 2001
> From: Denys Vlasenko
> To: linux-kernel@vger.kernel.org
> Subject: [PATCH 3/4] x86: open-code register save/restore in trace_hardirqs
> thunks
>
> This is a
A define, two macros and an unreferenced bit of assembly are gone.
Signed-off-by: Denys Vlasenko
Acked-by: Borislav Petkov
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Borislav Petkov
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
CC: Will
> >
> > Signed-off-by: Tomas Winkler
>
> This patch adds build warnings, I can't take it:
>
> drivers/misc/mei/bus.c: In function ‘___mei_cl_send’:
> drivers/misc/mei/bus.c:276:3: warning: ‘cb’ may be used uninitialized in this
> function [-Wmaybe-uninitialized]
>mei_io_cb_free(cb);
>^
This is a preparatory patch for change in "struct pt_regs"
handling in entry_64.S.
trace_hardirqs thunks were (ab)using a part of pt_regs
handling code, namely SAVE_ARGS/RESTORE_ARGS macros,
to save/restore registers across C function calls.
Since SAVE_ARGS is going to be changed, open-code
No code changes.
This is a preparatory patch for change in "struct pt_regs" handling.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Borislav Petkov
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
CC: Will Drewry
This is the first part of a bigger patch set I posted last August,
then under title of "x86: entry.S optimizations".
I fully rebased that patch set to Linus tree, but currently
Linus and -next are diverging a bit in arch/x86/kernel/entry_64.S
To make it easier for mainteiners, I'm splitting the
The values of these two constants are the same, the meaning is different.
Signed-off-by: Denys Vlasenko
Acked-by: Borislav Petkov
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Borislav Petkov
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
On Sat, Jan 10, 2015 at 10:27 PM, Linus Torvalds
wrote:
> On Sat, Jan 10, 2015 at 1:09 PM, Denys Vlasenko
> wrote:
>>
>> I think using push/pop is okay. In the very hottest code paths
>> you may want to prefer mov's.
>
> For kernel entrypoints in particular, the code sequence is quite
> possibly
On Saturday 10 January 2015 22:40:22 Linus Walleij wrote:
> > static int v3_read_config(struct pci_bus *bus, unsigned int devfn, int
> > where,
> > int size, u32 *val)
> > {
> > - addr = v3_open_config_window(bus, devfn, where);
> > + int ret =
Adds a new set of functions to deal with scatter gather.
ubi_eba_read_leb_sg() will read from a LEB into a scatter gather list.
The new data structure struct ubi_sgl will be used within UBI to
hold the scatter gather list itself and metadata to have a cursor
within the list.
Signed-off-by:
Convert the driver to blk-mq.
Beside of moving to the modern block interface this change boosts
also the performance of the driver.
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron NAND 256MiB 3,3V 8-bit
nand: 256MiB, SLC, page size: 2048, OOB size: 64
root@debian-armhf:~#
Am 10.01.2015 um 19:58 schrieb Christoph Hellwig:
>> +struct ubiblock_pdu {
>> +struct request *req;
>
> No need to store the request, you can trivially get at it using
> blk_mq_rq_from_pdu().
Very handy, I was not aware of blk_mq_rq_from_pdu().
>> +struct ubiblock *dev;
>
> Why do you
When drivers are compiled in subdirectories the -DDEBUG flag need
to be passed in the individual Makefiles.
Reported-by: Mika Westerberg
Suggested-by: Yingjoe Chen
Cc: Mika Westerberg
Signed-off-by: Linus Walleij
---
This replaces Mika's patch too.
---
drivers/pinctrl/Makefile | 2 +-
1 file
On Sat, 2015-01-10 at 23:30 +0200, Oded Gabbay wrote:
> Yes, no problem.
> I will update on the result.
Please try this more complete patch, solving the TX pressure problem as
well, and not lying about NAPI budget. thanks !
diff --git a/drivers/net/ethernet/atheros/alx/main.c
On Sat, Jan 10, 2015 at 1:36 PM, Arnd Bergmann wrote:
>>
>> (d) the powerpc TLB fill/buildup/teardown costs are horrible, so on
>> AIX the cost of lots of small pages is much higher too.
>
> I think (d) applies to ARM as well, since it has no hardware
> dirty/referenced bit tracking and requires
On Fri, Jan 9, 2015 at 11:22 AM, Yingjoe Chen wrote:
>
> On Fri, 2015-01-09 at 10:41 +0100, Linus Walleij wrote:
>> When drivers are compiled in subdirectories the -DDEBUG flag need
>> to be passed in the individual Makefiles.
>
> Hi,
>
> It will be easy to forget adding this when adding new
On 01/10/2015 11:30 PM, Oded Gabbay wrote:
>
>
> On 01/10/2015 10:58 PM, Eric Dumazet wrote:
>> On Sat, 2015-01-10 at 22:39 +0200, Oded Gabbay wrote:
>>> Hi,
>>>
>>> Commit d75b1ade567ffab085e8adbbdacf0092d10cd09c breaks my "Qualcomm Atheros
>>> AR8161 Gigabit Ethernet (rev 10)" Ethernet
Currently, if a hierarchy doesn't have any live children when it's
unmounted, the hierarchy starts dying by killing its refcnt. The
expectation is that even if there are lingering dead children which
are lingering due to remaining references, they'll be put in a finite
amount of time. When the
On Sat, Jan 10, 2015 at 3:34 AM, Rob Herring wrote:
> Convert the integrator PCI driver to use the generic config access
> functions.
>
> This changes accesses from __raw_readX/__raw_writeX to readX/writeX
> variants.
Just as good.
> The spinlock is removed because it is unnecessary. The
On Saturday 10 January 2015 13:00:27 Linus Torvalds wrote:
>
> > IIRC, AIX works great with 64k pages, but only because of two
> > reasons that don't apply on Linux:
>
> .. there's a few other ones:
>
> (c) nobody really runs AIX on dekstops. It's very much a DB load
> environment, with
On Tue, Dec 2, 2014 at 2:55 PM, Sascha Hauer wrote:
Sorry for taking eternities to get back on this, I ran into a merge window
and some christmas. I do hope we can resolve this in the current
development cycle so we can get this support in.
> On Fri, Nov 28, 2014 at 05:12:44PM +0100, Linus
On 01/10/2015 10:58 PM, Eric Dumazet wrote:
> On Sat, 2015-01-10 at 22:39 +0200, Oded Gabbay wrote:
>> Hi,
>>
>> Commit d75b1ade567ffab085e8adbbdacf0092d10cd09c breaks my "Qualcomm Atheros
>> AR8161 Gigabit Ethernet (rev 10)" Ethernet controller, which is handled by
>> the alx network driver.
>>
TL;DR:
media: cx23885 broken by commit 453afdd9ce33293f640e84dc17e5f366701516e8
"[media] cx23885: convert to vb2"
Broken mean: until this commit driver was rock solid, after I started to
receive
IOMMU related warnings and sometimes card stopped working
Full report:
On 09.01.2015 10:34,
Commit 6dda730e55f4 introduced a bug which resulted in inconsistent
brightness levels on different machines. If a suspended was entered
with the screen off some machines would resume with the screen
at minimum brightness and others at maximum brightness.
The following commands can be used to
On Sat, Jan 10, 2015 at 1:09 PM, Denys Vlasenko
wrote:
>
> I think using push/pop is okay. In the very hottest code paths
> you may want to prefer mov's.
For kernel entrypoints in particular, the code sequence is quite
possibly constrained by the decoder and instruction fetch rather than
the
On Sat, Jan 10, 2015 at 01:08:33PM -0800, Linus Torvalds wrote:
> It was true for some AMD CPU's in particular. One insn/cycle vs two.
Probably on K8: Agner Fog's insn tables show reciprocal throughput of
1/2 for MOV r64/m64 vs 1 for PUSH/POP.
> I personally would be very happy to go back to
On Sat, Jan 10, 2015 at 10:17:10AM -0800, Greg KH wrote:
> > > Yes, 3.18, please use that instead.
> >
> > Can't, sorry. My goal is to get 3.18/3.19 working, but I really need
> > working kernel to debug userland (and then use that userland to debug
> > kernel).
> >
> > > Seriously, lots of
1 - 100 of 476 matches
Mail list logo
