Create a new header file include/linux/ptp_pch.h which contains
prototype declaration of functions pch_ch_control_read(),
pch_ch_control_write(), pch_ch_event_read(), pch_ch_event_write(),
pch_src_uuid_lo_read(), pch_src_uuid_hi_read(), pch_rx_snap_read(),
pch_tx_snap_read() and
So I delayed this a couple of days to get back to my normal Sunday
release schedule, but I'm not entirely happy with the result. Things
aren't calming down the way they should be, and -rc4 is bigger than
previous rc's. And I don't think I can just blame the two extra days.
Anyway, what that means
SubmittingPatches already mentions referencing bugs fixed by a commit,
but doesn't mention citing relevant mailing list discussions. Add a
note to that effect, along with a recommendation to use the
https://lkml.kernel.org/ redirector.
Portions based on text from git's SubmittingPatches.
Most of the mechanical portions of SubmittingPatches exist to help patch
submitters replicate the output of git. Mention this explicitly, both
as a reminder that git will help with this process, and as signposting to
let git users know what they can safely skip.
Signed-off-by: Josh Triplett
Most commit messages use this style, and the recommendation frequently
comes up in discussions (especially in response to patches that don't
use it), but that recommendation doesn't actually appear anywhere in
Documentation. Add this style guideline to SubmittingPatches, using the
description
On Mon, Dec 16, 2013 at 02:14:15AM +0530, Rashika Kheria wrote:
Create a new header file include/linux/ptp_pch.h which contains
prototype declaration of functions pch_ch_control_read(),
pch_ch_control_write(), pch_ch_event_read(), pch_ch_event_write(),
pch_src_uuid_lo_read(),
On Sun, 15 Dec 2013 16:28:39 +0100
Sebastian Andrzej Siewior bige...@linutronix.de wrote:
Thank you for the fixups. I just did the same thing in the v3.12 tree.
The chunk you nuked is now in Dave's net tree as a0a9663dd214 (net: make
neigh_priv_len in struct net_device 16bit instead of 8bit).
On Sun, Dec 15, 2013 at 12:59:26PM -0800, Josh Triplett wrote:
Most commit messages use this style, and the recommendation frequently
comes up in discussions (especially in response to patches that don't
use it), but that recommendation doesn't actually appear anywhere in
Documentation. Add
On Sun, Dec 15, 2013 at 12:59:51PM -0800, Josh Triplett wrote:
Most of the mechanical portions of SubmittingPatches exist to help patch
submitters replicate the output of git. Mention this explicitly, both
as a reminder that git will help with this process, and as signposting to
let git users
On Sun, Dec 15, 2013 at 12:59:40PM -0800, Josh Triplett wrote:
SubmittingPatches already mentions referencing bugs fixed by a commit,
but doesn't mention citing relevant mailing list discussions. Add a
note to that effect, along with a recommendation to use the
https://lkml.kernel.org/
What is the status of this?
If I understand correctly, the crash I saw is different from what Dave
saw.
There was one patched scheduled for inclusion that fixes Dave's crash. But
what about mine? I have been running 3.13-rc2 for a couple of weeks now with
your other patch, without seeing it
On Sun, Dec 15, 2013 at 10:14:29PM +0100, Borislav Petkov wrote:
On Sun, Dec 15, 2013 at 12:59:26PM -0800, Josh Triplett wrote:
Most commit messages use this style, and the recommendation frequently
comes up in discussions (especially in response to patches that don't
use it), but that
My draft patch series uses Skein/Threefish. The authors conveniently
specified a way to use it as a PRNG, and it's very fast without
special hardware support (consequently, for all kinds of hardware.)
On my laptop, reading from /dev/urandom becomes about 25 times faster
for large reads, and
On Sun, Dec 15, 2013 at 10:04 AM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sun, Dec 15, 2013 at 02:31:23PM +0800, Fengguang Wu wrote:
Greetings,
I got the below dmesg and the first bad commit is
I thought this was already fixed in Bjorn's tree, but perhaps he hasn't
merged in
On Sun, Dec 15, 2013 at 03:34:59AM -0500, George Spelvin wrote:
I'm not convinced we need to worry about cache timing attacks, since
they typically involve a chosen plaintext attack and a fixed key ---
and the attacker isn't going to know what we are going to be
encrypting, let alone be
On 12/13/2013 08:52 PM, Felipe Balbi wrote:
Hi,
On Fri, Dec 13, 2013 at 08:48:30AM +0100, Andreas Larsson wrote:
On Wed, Dec 04, 2013 at 09:13:58AM +0100, Andreas Larsson wrote:
+static void gr_finish_request(struct gr_ep *ep, struct gr_request *req,
+ int status)
Hello,
-Original Message-
From: Bjorn Helgaas [mailto:bhelg...@google.com]
On Fri, Dec 13, 2013 at 12:04 PM, Rajat Jain rajatj...@juniper.net
wrote:
On Thu, Dec 12, 2013 at 11:26 PM, Yinghai Lu ying...@kernel.org
wrote:
On Thu, Dec 12, 2013 at 2:44 PM, Bjorn Helgaas
On Sun, Dec 15, 2013 at 03:12:03PM -0700, Bjorn Helgaas wrote:
On Sun, Dec 15, 2013 at 10:04 AM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sun, Dec 15, 2013 at 02:31:23PM +0800, Fengguang Wu wrote:
Greetings,
I got the below dmesg and the first bad commit is
I thought
Once again: the way I interpret this is:
* Always enable Link events.
* Disable presence events if attention button is present.
That sounds like a good plan to me.
How about Diag_Reset from MPT2SAS and others?
link could up and down
I am assuming you are referring to
Add of_match_table to hsi_char driver, so that it can
be referenced from Device Tree.
Signed-off-by: Sebastian Reichel s...@debian.org
---
drivers/hsi/clients/hsi_char.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/hsi/clients/hsi_char.c
Create device tree binding documentation for
OMAP Synchronous Serial Interface (SSI) device.
Signed-off-by: Sebastian Reichel s...@debian.org
---
Documentation/devicetree/bindings/hsi/omap_ssi.txt | 69 ++
1 file changed, 69 insertions(+)
create mode 100644
This adds support for the protocol used to communicate
with its cellular modem.
Signed-off-by: Sebastian Reichel s...@debian.org
---
arch/arm/boot/dts/omap3-n900.dts | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts
Add SSI device tree data for OMAP3 and Nokia N900.
Signed-off-by: Sebastian Reichel s...@debian.org
---
arch/arm/boot/dts/omap3-n900.dts | 28
arch/arm/boot/dts/omap3.dtsi | 47
2 files changed, 75 insertions(+)
diff --git
Create device tree binding documentation for
Nokia cellular modem GPIO handling.
Signed-off-by: Sebastian Reichel s...@debian.org
---
.../devicetree/bindings/misc/nokia-cmt.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
This adds support for the Nokia N900 cellular modem.
Signed-off-by: Sebastian Reichel s...@debian.org
---
arch/arm/boot/dts/omap3-n900.dts | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
Add driver handling GPIO pins of Nokia modems. The
driver provides reset notifications, so that SSI
clients can subscribe to them easily.
Signed-off-by: Sebastian Reichel s...@debian.org
---
drivers/misc/Kconfig | 7 ++
drivers/misc/Makefile | 1 +
drivers/misc/nokia-cmt.c | 298
This adds a driver for the SSI McSAAB protocol as used in
the Nokia N900.
Signed-off-by: Sebastian Reichel s...@debian.org
---
drivers/hsi/clients/Kconfig|8 +
drivers/hsi/clients/Makefile |3 +-
drivers/hsi/clients/ssi_protocol.c | 1201
Fix return code check of alloc_chrdev_region, which
returns 0 on success.
Signed-off-by: Sebastian Reichel s...@debian.org
---
drivers/hsi/clients/hsi_char.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hsi/clients/hsi_char.c b/drivers/hsi/clients/hsi_char.c
index
This exports a method to unregister all clients from
an hsi port.
Signed-off-by: Sebastian Reichel s...@debian.org
---
drivers/hsi/hsi.c | 10 ++
include/linux/hsi/hsi.h | 1 +
2 files changed, 11 insertions(+)
diff --git a/drivers/hsi/hsi.c b/drivers/hsi/hsi.c
index
Hi,
This is the fourth round of the OMAP SSI driver patches.
I added some more patches on top of the actual OMAP SSI driver, so that one can
get the overall picture of the planned architecture. This patchset contains
everything, that is needed to get the N900's modem running (without audio
Hi Simon,
Today's linux-next merge of the renesas tree got a conflict in
drivers/clk/Makefile between commit 0ad6125b1579 (clk: at91: add PMC
base support) from the arm-soc tree and commit 10cdfe9f327a (clk:
shmobile: Add R-Car Gen2 clocks support) from the renesas tree.
I fixed it up (see
On Sun, Dec 15, 2013 at 4:14 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sun, Dec 15, 2013 at 03:12:03PM -0700, Bjorn Helgaas wrote:
On Sun, Dec 15, 2013 at 10:04 AM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sun, Dec 15, 2013 at 02:31:23PM +0800, Fengguang Wu
On Mon, 2013-12-16 at 01:02 +0530, Hariprasad S wrote:
Hi,
Can you please pull from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
The following changes since commit 7d0c7a8cfd78388d90cc784a185b19dcbdbce824:
Ben Hutchings (1):
Merge
I just booted 3.13-rc4 on one of my ARM platforms and was greeted by this
trace. Maybe caused by 975022310233 which appears to take this lock in
softirq context.
=
[ INFO: inconsistent lock state ]
3.13.0-rc4+ #387 Not tainted
-
On Sun, Dec 15, 2013 at 4:24 PM, Rajat Jain rajatj...@juniper.net wrote:
Once again: the way I interpret this is:
* Always enable Link events.
* Disable presence events if attention button is present.
That sounds like a good plan to me.
How about Diag_Reset from MPT2SAS and
I think I can prepare a series that puts my changes
before Tim's. Unless I have trouble doing that
I will send that out in a few hours.
-Alex
On Dec 15, 2013, at 11:39 AM, Alex Elder alex.el...@linaro.org wrote:
On 12/14/2013 05:57 PM, Mike Turquette
On Sun, Dec 15, 2013 at 05:09:10PM -0500, George Spelvin wrote:
Well, /dev/urandom is documented as being *deliberately* slow. It's meant
only to produce 128 to 256 bits of seed material for CPRNG. I don't
know if Ted considers speeding it up to be goal or an antigoal. :-)
Hmm, I don't think
On Mon, 2013-12-16 at 00:07 +, Russell King - ARM Linux wrote:
I just booted 3.13-rc4 on one of my ARM platforms and was greeted by this
trace. Maybe caused by 975022310233 which appears to take this lock in
softirq context.
Yep, this was mentioned earlier, thanks !
Hi Linus !
Here are some more powerpc fixes for 3.13.
Uli's patch fixes a regression in ptrace caused by a mis-merge of
a previous LE patch. The rest are all more endian fixes, all fairly
trivial, found during testing of 3.13-rc's.
Cheers,
Ben.
The following changes since commit
Hi Jean,
Today's linux-next merge of the jdelvare-hwmon tree got a conflict in
drivers/hwmon/lm90.c between commits from Linus' tree and commits from
the jdelvare-hwmon tree.
It looks like the jdelvare-hwmon patch series has been reset back
(unintentionally?) to stuff that has already been
From: Mark Salter msal...@redhat.com
Date: Sun, 15 Dec 2013 10:50:26 -0500
On Sun, 2013-12-15 at 02:36 -0800, Dmitry Torokhov wrote:
How are we going to merge this? In bulk through input tree or peacemeal
through all arches first?
They should all go together to eliminate the chance of bisect
On 12/13/13 at 12:30pm, Matt Fleming wrote:
On Fri, 13 Dec, at 03:26:00PM, Dave Young wrote:
On 12/12/13 at 09:53pm, Borislav Petkov wrote:
On Thu, Dec 12, 2013 at 10:36:17AM +0800, Dave Young wrote:
Sorry that I forgot to explain this in changelog, should ask you before.
I did
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_pm.c between commit be3d26b0588c (drm/i915:
get a PC8 reference when enabling the power well) from the
drm-intel-fixes tree and commit c1ca727f8945 (drm/i915: support for
multiple power wells) from
On 11/27/13 at 09:44pm, Mark Salter wrote:
This patch copies generic bits of x86 early_ioremap() support
into a library for potential use by other architectures.
Signed-off-by: Mark Salter msal...@redhat.com
CC: Arnd Bergmann a...@arndb.de
CC: Ingo Molnar mi...@kernel.org
CC:
On 12/13/13 at 04:51pm, Leif Lindholm wrote:
On Wed, Dec 11, 2013 at 10:17:58AM -0500, Mark Salter wrote:
Anyway, I posted a patch to create a generic early_ioremap
implementation using generic bits of the x86 code:
https://lkml.org/lkml/2013/11/27/621
So maybe Dave's patch 1/14
On Sun, Dec 15, 2013 at 02:35:07PM +1100, dt.ta...@gmail.com wrote:
From: Daniel Tang dt.ta...@gmail.com
The USB controller in TI-NSPIRE calculators (LSI Zevio SoC) are based off
either
Freescale's USB OTG controller or the USB controller found in the IMX233, both
of which are Chipidea
There are a lot of 16K page size NAND, they are used in android system.
Many NAND need read retry and data randomization, kernel does not support
this
feature.
Brian is adding the read-retry feature.
I think the data randomization should be done by the hardware.
If we do it by
Hi,
On 16/12/2013, at 12:19 PM, Peter Chen peter.c...@freescale.com wrote:
The driver patch is okay for me, please cc me your dt patch next
time, I will apply it when your dt patches are applied by
dt maintainer (or any of your dt strings zevio_xxx are applied).
--
Best Regards,
- print_efi_memmap();
+ if (efi_setup) {
+ int s;
+ struct efi_setup_data *data;
+
+ s = sizeof(*data) + nr_efi_runtime_map * sizeof(data-map[0]);
+ data = early_memremap(efi_setup, s);
+ if (!data)
+ return;
On Mon, Dec 16, 2013 at 12:36:36AM +0800, Jiang Liu wrote:
Commit 9a46ad6d6df3b54 smp: make smp_call_function_many() use logic
similar to smp_call_function_single() has unified the way to handle
single and multiple cross-CPU function calls. Now only one interrupt
is needed for architecture
On 12/16/13 at 09:33am, Dave Young wrote:
On 12/13/13 at 12:30pm, Matt Fleming wrote:
On Fri, 13 Dec, at 03:26:00PM, Dave Young wrote:
On 12/12/13 at 09:53pm, Borislav Petkov wrote:
On Thu, Dec 12, 2013 at 10:36:17AM +0800, Dave Young wrote:
Sorry that I forgot to explain this in
Hi Kristian,
On 12/16/2013 05:59 AM, Kristian Nielsen wrote:
What is the status of this?
If I understand correctly, the crash I saw is different from what Dave
saw.
There was one patched scheduled for inclusion that fixes Dave's crash. But
what about mine? I have been running 3.13-rc2
On 12/12/2013 02:34 AM, Ramkumar Ramachandra wrote:
David Ahern wrote:
Why not make raw_dump a proper argument?
Sure, that'd work too. I was thinking of a minimal way to fix the
problem myself.
Hi Ramkumar and David,
If this argument is only used for perf complement, how about make
it
Hello ,
I hope this e-mail find you in good health. i am Johnson Clitton an America
military. seeking for true friendship and partner. as i was searching i saw
your profile here and i move to contact you.
I will give you further details about myself when i read from you. please
write me on my
On 12/11/13, 5:36 AM, Alexander Shishkin wrote:
diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
index a0c7c59..80817ec 100644
--- a/tools/perf/util/dso.c
+++ b/tools/perf/util/dso.c
@@ -446,6 +446,7 @@ struct dso *dso__new(const char *name)
dso-cache = RB_ROOT;
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/x86/platform/efi/efi.c between commit 04bf9ba720fc (x86, efi: Don't
use (U)EFI time services on 32 bit) from Linus' tree and commit
f4fccac05f7f (x86/efi: Simplify EFI_DEBUG) from the tip tree.
I fixed it up (see below) and
Currently, if we use perf kvm --guestkallsyms --guestmodules report,
we can not get the perf information from perf data file. The all sample
are shown as unknown.
Reproducing steps:
# perf kvm --guestkallsyms /tmp/kallsyms --guestmodules /tmp/modules
record -a sleep 1
[ perf
Hi Kristian,
On 12/16/2013 10:58 AM, Gu Zheng wrote:
Hi Kristian,
On 12/16/2013 05:59 AM, Kristian Nielsen wrote:
What is the status of this?
If I understand correctly, the crash I saw is different from what Dave
saw.
Thought the crash you saw is different from Dave's, but as you know,
On Mon, Dec 16, 2013 at 02:03:54AM +, Caizhiyong wrote:
There are a lot of 16K page size NAND, they are used in android system.
Many NAND need read retry and data randomization, kernel does not support
this
feature.
Brian is adding the read-retry feature.
I think the
On 12/11/2013 04:36 AM, Serge E. Hallyn wrote:
Quoting Eric Paris (epa...@redhat.com):
On Tue, 2013-12-10 at 10:51 -0600, Serge Hallyn wrote:
Quoting Gao feng (gaof...@cn.fujitsu.com):
On 12/10/2013 02:26 AM, Serge Hallyn wrote:
Quoting Gao feng (gaof...@cn.fujitsu.com):
On 12/07/2013 06:12
David,
Could you please help to review this patch when you have a time ?
Thanx in advance
- Yang
On 12/16/2013 11:26 AM, Dongsheng Yang wrote:
Currently, if we use perf kvm --guestkallsyms --guestmodules report,
we can not get the perf information from perf data file. The all sample
2, If the regulator dt node is exist but the optional VDDD is absent (i.e.
The external VDDD is not used), a -EPROBE_DEFER will be returned, if
just return the -EPROBE_DEFER to the probe(and then the probe deferral
mechanism will do the probe again later, is that right ?), and then
the
On Sat, Dec 14, 2013 at 03:23:24PM -0500, Tejun Heo wrote:
Hello, Dave.
On Sat, Dec 14, 2013 at 12:53:43PM +1100, Dave Chinner wrote:
That's the fundamental problem here - device removal asks the device
to fsync the filesystem on top of the device that was just removed.
The simple way to
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next, I've
noticed that
quite often there's a hang happening inside shmem_fallocate. There are several
processes stuck
trying to acquire inode-i_mutex (for more than 2 minutes), while the process
that holds it has
the
PREEMPT_RT support for Sparc64.
I have tested it on UltraSparc T4 (Niagara4).
Allen Pais (3):
sparc64: use generic rwsem spinlocks rt
sparc64: convert spinlock_t to raw_spinlock_t in mmu_context_t
sparc64: convert ctx_alloc_lock raw_spinlock_t
arch/sparc/Kconfig |
Signed-off-by: Allen Pais allen.p...@oracle.com
---
arch/sparc/include/asm/mmu_context_64.h |2 +-
arch/sparc/mm/init_64.c | 10 +-
arch/sparc/mm/tsb.c |4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git
Issue debugged by Thomas Gleixner t...@linutronix.de
Signed-off-by: Allen Pais allen.p...@oracle.com
---
arch/sparc/Kconfig |1 +
arch/sparc/include/asm/mmu_64.h |2 +-
arch/sparc/include/asm/mmu_context_64.h |8
arch/sparc/kernel/smp_64.c
From: David A. Long dave.l...@linaro.org
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 dave.l...@linaro.org
---
arch/arm/kernel/kprobes-common.c | 2 +-
arch/arm/kernel/kprobes-thumb.c | 16
From: David A. Long dave.l...@linaro.org
Separate the kprobe-only definitions from the definitions needed by
both kprobes and uprobes.
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm/include/asm/kprobes.h | 15 +--
arch/arm/include/asm/probes.h | 18
From: David A. Long dave.l...@linaro.org
Now that arm uprobes support has been made separate from the arm kprobes code
the Kconfig can be changed to reflect that.
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git
-Original Message-
From: Huang Shijie [mailto:b32...@freescale.com]
Sent: Monday, December 16, 2013 11:07 AM
To: Caizhiyong
Cc: Huang Shijie; Brian Norris; David Woodhouse; Quyaxin;
linux-kernel@vger.kernel.org; linux-...@lists.infradead.org; Artem Bityutskiy;
Wanglin (Albert);
Hi Ian,
(2013/12/13 8:30), Ian Webster wrote:
This change adds a --clock option to trace-cmd record. It simply writes
trace_clock on debugfs. Examples of valid choices on most systems are: local,
global, counter, and any other choice compatible with ftrace.
Nice work!
Please see my following
From: David A. Long dave.l...@linaro.org
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
From: David A. Long dave.l...@linaro.org
Using Rabin Vincent's ARM uprobes patches as a base, enable uprobes
support on ARM.
Caveats:
- Thumb is not supported
- XOL abort/trap handling is not implemented
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm/Kconfig
From: David A. Long dave.l...@linaro.org
Add an emulate flag into the instruction interpreter, primarily for uprobes
support.
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm/kernel/kprobes.c | 3 ++-
arch/arm/kernel/kprobes.h | 1 +
arch/arm/kernel/probes-arm.c | 4
From: David A. Long dave.l...@linaro.org
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 dave.l...@linaro.org
---
arch/arm/include/asm/probes.h| 13 ++--
From: David A. Long dave.l...@linaro.org
For any ARM kprobes/uprobes code interfacing to the generic ARM probes code
use a new probes_opcode_t type to avoid a dependency on kprobes definitions.
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm/include/asm/probes.h| 7 ++--
From: David A. Long dave.l...@linaro.org
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
From: Jon Medhurst (Tixy) t...@linaro.org
For now the jprobes tests fail on ARM for when built into a kernel compiled
in thumb mode. They work fine for ARM kernels, and when built as a loadable
module.
Signed-off-by: Jon Medhurst (Tixy) t...@linaro.org
Signed-off-by: David A. Long
From: David A. Long dave.l...@linaro.org
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 dave.l...@linaro.org
---
arch/arm/include/asm/probes.h | 4 ++--
From: David A. Long dave.l...@linaro.org
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:
From: David A. Long dave.l...@linaro.org
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 dave.l...@linaro.org
Acked-by: Oleg Nesterov
Signed-off-by: Allen Pais allen.p...@oracle.com
---
arch/sparc/Kconfig |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
index 6787bd3..554995d 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/Kconfig
@@ -179,12 +179,10 @@ config
From: David A. Long dave.l...@linaro.org
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
On Sun, Dec 15, 2013 at 03:34:59AM -0500, George Spelvin wrote:
You're describing standard key-recovery attacks. For /dev/random,
just knowing the *ciphertext* constitutes a successful attack.
Um, no. The *ciphertext* is the output. The attacker can get all of
the ciphertext he or she
Konrad Rzeszutek Wilk wrote:
On Mon, Dec 16, 2013 at 12:36:36AM +0800, Jiang Liu wrote:
Commit 9a46ad6d6df3b54 smp: make smp_call_function_many() use logic
similar to smp_call_function_single() has unified the way to handle
single and multiple cross-CPU function calls. Now only one interrupt
On 12/15/2013 06:22 PM, Alex Elder wrote:
I think I can prepare a series that puts my changes
before Tim's. Unless I have trouble doing that
I will send that out in a few hours.
. . .
I got started on doing this but then I decided to go
check on the status of Tim's series. It looks like
From: Namhyung Kim namhyung@lge.com
Move fetch function helper macros/functions to the header file and
make them external. This is preparation of supporting uprobe fetch
table in next patch.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju
From: Namhyung Kim namhyung@lge.com
Move existing functions to trace_kprobe.c and add NULL entries to the
uprobes fetch type table. I don't make them static since some generic
routines like update/free_XXX_fetch_param() require pointers to the
functions.
Cc: Masami Hiramatsu
From: Hyeoncheol Lee cheol@lge.com
The deref fetch methods access a memory region but it assumes that
it's a kernel memory since uprobes does not support them.
Add -fetch and -fetch_size member in order to provide a proper
access methods for supporting uprobes.
Acked-by: Masami Hiramatsu
From: Oleg Nesterov o...@redhat.com
uprobe_trace_print() and uprobe_perf_print() need to pass the additional
info to call_fetch() methods, currently there is no simple way to do this.
current-utask looks like a natural place to hold this info, but we need
to allocate it before handler_chain().
From: Namhyung Kim namhyung@lge.com
Use separate fetch_type_table for kprobes and uprobes. It currently
shares all fetch methods but some of them will be implemented
differently later.
This is not to break build if [ku]probes is configured alone (like
!CONFIG_KPROBE_EVENT and
From: Namhyung Kim namhyung@lge.com
Enable to fetch other types of argument for the uprobes. IOW, we can
access stack, memory, deref, bitfield and retval from uprobes now.
The format for the argument types are same as kprobes (but @SYMBOL
type is not supported for uprobes), i.e:
@ADDR
Hi Artem:
As we talked in mail before, please check my patch as below:
From: Qi Wang qiw...@micron.com
nor_erase_prepare() will be called before erase a NOR flash, it will program '0'
into a block to mark this block. But program data into a erasure interrupted
block
can cause program
From: Namhyung Kim namhyung@lge.com
Fetching from user space should be done in a non-atomic context. So
use a per-cpu buffer and copy its content to the ring buffer
atomically. Note that we can migrate during accessing user memory
thus use a per-cpu mutex to protect concurrent accesses.
From: Namhyung Kim namhyung@lge.com
Currently uprobes don't pass is_return to the argument parser so that
it cannot make use of $retval fetch method since it only works for
return probes.
Reviewed-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju
From: Namhyung Kim namhyung@lge.com
Use separate method to fetch from stack. Move existing functions to
trace_kprobe.c and make them static. Also add new stack fetch
implementation for uprobes.
Cc: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju
From: Namhyung Kim namhyung@lge.com
Enable to fetch data from a file offset. Currently it only supports
fetching from same binary uprobe set. It'll translate the file offset
to a proper virtual address in the process.
The syntax is @+OFFSET as it does similar to normal memory fetching
From: Namhyung Kim namhyung@lge.com
Use separate method to fetch from memory. Move existing functions to
trace_kprobe.c and make them static. Also add new memory fetch
implementation for uprobes.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju
From: Namhyung Kim namhyung@lge.com
The set_print_fmt() functions are implemented almost same for
[ku]probes. Move it to a common place and get rid of the duplication.
Acked-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Srikar Dronamraju sri...@linux.vnet.ibm.com
Cc: Oleg
1 - 100 of 518 matches
Mail list logo
