On 02/26, Lorenzo Pieralisi wrote:
> On Tue, Feb 25, 2014 at 08:48:38PM +, Kumar Gala wrote:
> >
> > On Feb 25, 2014, at 5:16 AM, Lorenzo Pieralisi
> > wrote:
> > >
> > > As I mentioned, I do not like the idea of adding compatible properties
> > > just to force the kernel to create
On Fri, 2014-03-07 at 09:28PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:27 -0800
> Soren Brinkmann wrote:
>
> > Signed-off-by: Soren Brinkmann
> > ---
> > drivers/tty/serial/xilinx_uartps.c | 6 +-
> > 1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git
Commit-ID: d4078e232267ff53f3b030b9698a3c001db4dbec
Gitweb: http://git.kernel.org/tip/d4078e232267ff53f3b030b9698a3c001db4dbec
Author: Peter Zijlstra
AuthorDate: Wed, 5 Mar 2014 14:07:49 +0100
Committer: H. Peter Anvin
CommitDate: Thu, 6 Mar 2014 10:58:18 -0800
x86, trace: Further
On Sat, Mar 08, 2014 at 12:29:49AM +0200, Stanimir Vabanov wrote:
> > +#define BAM_IRQ_SRCS_EE(pipe) (0x0800 + ((pipe) * 0x80))
> > +#define BAM_IRQ_SRCS_MSK_EE(pipe) (0x0804 + ((pipe) * 0x80))
>
> s/pipe/ee ?
>
Ah good catch. I'll fix that.
> > +struct bam_chan {
> > + struct
On Fri, Mar 7, 2014 at 1:53 PM, Stefani Seibold wrote:
>
> Am Freitag, den 07.03.2014, 10:56 -0800 schrieb Andy Lutomirski:
>> On Thu, Mar 6, 2014 at 11:21 PM, Stefani Seibold wrote:
>> > Hi Fengguang,
>> >
>> > i have build a kernel with the config, but my kvm is unable to start it.
>> > I will
On Fri, Mar 07, 2014 at 01:30:17PM -0800, j...@joshtriplett.org wrote:
> On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > From: Alistair Popple
> > > Date: Thu, 6 Mar 2014 14:52:25 +1100
> > >
> > > > +
On Fri, 2014-03-07 at 09:30PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:31 -0800
> Soren Brinkmann wrote:
>
> > Rename the config symbols for the Cadence UART to reflect the driver
> > rebranding:
> > SERIAL_XILINX_PS_UART(_CONSOLE) -> SERIAL_CADENCE_UART(_CONSOLE)
>
>
On Fri, 2014-03-07 at 09:29PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:29 -0800
> Soren Brinkmann wrote:
>
> > Signed-off-by: Soren Brinkmann
> > ---
> > I'm not sure about this change. Is this acceptable or already too much?
> > I think the name is used for some sysfs
On Fri, Mar 07, 2014 at 01:15:35PM -0800, H. Peter Anvin wrote:
> On 03/07/2014 11:39 AM, Don Zickus wrote:
> > A customer generated an external NMI using their iLO to test kdump worked.
> > Unfortunately, the machine hung. Disabling the nmi_watchdog made things
> > work.
> >
> > I speculated
On Fri, Mar 07, 2014 at 11:04:29PM +0100, Manuel Krause wrote:
> On 2014-03-07 21:55, Guenter Roeck wrote:
> >On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
> >>Please have a short look at the following BUG report + the comments
> >>-- this message here is a kind of FWD-ing it:
>
As usual Eric, your commentary is anything but useful. However your
technical thoughts are not off the mark. Can we stick to those?
On Wed, 2014-03-05 at 10:06 -0800, Eric W. Biederman wrote:
> Steve Grubb writes:
>
> > On Tuesday, March 04, 2014 07:21:52 PM David Miller wrote:
> >> From:
On 7.3.2014 1:33, Andrew Morton wrote:
On Thu, 6 Mar 2014 10:21:32 -0800 Laura Abbott wrote:
We received several reports of bad page state when freeing CMA pages
previously allocated with alloc_contig_range:
<1>[ 1258.084111] BUG: Bad page state in process Binder_A pfn:63202
<1>[
From: Borislav Petkov
The name in struct bootparam is ->initrd_addr_max and not ramdisk_max.
Fix that.
Signed-off-by: Borislav Petkov
---
Documentation/x86/boot.txt | 4 ++--
arch/x86/boot/header.S | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On Fri, Mar 07, 2014 at 05:27:43PM -0500, Dave Jones wrote:
> When I wrote it 10 years or so back it made more sense than it
> probably does now, so I'd be ok with just dropping it all too tbh.
> Machines of that vintage probably have bigger problems now anyway.
Yeah.
> I don't recall seeing a
On 6.3.2014 19:21, Laura Abbott wrote:
We received several reports of bad page state when freeing CMA pages
previously allocated with alloc_contig_range:
<1>[ 1258.084111] BUG: Bad page state in process Binder_A pfn:63202
<1>[ 1258.089763] page:d21130b0 count:0 mapcount:1 mapping: (null)
On Sat, Mar 08, 2014 at 06:27:50AM +0800, Fengguang Wu wrote:
> Yeah I confirmed that it works w/o the warning!
>
> [0.575854] smpboot: CPU0: Intel Core Processor (Haswell) (fam: 06, model:
> 3c, stepping: 01)
Hahah, Haswell is just a couple models away from K7: model 6 vs
model 3c, same
On Fri, Mar 07, 2014 at 02:11:50PM -0800, H. Peter Anvin wrote:
> On 03/07/2014 02:06 PM, Dave Jones wrote:
> > On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
> >
> > > * Another option would be if we change the f/m/s of "qemu64" so that
> > > the test doesn't fire.
> > >
>
On Fri, Mar 07, 2014 at 11:20:18PM +0100, Borislav Petkov wrote:
> Yeah, I think the test in the kernel is open above as a precaution in
> case newer models appeared:
>
> if (((c->x86_model == 6) && (c->x86_mask >= 2)) ||
>
> I hardly can imagine, though, if anyone is actually
Hi Andy,
Thanks for the patch.
> +#define BAM_IRQ_SRCS_EE(pipe)(0x0800 + ((pipe) * 0x80))
> +#define BAM_IRQ_SRCS_MSK_EE(pipe)(0x0804 + ((pipe) * 0x80))
s/pipe/ee ?
> +struct bam_chan {
> + struct virt_dma_chan vc;
> +
> + struct bam_device *bdev;
> +
> + /*
On Fri, Mar 07, 2014 at 05:06:55PM -0500, Dave Jones wrote:
> Additionally, fam:6 model:6 stepping 3 never existed in the real
> world afaict. I used to keep x86info's stepping db pretty up to date,
> and that only has knowledge of stepping 1 & 2.[*] Modelling qemu on
> something from the real
On Fri, Mar 07, 2014 at 02:11:50PM -0800, H. Peter Anvin wrote:
> > > * Another option would be if we change the f/m/s of "qemu64" so that
> > > the test doesn't fire.
> > >
> > > What also makes me wonder is why is this thing even called qemu64?? AMD
> > > family 6 was 32-bit only
On Fri, Mar 7, 2014 at 12:38 PM, David Miller wrote:
> From: Alexei Starovoitov
> Date: Wed, 5 Mar 2014 19:30:15 -0800
>
>> Extended BPF extends old BPF in the following ways:
>> - from 2 to 10 registers
>> Original BPF has two registers (A and X) and hidden frame pointer.
>> Extended BPF
On 03/07/2014 02:06 PM, Dave Jones wrote:
> On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
>
> > * Another option would be if we change the f/m/s of "qemu64" so that
> > the test doesn't fire.
> >
> > What also makes me wonder is why is this thing even called qemu64?? AMD
>
Fully agree.
It will be a very helpful feature to make ple setting per VM.
This feature will provide more flexible control to the VM user. All KVM user
will love to have it.
The enhancement we proposed is neither overlapping nor conflicting with this
feature. The enhancement is targeting to
On Fri, Mar 7, 2014 at 2:03 PM, Paul Bolle wrote:
> On Fri, 2014-03-07 at 13:40 -0700, Bjorn Helgaas wrote:
>> It seems quite possible that I broke pci_bus_alloc_resource(), which could
>> cause an allocation failure like this.
>>
>> If you have a chance to try it, here's a debug patch against
On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
> * Another option would be if we change the f/m/s of "qemu64" so that
> the test doesn't fire.
>
> What also makes me wonder is why is this thing even called qemu64?? AMD
> family 6 was 32-bit only CPUs so 64 is kinda wrong
On 2014-03-07 21:55, Guenter Roeck wrote:
On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
Please have a short look at the following BUG report + the comments
-- this message here is a kind of FWD-ing it:
https://bugs.archlinux.org/task/39005
I came late to test kernel 3.13 with
> - The renderer supports *any* RGB target, from 8bit to 32bit with
>big-endian and little-endian support. The related pixel-renderer will
>probably never win a beauty-contest, but it works.. Again, who cares
>for debug-log rendering speed?
Debug log writing performance is extremely
Hello,I know this mail seems you in a good form,lets see what future has in
store,please contact me soonest marisa_...@yahoo.com Thanks marisa
--
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
Am Freitag, den 07.03.2014, 10:56 -0800 schrieb Andy Lutomirski:
> On Thu, Mar 6, 2014 at 11:21 PM, Stefani Seibold wrote:
> > Hi Fengguang,
> >
> > i have build a kernel with the config, but my kvm is unable to start it.
> > I will try to find a way to test your kernek config.
> >
> > One thing
-statfs(2) /undefined
-Don't recalculate f_frsize and f_bavail.
-Remove ?? comment.
-Use defined CEPH_BLOCK.
-Directly work with >> 12 for 4Kb conversions (like in dir.c)
Signed-off-by: Fabian Frederick
---
fs/ceph/super.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
From: "K. Y. Srinivasan"
Date: Thu, 6 Mar 2014 21:32:36 -0800
> +static u32 fill_pg_buf(struct page *page, u32 offset, u32 len,
> + struct hv_page_buffer *pb)
> +{
> + int j = 0;
> +
> + /* Deal with compund pages by ignoring unused part
> + * of the page.
> +
On Fri, 2014-03-07 at 13:30 -0800, j...@joshtriplett.org wrote:
> On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > From: Alistair Popple
> > > Date: Thu, 6 Mar 2014 14:52:25 +1100
> > >
> > > > +
On Thu, 6 Mar 2014 18:23:39 +0100
Andrew Lunn wrote:
> > Can't we fix this so the probe order doesn't affect the name?
> >
> > Is that sane?
>
> You are not supposed to trust the device name, since probing can
> happen in parallel, on different buses. udev should have rules to name
> the
From: Jason Wang
Date: Fri, 7 Mar 2014 13:28:27 +0800
> This is because the delay added by htb may lead the delay the finish
> of DMAs and cause the pending DMAs for tap0 exceeds the limit
> (VHOST_MAX_PEND). In this case vhost stop handling tx request until
> htb send some packets. The problem
+ Paolo.
(drop Andreas' old, invalid now email).
On Fri, Mar 07, 2014 at 01:01:22PM -0800, H. Peter Anvin wrote:
> > qemu64 triggers this ? That spew comes from amd_k7_smp_check()
> > which should only run on family 6, which was all 32bit.
>
> [0.152749] smpboot: CPU0: AMD QEMU Virtual CPU
On Sat, Mar 08, 2014 at 01:48:42AM +0530, Nilesh More wrote:
>
> 1. When the USB is hotplugged, in the call stack of add_disk( ),
> while registering disk blkdev_get(bdev, FMODE_READ, NULL) gets called
> which I guess scans the partition table, initializes part array and
> registers the
On Fri, 7 Mar 2014 11:13:31 -0800
Soren Brinkmann wrote:
> Rename the config symbols for the Cadence UART to reflect the driver
> rebranding:
> SERIAL_XILINX_PS_UART(_CONSOLE) -> SERIAL_CADENCE_UART(_CONSOLE)
This breaks all those setups people have with pre-packed .config files
that have
On Fri, 7 Mar 2014 11:13:29 -0800
Soren Brinkmann wrote:
> Signed-off-by: Soren Brinkmann
> ---
> I'm not sure about this change. Is this acceptable or already too much?
> I think the name is used for some sysfs entries.
Its probably not a good idea. You might be ok depending whether anything
On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > From: Alistair Popple
> > Date: Thu, 6 Mar 2014 14:52:25 +1100
> >
> > > + out_be32(dev->reg, in_be32(dev->reg) | WKUP_ETH_RGMIIEN
> > > + | WKUP_ETH_TX_OE |
On Fri, 7 Mar 2014 11:13:27 -0800
Soren Brinkmann wrote:
> Signed-off-by: Soren Brinkmann
> ---
> drivers/tty/serial/xilinx_uartps.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/tty/serial/xilinx_uartps.c
> b/drivers/tty/serial/xilinx_uartps.c
>
On Saturday, March 08, 2014 01:11:49 AM Alexey Khoroshilov wrote:
> If p54u_load_firmware() fails, p54u_probe() does not deallocate
> already allocated resources. The patch adds proper failure handling.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey
From: Hayes Wang
Date: Fri, 7 Mar 2014 11:04:33 +0800
> - Select the suitable spin lock for each function.
> - Add additional check to reduce the spin lock.
> - Up the priority of the tx to avoid interrupted by rx.
> - Support rx checksum, large send, and IPv6 hw checksum.
Series applied,
On Fri, 7 Mar 2014 22:00:51 +0100
Jean Delvare wrote:
> As far as I know, the CS5535 and CS5536 chipsets are companions of the
> Geode series of processors, which are 32-bit only. So the CS5535
> drivers are not needed on x86-64, except for build testing purpose.
>
> This aligns the
On Fri, 7 Mar 2014 10:58:43 +0800 Liu ShuoX wrote:
>
> ftrace_read_cnt need to be reset in open to support mutli times
> getting the records.
>
> Signed-off-by: Liu ShuoX
> ---
> fs/pstore/ram.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/pstore/ram.c
From: Joe Perches
Date: Fri, 07 Mar 2014 13:02:44 -0800
> Right now, checkpatch emits a --strict only warning on "&&" or "||"
> at the beginning of line but that could be changed to any "$Operators"
>
> our $Arithmetic = qr{\+|-|\*|\/|%};
> our $Operators= qr{
>
On 03/07/2014 11:39 AM, Don Zickus wrote:
> A customer generated an external NMI using their iLO to test kdump worked.
> Unfortunately, the machine hung. Disabling the nmi_watchdog made things work.
>
> I speculated the external NMI fired, caused the machine to panic (as expected)
> and the perf
Dave,
Please pull this batch of fixes intende for the 3.14 stream...
For the mac80211 bits, Johannes says:
"Here I have a fix from Eliad for the minimal channel width calculation
in the mac80211 code which lead to monitor mode not working at all for
drivers using that. One of my fixes is for an
On Fri, 7 Mar 2014 11:58:52 +0900 Minchan Kim wrote:
> On Thu, Mar 06, 2014 at 10:21:32AM -0800, Laura Abbott wrote:
> > We received several reports of bad page state when freeing CMA pages
> > previously allocated with alloc_contig_range:
> >
> > <1>[ 1258.084111] BUG: Bad page state in
From: David Howells
Date: Thu, 06 Mar 2014 22:31:18 +
> David Miller wrote:
>
>> It depends upon whether you want the bug fixes to go into Linus's
>> tree for the current release or not.
>
> The fixes aren't particularly urgent, so if net-next is aimed at the next
> merge window, I would
If p54u_load_firmware() fails, p54u_probe() does not deallocate
already allocated resources. The patch adds proper failure handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/wireless/p54/p54usb.c | 4
1 file changed,
On Fri, 7 Mar 2014 11:05:49 -0600 (CST) Christoph Lameter
wrote:
> On Thu, 6 Mar 2014, Andrew Morton wrote:
>
> > > So, by "the whole series" do you mean just/all these:
> > >
> > > percpu-add-raw_cpu_ops.patch
> > > ...
> > > sh-replace-__get_cpu_var-uses.patch
> >
> > Yep. Commented out in
The bus and architecture dependencies are already on MFD_CS5535, so
there is no need to repeat them here.
Signed-off-by: Jean Delvare
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
drivers/misc/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
From: Zoltan Kiss
Date: Thu, 6 Mar 2014 21:48:22 +
> A long known problem of the upstream netback implementation that on the TX
> path (from guest to Dom0) it copies the whole packet from guest memory into
> Dom0. That simply became a bottleneck with 10Gb NICs, and generally it's a
> huge
Hi Linus !
Here are a couple of powerpc fixes for 3.14. One is (another !) nasty TM
problem, we can crash the kernel by forking inside a transaction. The
other one is a simple fix for an alignment issue which can hurt in LE
mode.
Cheers,
Ben.
The following changes since commit
On Fri, 2014-03-07 at 13:40 -0700, Bjorn Helgaas wrote:
> It seems quite possible that I broke pci_bus_alloc_resource(), which could
> cause an allocation failure like this.
>
> If you have a chance to try it, here's a debug patch against v3.14-rc5. It
> should apply cleanly to 96702be56037.
(added some cc's)
On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> From: Alistair Popple
> Date: Thu, 6 Mar 2014 14:52:25 +1100
>
> > + out_be32(dev->reg, in_be32(dev->reg) | WKUP_ETH_RGMIIEN
> > +| WKUP_ETH_TX_OE | WKUP_ETH_RX_IE);
>
> When an expression spans multiple
On 03/07/2014 11:10 AM, Dave Jones wrote:
> On Fri, Mar 07, 2014 at 10:56:11AM -0800, H. Peter Anvin wrote:
> > On 03/06/2014 09:50 PM, Fengguang Wu wrote:
> > >>
> > >> Unfortunately these things are hard to fix in Qemu.
> > >
> > > OK. As an alternative, is it possible to pass one of the
As far as I know, the CS5535 and CS5536 chipsets are companions of the
Geode series of processors, which are 32-bit only. So the CS5535
drivers are not needed on x86-64, except for build testing purpose.
This aligns the dependencies to what FB_GEODE already uses.
Signed-off-by: Jean Delvare
Cc:
Adding three more findings -
4. The memory pages thar are getting allocated in blkdev_get call in
step#1 are in msdos_partition() (1 page is alloacted here) and in
efi_partition() (2 pages are allocated here) function calls. I traced
the 'bdev->bd_inode->i_mapping->nrpages' to track the page
On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
> Please have a short look at the following BUG report + the comments
> -- this message here is a kind of FWD-ing it:
> https://bugs.archlinux.org/task/39005
>
> I came late to test kernel 3.13 with the .5 one, as it was the time
>
On Fri, Mar 07, 2014 at 09:45:28PM +0100, Lukasz Pawelczyk wrote:
>
> On 7 Mar 2014, at 20:09, Greg KH wrote:
>
> > On Fri, Mar 07, 2014 at 07:46:44PM +0100, Lukasz Pawelczyk wrote:
> >> Problem:
> >> Has anyone thought about a mechanism to limit/remove an access to a
> >> device during an
On 7 Mar 2014, at 20:24, Lennart Poettering wrote:
> On Fri, 07.03.14 19:45, Lukasz Pawelczyk (hav...@gmail.com) wrote:
>
>> Problem:
>> Has anyone thought about a mechanism to limit/remove an access to a
>> device during an application runtime? Meaning we have an application
>> that has an
On Fri, 07 Mar 2014 09:20:39 -0800 Andi Kleen wrote:
> David Rientjes writes:
> >
> > Per-process flags are a scarce resource so we should free them up
> > whenever possible and make them available. We'll be using it shortly for
> > memcg oom reserves.
>
> I'm not convinced TCP_RR is a
On 7 Mar 2014, at 20:09, Greg KH wrote:
> On Fri, Mar 07, 2014 at 07:46:44PM +0100, Lukasz Pawelczyk wrote:
>> Problem:
>> Has anyone thought about a mechanism to limit/remove an access to a
>> device during an application runtime? Meaning we have an application
>> that has an open file
Christoph Hellwig writes:
> Witch to using a preallocated flush_rq for blk-mq similar to what's done
> with the old request path. This allows us to set up the request properly
> with a tag from the actually allowed range and ->rq_disk as needed by
> some drivers. To make life easier we also
From: Alistair Popple
Date: Thu, 6 Mar 2014 14:52:25 +1100
> + out_be32(dev->reg, in_be32(dev->reg) | WKUP_ETH_RGMIIEN
> + | WKUP_ETH_TX_OE | WKUP_ETH_RX_IE);
When an expression spans multiple lines, the lines should end with
operators rather than begin with them.
Also, it
On Fri, Mar 07, 2014 at 06:16:49PM +0100, Paul Bolle wrote:
> Bjorn Helgaas schreef op vr 07-03-2014 om 09:55 [-0700]:
> > On Fri, Mar 7, 2014 at 2:48 AM, Paul Bolle wrote:
> > > This might end up not being relevant. And this is surely documented
> > > somewhere, but anyhow:
> > > - what git
From: Alexei Starovoitov
Date: Wed, 5 Mar 2014 19:30:15 -0800
> Extended BPF extends old BPF in the following ways:
> - from 2 to 10 registers
> Original BPF has two registers (A and X) and hidden frame pointer.
> Extended BPF has ten registers and read-only frame pointer.
> - from 32-bit
On Thu, Mar 6, 2014 at 1:25 PM, Paul Bolle wrote:
> Bjorn Helgaas schreef op ma 10-02-2014 om 14:33 [-0700]:
>> Can you open a kernel.org bugzilla report and attach complete dmesg
>> logs of the working and broken kernels to it? There might be more
>> useful resource-related messages from the
Hi!
> The Power Supply charging driver connects multiple subsystems
> to do charging in a generic way. The subsystems involves power_supply,
> thermal and battery communication subsystems (1wire).With this the charging is
> handled in a generic way.
" " after ".", please.
> +
> +The Power Supply
Artem Fetishev writes:
> https://bugzilla.kernel.org/show_bug.cgi?id=68991
>
> The expected logic of proc_map_files_get_link() is either to return 0 and
> initialize 'path' or return an error and leave 'path' uninitialized. By the
> time
> dname_to_vma_addr() returns 0 the corresponding vma may
Thanks Theodore for your quick reply.
To make few things clear, USB drive has FAT file system in it. And the
ext4 file system is of internal sdcard present in android device. The
ext4 corruption in /data partition occurs when USB drive is
hotplugged/hotunplugged. The bug may repro with first
From: "David A. Long"
Separate the kprobe-only definitions from the definitions needed by
both kprobes and uprobes.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/include/asm/kprobes.h | 15 +-
arch/arm/include/asm/{kprobes.h => probes.h} | 44
From: "David A. Long"
Suggested change from Oleg Nesterov. Fixes incomplete dependencies
for uprobes feature.
Signed-off-by: David A. Long
---
arch/Kconfig | 6 +-
kernel/trace/Kconfig | 1 +
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/Kconfig
From: "David A. Long"
Change the generic ARM probes code to pass in the opcode and
architecture-specific
structure separately instead of using struct kprobe, so we do not pollute
code being used only for uprobes or other non-kprobes instruction
interpretation.
Signed-off-by: David A. Long
From: "David A. Long"
Change the name of kprobes_insn to probes_insn so it can be shared between
kprobes and uprobes without confusion.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/kernel/kprobes-common.c | 2 +-
arch/arm/kernel/kprobes-thumb.c | 16
From: "David A. Long"
Any more ARM kprobes/uprobes symbols which have "kprobe" in the name must be
changed to the more generic "probes" or other non-kprobes specific symbol.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/include/asm/probes.h| 13 ++---
From: "David A. Long"
Using Rabin Vincent's ARM uprobes patches as a base, enable uprobes
support on ARM.
Caveats:
- Thumb is not supported
Signed-off-by: Rabin Vincent
Signed-off-by: David A. Long
---
arch/arm/Kconfig | 3 +
arch/arm/include/asm/ptrace.h | 6 +
From: "David A. Long"
Because the common underlying code for ARM kprobes and uprobes needs
to share a common architecrure-specific context structure, and because
the generic kprobes include file insists on defining this to a dummy
structure when kprobes is not configured, a new common structure
From: "David A. Long"
Add an emulate flag into the instruction interpreter, primarily for uprobes
support.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/kernel/kprobes.c | 2 +-
arch/arm/kernel/kprobes.h | 1 +
arch/arm/kernel/probes-arm.c | 4 ++--
From: "David A. Long"
Change kprobe_emulate_none, kprobe_simulate_nop, and arm_kprobe_decode_init
function names to something more appropriate for code being shared
outside of the kprobes subsystem. Also, move the new arm_probes_decode_init
declaration out of the kprobes.h include file and into
On Fri 2014-03-07 10:59:31, Jenny TC wrote:
> Add new power supply properties for input current, charge termination
> current, min and max temperature
>
> POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature
> POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature
>
>
From: "David A. Long"
This patch series adds basic uprobes support to ARM. It is based on patches
developed earlier by Rabin Vincent. That approach of adding hooks into
the kprobes instruction parsing code was not well received. This approach
separates the ARM instruction parsing code in kprobes
From: "David A. Long"
In preparation for sharing the ARM kprobes instruction interpreting
code with uprobes, make the symbols names less kprobes-specific.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/include/asm/probes.h| 11 +++---
arch/arm/kernel/kprobes-arm.c|
From: "David A. Long"
Allow arches to decided to ignore a probe hit. ARM will use this to
only call handlers if the conditions to execute a conditionally executed
instruction are satisfied.
Signed-off-by: David A. Long
Acked-by: Oleg Nesterov
---
include/linux/uprobes.h | 1 +
From: "David A. Long"
Make sure includes in ARM kprobes sources are done explicitly. Do not
rely on includes from other includes.
Signed-off-by: David A. Long
Acked-by: Jon Medhurst
---
arch/arm/include/asm/kprobes.h | 2 +-
arch/arm/kernel/kprobes-common.c | 3 +++
Hi!
> >> > +++ b/include/linux/power/power_supply_charger.h
> >>
> >> > +#define MAX_CUR_VOLT_SAMPLES 3
> >> > +#define DEF_CUR_VOLT_SAMPLE_JIFF (30*HZ)
> >>
> >> Why are things defined in Jiffies like this insead of seconds, milliseconds
> >> etc? This will vary with the current operating
On Fri 2014-03-07 11:04:59, Linus Walleij wrote:
> On Fri, Feb 28, 2014 at 6:01 PM, Pavel Machek wrote:
> > On Thu 2014-02-27 21:08:01, Linus Walleij wrote:
> >> On Thu, Feb 20, 2014 at 6:53 AM, Jenny TC wrote:
> >>
> >> > +++ b/include/linux/power/power_supply_charger.h
> >>
> >> > +#define
Em Fri, Mar 07, 2014 at 04:51:00PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Mar 07, 2014 at 02:19:49PM +0100, Jiri Olsa escreveu:
> > On Thu, Feb 27, 2014 at 08:22:26PM -0800, Andi Kleen wrote:
> > > +static void resolve_branch_ams(struct machine *machine, struct thread
> > > *thread,
Em Fri, Mar 07, 2014 at 02:19:49PM +0100, Jiri Olsa escreveu:
> On Thu, Feb 27, 2014 at 08:22:26PM -0800, Andi Kleen wrote:
> > From: Andi Kleen
>
> SNIP
>
> > index 8ad97e9..be29bb8 100644
> > --- a/tools/perf/util/callchain.h
> > +++ b/tools/perf/util/callchain.h
> > @@ -53,6 +53,7 @@ struct
A customer generated an external NMI using their iLO to test kdump worked.
Unfortunately, the machine hung. Disabling the nmi_watchdog made things work.
I speculated the external NMI fired, caused the machine to panic (as expected)
and the perf NMI from the watchdog came in and was latched. My
On Fri, Mar 7, 2014 at 8:45 AM, Bjorn Helgaas wrote:
>
> I opened a bugzilla report at
> https://bugzilla.kernel.org/show_bug.cgi?id=71691
>
> It seems like clearing DisINTx has some effect on MSI. I don't see
> anything in the spec that would suggest this (I'm looking at the PCIe
> r3.0 spec,
Kamil Debski wrote:
> Add support for Exynos 5250. This driver is to replace the old
> USB 2.0 PHY driver.
>
> Signed-off-by: Kamil Debski
> ---
> .../devicetree/bindings/phy/samsung-phy.txt|1 +
> drivers/phy/Kconfig| 11 +
> drivers/phy/Makefile
Kamil Debski wrote:
> Add a new driver for the Exynos USB 2.0 PHY. The new driver uses the generic
> PHY framework. The driver includes support for the Exynos 4x10 and 4x12
> SoC families.
>
> Signed-off-by: Kamil Debski
> ---
> .../devicetree/bindings/phy/samsung-phy.txt| 53
>
Kamil Debski wrote:
> Previously the of_phy_get function took a struct device * and
> was declared static. It was impossible to call it from
> another driver and thus it was impossible to get phy defined
> for a given node. The old function was renamed to _of_phy_get
> and was left for internal
Kamil Debski wrote:
> Adding devm_of_phy_get will allow to get phys by supplying a
> pointer to the struct device_node instead of struct device.
>
> Signed-off-by: Kamil Debski
> ---
> drivers/phy/phy-core.c | 31 +++
> include/linux/phy/phy.h |8
> 2
On Fri, 07.03.14 19:45, Lukasz Pawelczyk (hav...@gmail.com) wrote:
> Problem:
> Has anyone thought about a mechanism to limit/remove an access to a
> device during an application runtime? Meaning we have an application
> that has an open file descriptor to some /dev/node and depending on
>
Please have a short look at the following BUG report + the
comments -- this message here is a kind of FWD-ing it:
https://bugs.archlinux.org/task/39005
I came late to test kernel 3.13 with the .5 one, as it was the
time that the related -CK/BFS patch became available.
I'm not using
Sure, no problem.
Do you have a git tree with the latest versions of all the changes you
want for 3.15 in a branch? That would be helpful as I catch up on
applying things, so that I don't miss anything.
If you don't have one, taking a little time to set one up on github or
wherever would be
201 - 300 of 1502 matches
Mail list logo
