On 16/12/13 05:16, David Ahern wrote:
> 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
On Sun, 24 Nov 2013 01:53:11 -0200 Henrique de Moraes Holschuh
wrote:
> On Sun, 24 Nov 2013, Matthew Garrett wrote:
> > On Sat, Nov 23, 2013 at 10:40:15PM -0200, Henrique de Moraes Holschuh wrote:
> > > On Fri, 22 Nov 2013, Matthew Garrett wrote:
> > > > We have userspace that relies on uevents
On Fri, Dec 13, 2013 at 3:12 AM, Grygorii Strashko
wrote:
> The similar GPIO HW block is used by keystone SoCs as
> in Davinci SoCs.
> Hence, reuse Davinci GPIO driver for Keystone taking into
> account that Keystone contains ARM GIC IRQ controller which
> is implemented using IRQ Chip.
>
>
On 2013年12月13日 18:36, David Laight wrote:
From: fre...@asix.com.tw
...
- skb = __netdev_alloc_skb_ip_align(dev->net, size, flags);
+ if (dev->driver_info->flags & FLAG_HW_IPALIGN)
+ skb = __netdev_alloc_skb(dev->net, size, flags);
+ else
+ skb =
We just initialize the ftrace profile for each online cpu currently, this
implementation has two problems:
- If we online a CPU after we enable the function profile, and then run the
test, we will lose the trace information on that CPU.
Steps to reproduce:
# echo 0 >
Yijing,
This one looks good.
While I take a look at the source code, there are around 20 places with
similar style. Do you think it would be good to change all these places
in one patch?
On Thu, Dec 05, 2013 at 08:01:20PM +0800, Yijing Wang wrote:
>Use PCI standard marco dev_is_pci() instead of
Hi,
I sent a fix for this already on last Wednesday but I forgot to put you
on as recipient.
http://thread.gmane.org/gmane.linux.kernel/1612360
Fix is needed also for clock driver and on Saturday Rashika Kheria
posted similar patch.
Best regards,
Krzysztof
On Mon, 2013-12-16 at 16:47 +1100,
On Wed, 20 Nov 2013 14:30:55 +0100 Pali Roh__r wrote:
> Both proc files are writeable and used for configuring cells. But
> there is missing correct mode flag for writeable files. Without
> this patch both proc files are read only.
>
> diff --git a/fs/afs/proc.c b/fs/afs/proc.c
> index
>> Well, /dev/urandom is documented as being *deliberately* slow.
> Hmm, I don't think I've seen that documentation. I don't see anything
> about that point in the comments of drivers/char/random.c. The
> urandom(4) man page says /dev/urandom "is designed for security, not
> speed, and is
On Mon, Dec 16, 2013 at 01:43:59AM -0500, Theodore Ts'o wrote:
> I understand that; and as I wrote in my last e-mail, I think that is a
> substantially harder attack than the currently published cache timing
> attacks, which are known plaintext attacks --- that is the attacker
> doesn't know the
On Sun, Dec 15, 2013 at 11:22:47PM -0500, George Spelvin wrote:
>
> > Um, no. The *ciphertext* is the output. The attacker can get all of
> > the ciphertext he or she wants by reading /dev/random (although we'd
> > probably do some folding as we currently do so the attacker won't even
> > get
On 2013/12/13 7:48, Zoltan Kiss wrote:
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 perfomance penalty. The
This removes the double initialization of the msg_namelen variable.
Signed-off-by: Sankha Narayan Guria
--- linux/drivers/staging/usbip/usbip_common.c.orig 2013-12-16
11:24:32.930512781 +0530
+++ linux/drivers/staging/usbip/usbip_common.c 2013-12-16
11:25:03.190513334 +0530
@@ -366,7 +366,6 @@
On 15-12-13 20:04, Tejun Heo wrote:
Hello, Hans.
On Sun, Dec 15, 2013 at 08:00:20PM +0100, Hans de Goede wrote:
I think it would be a good idea to merge ahci upstream using the
ahci_imx.c method for now. You already indicated that you were not against
doing that for now.
Well, the thing is
From: Wei Yongjun
In case of error, the function debugfs_create_file() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test in
the return value check should be replaced with NULL test.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/i915/i915_debugfs.c | 12 ++--
On Sun, Dec 15, 2013 at 8:29 PM, Alex Elder wrote:
> In the mean time, I have created a new branch that
> is based on v3.13-rc4 (and includes Tim's prerequisite
> patches). Pull request (still wrapped my my mailer)
> is below.
Hi Alex,
This isn't a mess but is pretty normal. Can you create a
The description should be for native_stop_other_cpus() instead of
smp_reboot_interrupt().
Signed-off-by: Xie XiuQi
---
arch/x86/kernel/smp.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/smp.c b/arch/x86/kernel/smp.c
index 7c3a5a6..f295a18 100644
---
On 12/13/13 at 12:30pm, Matt Fleming wrote:
> I agree with Borislav that this should be invoked from efisubsys_init().
> Also Dave, there's nothing inherently x86-specific about runtime-map.c -
> we've been trying not to dump arch-specific code in
> drivers/firmware/efi/.
>
> How about something
Hi all,
Changes since 20131213:
Linus' tree gained a build failure for which I added a patch.
The renesas tree gained a conflict against the arm-soc tree.
The powerpc tree still had its build failure for which I applied a
supplied patch.
The jdelvare-hwmon tree gained a conflict against
It's ok to unicore32.
Acked-by: Guan Xuetao
- Mark Salter 写道：
> Architectures which might use an i8042 for serial IO to keyboard,
> mouse, etc should select ARCH_MIGHT_HAVE_PC_SERIO.
>
> Signed-off-by: Mark Salter
> CC: Guan Xuetao
> ---
> arch/unicore32/Kconfig | 1 +
> 1 file
From: Wei Yongjun
Fix to return negative error code -EIO from the error handling
case instead of 0.
Signed-off-by: Wei Yongjun
---
drivers/staging/xillybus/xillybus_pcie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/xillybus/xillybus_pcie.c
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/regulator/s2mps11.c: In function 's2mps11_pmic_probe':
drivers/regulator/s2mps11.c:441:23: error: 'struct sec_pmic_dev' has no member
named 'regmap'
config.regmap = iodev->regmap;
On Fri, Dec 13, 2013 at 07:12:58PM +0900, Magnus Damm wrote:
> Hi Olof,
>
> On Thu, Dec 12, 2013 at 10:05 AM, Olof Johansson wrote:
> > Hi,
> >
> > A couple of small comments below.
>
> Thanks for your feedback!
>
> > On Thu, Dec 12, 2013 at 08:56:26AM +0900, Magnus Damm wrote:
> >> From:
Change regmap to regmap_pmic. This is needed for commit
3e1e4a5f3a324502c27c4e8808e06ac2ea842360 ("mfd/rtc: s5m: fix register
updating by adding regmap for RTC") to rename regmap to regmap_pmic in
include/linux/mfd/samsung/core.h.
Signed-off-by: Stephen Engelman
Cc: Krzysztof Kozlowski
Cc:
This patch removes synchronous wait for the up-to-date of buffer in the
file system level. Instead all operations after submit_bh are moved into
the End-of-IO handler and its associated workeque. It decompresses/copies
data into pages and unlock them asynchronously.
This patch enhances the
Hi Linus,
Please pull the following pair of Ceph fixes from
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
One of these is fixing a regression from the d_flags file type patch that
went into -rc1 that broke instantiation of inodes and dentries (we were
doing
Hi Davidlohr,
On Sat, 14 Dec 2013 20:31:56 -0800, Davidlohr Bueso wrote:
> Block a bunch of threads on a futex and wake them up, N at a time.
>
> This program is particularly useful to measure the latency of nthread wakeups
> in non-error situations: all waiters are queued and all wake calls
Hi Karl,
On Mon, Dec 09, 2013 at 07:22:57AM -0500, Karl Dahlke wrote:
> From: Karl Dahlke
>
> The speaker driver can play a tone at a specified frequency,
> or the standard control G bell,
> which is a special case of TONE at 1000 hz 0.1 seconds.
> This patch adds kd_mkpulse() to generate a
Hi Vegard,
On 12/12/2013 11:52 AM, vegard.nos...@oracle.com wrote:
> +#ifdef CONFIG_EXPLOIT_DETECTION
> +extern void _exploit(const char *id);
So right now the on/off switch is a kernel config option. I suggest we should
add another
dynamic switch (maybe in the form of jump labels) to add an
Hi Vince,
On Sat, 14 Dec 2013 15:25:18 -0500 (EST), Vince Weaver wrote:
> OK, here's an updated version that reuses evsel and hopefully doesn't leak
> memory like the previous patch I posted.
>
>
> "perf list" listing of hardware events doesn't work on older ARM devices.
> The change enabling
On Sun, Dec 15, 2013 at 08:27:25PM -0500, David Miller wrote:
> From: Mark Salter
> 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?
>
Enable system-call auditing support at alpha architecture
Signed-off-by: Zhenglong.cai
arch/alpha/Kconfig |3 +++
arch/alpha/include/asm/ptrace.h |5 +
arch/alpha/include/asm/thread_info.h |2 ++
arch/alpha/kernel/Makefile |1 +
On Saturday, December 14, 2013 3:40 AM, Levente Kurusa wrote:
>
> Currently we kfree the container of the device which failed to register.
> This is wrong as the last reference is not given up with a put_device
> call. Also, now that we have put_device() callen, we no longer need
> the kfree as
Hi Arnaldo,
On Fri, 13 Dec 2013 11:52:04 -0300, Arnaldo Carvalho de Melo wrote:
>> -str = malloc_or_die(6);
>> +str = malloc(6);
>> +if (str == NULL)
>> +break;
>>
Hi,
The patch had some compile time fixes to be done. It was accidentally mailed
out before doing so. Below is the right patch. Apologies for the same.
Thanks
Regards
Preeti U Murthy
-
time: Support in tick broadcast
Hi Felipe,
After merging the usb-gadget tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/usb/phy/phy-keystone.c: In function 'keystone_usbphy_probe':
drivers/usb/phy/phy-keystone.c:96:4: warning: passing argument 3 of
'usb_phy_gen_create_phy' makes pointer from
From: Namhyung Kim
The print format of s32 type was "ld" and it's casted to "long". So
it turned out to print 4294967295 for "-1" on 64-bit systems. Not
sure whether it worked well on 32-bit systems.
Anyway, it doesn't need to have cast argument at all since it already
casted using type
From: Namhyung Kim
Convert struct trace_uprobe to make use of the common trace_probe
structure.
Reviewed-by: Masami Hiramatsu
Acked-by: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
kernel/trace/trace_uprobe.c | 159
Hello,
This patchset implements memory (address), stack[N], deference,
bitfield, retval (it needs uretprobe tho) and file_offset fetch
methods for uprobes. It's based on the previous work [1] done by
Hyeoncheol Lee.
Now kprobes and uprobes have their own fetch_type_tables and, in turn,
memory
From: Namhyung Kim
The __get_data_size() and store_trace_args() will be used by uprobes
too. Move them to a common location.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
From: Namhyung Kim
There are functions that can be shared to both of kprobes and uprobes.
Separate common data structure to struct trace_probe and use it from
the shared functions.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung
From: Namhyung Kim
The uprobe syntax requires an offset after a file path not a symbol.
Reviewed-by: Masami Hiramatsu
Acked-by: Oleg Nesterov
Acked-by: Srikar Dronamraju
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
Documentation/trace/uprobetracer.txt |
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
From: Namhyung Kim
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
(@ADDR) which does no
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
From: Namhyung Kim
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.
This is needed since
From: Namhyung Kim
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 : Fetch memory at
Hi Artem:
As we talked in mail before, please check my patch as below:
From: Qi Wang
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 timtout(several minutes at
From: Oleg Nesterov
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().
This is a bit
From: Namhyung Kim
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 CONFIG_UPROBE_EVENT). So I added
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg
From: Hyeoncheol Lee
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
Cc: Srikar
From: Namhyung Kim
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
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
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
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
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
Signed-off-by: Allen Pais
---
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 NR_CPUS
source
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"
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"
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"
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
---
arch/arm/include/asm/probes.h | 4 ++--
arch/arm/kernel/kprobes-thumb.c | 4 ++--
From: "David A. Long"
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
---
arch/arm/include/asm/probes.h| 7 ++--
arch/arm/kernel/kprobes-arm.c| 16
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
From: "Jon Medhurst (Tixy)"
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)"
Signed-off-by: David A. Long
---
arch/arm/kernel/kprobes-test.c |
From: "David A. Long"
Add an emulate flag into the instruction interpreter, primarily for uprobes
support.
Signed-off-by: David A. Long
---
arch/arm/kernel/kprobes.c | 3 ++-
arch/arm/kernel/kprobes.h | 1 +
arch/arm/kernel/probes-arm.c | 4 ++--
arch/arm/kernel/probes-arm.h
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
---
arch/arm/include/asm/probes.h| 13 ++--
arch/arm/kernel/kprobes-common.c |
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"
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"
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
---
arch/arm/Kconfig | 4 +
From: "David A. Long"
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
---
arch/arm/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index
> -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
Issue debugged by Thomas Gleixner
Signed-off-by: Allen Pais
---
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 |4 ++--
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
---
arch/arm/kernel/kprobes-common.c | 2 +-
arch/arm/kernel/kprobes-thumb.c | 16
arch/arm/kernel/kprobes.h
From: "David A. Long"
Separate the kprobe-only definitions from the definitions needed by
both kprobes and uprobes.
Signed-off-by: David A. Long
---
arch/arm/include/asm/kprobes.h | 15 +--
arch/arm/include/asm/probes.h | 18 ++
2 files changed, 19 insertions(+),
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
---
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 a/arch/sparc/include/asm/mmu_context_64.h
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
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
> > 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
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):
>>
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
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.
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
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 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)
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;
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
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
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
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
> > - 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)
> > +
Hi,
On 16/12/2013, at 12:19 PM, Peter Chen 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,
> Peter Chen
>
> >
> > 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
On Sun, Dec 15, 2013 at 02:35:07PM +1100, dt.ta...@gmail.com wrote:
> From: Daniel Tang
>
> 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 compatible.
>
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
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
> CC: Arnd Bergmann
> CC: Ingo Molnar
> CC: linux-a...@vger.kernel.org
> ---
>
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")
1 - 100 of 518 matches
Mail list logo
