> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
> Sent: Wednesday, November 12, 2014 19:29
> To: Jamet, Michael
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Levy, Amir
> (Jer); Alloun, Dan; Rafael Wysocki; Andreas Noever
> Subject: Re: [PATCH] pci:
On 11/17/2014 12:00 AM, Peter Crosthwaite wrote:
> On Mon, Nov 17, 2014 at 5:32 AM, Sören Brinkmann
> wrote:
>> On Sun, 2014-11-16 at 11:51AM +0100, Andreas Färber wrote:
>>> Hi Michal,
>>>
>>> Am 14.11.2014 um 11:52 schrieb Michal Simek:
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi
On Tue, Nov 18, 2014 at 03:13:50PM +0900, Namhyung Kim wrote:
SNIP
> >> > + * in "from" register, while the callee is
> >> > stored
> >> > + * in "to" register.
> >> > + * For example, there is a call stack
> >> > +
On Tue, Nov 18, 2014 at 02:35:21PM +0800, Zefan Li wrote:
> For all 3 patches:
>
> Acked-by: Zefan Li
Applied 1-3 to cgroup/for-3.19.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Tue, Nov 18, 2014 at 02:30:44PM +0800, Zefan Li wrote:
> For all 3 patches:
>
> Acked-by: Zefan Li
Applied 1-3 to cgroup/for-3.19.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hello,
On 2014-11-14 15:51, Arnd Bergmann wrote:
On Friday 14 November 2014 15:11:58 Marek Szyprowski wrote:
I assume that after all comments from previous versions, no more changes
are needed
to this patchset and I would really like to have it queued to v3.19.
Arnd, Olof: could you take this
On 2014/11/17 18:08, Arnd Bergmann wrote:
> On Monday 17 November 2014 18:21:35 Yijing Wang wrote:
>> - list_for_each_entry(window, resources, list)
>> - if (window->res->flags & IORESOURCE_BUS) {
>> - found = true;
>> - break;
>> -
Smatch complains about this:
kernel/exit.c:543 forget_original_parent()
warn: add some parenthesis here?
I don't normally advocate changing the code to make the static checker
happy but these are normally precedence bugs so I think it's ok to put
parenthesis so it's clear the
On Sun 2014-11-16 13:29:50, Robert Jarzmik wrote:
> Pavel Machek writes:
>
> > On Thu 2014-11-13 20:18:04, Aaro Koskinen wrote:
> >> Hi,
> >>
> >> On Thu, Nov 13, 2014 at 09:45:36AM -0800, Tony Lindgren wrote:
> >> > * Pavel Machek [141113 08:23]:
> >> > > OTOH ofono seems pretty reasonable.
Hello edubezval,
I saw your latest patch[0].
I need send the new patch to fit the of-thermal Sensors API.
Right?
[0]: https://patchwork.kernel.org/patch/5324371/
在 2014年11月12日 13:02, Caesar Wang 写道:
Thermal is TS-ADC Controller module supports
user-defined mode and automatic mode.
On Mon, Nov 17, 2014 at 12:27 PM, Kees Cook wrote:
> On Sun, Nov 16, 2014 at 3:44 PM, Thomas Gleixner wrote:
>>
>> So the initial patch to get rid of the X mapping is of course to just
>> extend the area to the PMD. A little bit different to your initial
>> patch, but essentially the same.
>>
>>
Hi Eduardo,
In the mail topic we have PATCH 1/1 but I think that it should be PATCH
v3 1/1.
> Different drivers request API extensions in of-thermal. For this
> reason, additional callbacks are required to fit the new drivers
> needs.
>
> The current API implementation expects the registering
QoS requests that need to track an IRQ can be set to apply only on the
cpus to which the IRQ's smp_affinity attribute is set to. The PM QoS
framework will automatically track IRQ migration between the cores. The
QoS is updated to be applied only to the core(s) that the IRQ has been
migrated to.
Export irq_get_affinity API for drivers to read the smp affinity of an
IRQ safely.
Signed-off-by: Lina Iyer
---
include/linux/interrupt.h | 8
kernel/irq/manage.c | 18 ++
2 files changed, 26 insertions(+)
diff --git a/include/linux/interrupt.h
PM QoS constraints like the CPU_DMA_LATENCY, when set, apply to all cpus. The
QoS guarantees performance, at the expense of power. There is an opportunity to
save power on the cpus, if a subset of cpus need not participate in honoring
the QoS request.
The patches do the following -
- Add "type"
From: Praveen Chidambaram
QoS add requests uses a handle to the priority list that is used
internally to save the request, but this does not extend well. Also,
dev_pm_qos structure definition seems to use a list object directly.
The 'derivative' relationship seems to be broken.
Use
QoS request can be better optimized if the request can be set only for
the required cpus and not all cpus. This helps save power on other
cores, while still guaranteeing the quality of service on the desired
cores.
Add a new enumeration to specify the PM QoS request type. The enums help
specify
On Mon, Nov 17, 2014 at 12:23 PM, Michael Ellerman wrote:
> On Fri, 2014-11-14 at 14:42 +0530, Vineeth Vijayan wrote:
>> Now there is no way to disable TEXT randomization on a PPC32/PPC64
>> machine. Text randomization happens even in the case of "echo 0 >
>> /proc/sys/kernel/randomize_va_space"
Hi Felipe,
Today's linux-next merge of the usb-gadget tree got a conflict in
drivers/usb/dwc2/gadget.c between commit 7c3e90537b74 ("usb: dwc2: drop
owner assignment from platform_drivers") from the driver-core tree and
commit 11b2c3bb ("usb: dwc2: Move gadget probe function into
platform
Hi Wolfram,
Thank you for having found the bug, I indeed missed initializing
it('orig_jiffies').
I will do more detailed review and send the v11 soon.
Best Regards,
Yuan Yao
> -Original Message-
> From: Wolfram Sang [mailto:w...@the-dreams.de]
> Sent: Tuesday, November 18, 2014 2:24
Commit dcb18694 "Fix ipi on palmeto" disabled fastsleep at boot time.
Revert this commit since we no longer need this fix. However we can
continue to use powersave_nap parameter to control entry into deep
idle states beyond snooze.
Signed-off-by: Preeti U. Murthy
---
From: San Mehat
serial_core: Add wake_peer uart operation
Add wake_peer which is called before starting UART TX. The idea here
is to provide a mechanism where we can wakeup our peer before sending
data.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: linux-ser...@vger.kernel.org
Cc:
On Mon, Nov 17, 2014 at 04:23:08PM -0800, Juston wrote:
> Seems to be the case. Looked at some old commits (2.6.17) and found
> FMODE_EXEC was mainlined to allow lustre to be installed on a vanilla
> kernel.
We actually only care about the most recent kernel. I think you can
remove the ifdefs in
This new feature is to interpret AMD specific ACPI device to platform device
such as I2C, UART found on AMD CZ and later chipsets. It is based on example
INTEL LPSS. Now, it can support AMD I2C & UART.
Signed-off-by: Ken Xue
Signed-off-by: Jeff Wu
---
arch/x86/Kconfig| 11 +++
This patch introduce kprobeopt for ARM 32.
Limitations:
- Currently only kernel compiled with ARM ISA is supported.
- Offset between probe point and optinsn slot must not larger than
32MiB. Masami Hiramatsu suggests replacing 2 words, it will make
things complex. Futher patch can make
Copy old kprobe to newly alloced optimized_kprobe before
arch_prepare_optimized_kprobe(). Original kprove can brings more
information to optimizer.
v1 -> v2:
- Bugfix: copy p->addr when alloc_aggr_kprobe.
Signed-off-by: Wang Nan
---
kernel/kprobes.c | 6 ++
1 file changed, 6
> -Original Message-
> From: Matt Fleming [mailto:m...@console-pimps.org]
> Sent: Monday, November 17, 2014 11:12 PM
> >
> > - Only doing module unload is required to be aware of this synchronization
> > -> Ensuring the call back does not fall into unloaded code which may
> cause
> >
On 2014/11/18 4:58, Tejun Heo wrote:
> Implement cgroup_get_e_css() which finds and gets the effective css
> for the specified cgroup and subsystem combination. This function
> always returns a valid pinned css. This will be used by cgroup
> writeback support.
>
> While at it, add comment to
Enable OPTPROBES for ARM 32. Previous discussion can be found:
https://lkml.org/lkml/2014/10/25/48
https://lkml.org/lkml/2014/10/22/254
https://lkml.org/lkml/2014/8/27/255
https://lkml.org/lkml/2014/8/12/12
https://lkml.org/lkml/2014/8/8/992
https://lkml.org/lkml/2014/8/8/5
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: "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
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
AArch64 ISA does not instructions to pop PC register value
from 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 context, and
From: Sandeepa Prabhu
Add support for AArch64 instruction simulation in kprobes.
Kprobes need simulation of instructions that cannot be stepped
right-away from different memory location. i.e. those instructions
that uses PC-relative addressing. In simulation, the behaviour
of the instruction is
Any feedback?
/Jarkko
On Tue, Nov 11, 2014 at 03:45:03PM +0200, Jarkko Sakkinen wrote:
> This patch set enables TPM2 protocol and provides drivers for FIFO and
> CRB interfaces.
>
> v2:
> - Improved struct tpm_chip life-cycle by taking advantage of devres
> API.
> - Refined sysfs attributes
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
On 2014/11/14 5:59, Tejun Heo wrote:
> When a subsystem is offlined, its entry on @cgrp->subsys[] is cleared
> asynchronously. If cgroup_subtree_control_write() is requested to
> enable the subsystem again before the entry is cleared, it has to wait
> for the previous offlining to finish and
On Fri, 14 Nov 2014 08:44:12 -0500, kan liang wrote:
> + /* LBR only affects the user callchain */
> + if (i != chain_nr) {
> + struct branch_stack *lbr_stack = sample->branch_stack;
> + int lbr_nr = lbr_stack->nr;
> +
This is part of version 8 of 'ARM: kprobes: enable OPTPROBES for ARM32'.
Its main goal is introducing checker mechanism to give a chance to
detail check each probed instructions. Different from previous version,
this series redesign stack checker following Tixy's advise:
This patch prohibit probing instructions for which the stack
requirement are unable to be determined statically. Some test cases
are found not work again after the modification, this patch also
removes them.
v1 -> v2:
- Use MAX_STACK_SIZE macro instead of hard coded stack size.
Signed-off-by:
This patch use previous introduced checker on store instructions,
record stack consumption informations to arch_probes_insn. With such
information, kprobe opt can decide how much stack needs to be
protected.
v1 -> v2:
- Bugfix and code improvements following Tixy's suggestion. See:
This patch introdces 'checker' to decoding phase, and calls checkers
when instruction decoding. This allows further decoding for specific
instructions.
v1 -> v2:
- kprobe checker stubs are introduced in this patch.
Signed-off-by: Wang Nan
---
arch/arm/kernel/kprobes-arm.c | 2 ++
Hi Thomas,
On Fri, Oct 17 2014 at 01:29 -0600, Thomas Gleixner wrote:
On Fri, 10 Oct 2014, Lina Iyer wrote:
On Wed, Oct 08 2014 at 09:03 -0600, Thomas Gleixner wrote:
> On Thu, 25 Sep 2014, Lina Iyer wrote:
> > > How would a general "keep track of the targets of all interrupts in
> > > the
On Mon, 17 Nov 2014 17:41:32 +, Kan Liang wrote:
>> SNIP
>>
>> > diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
>> > index f4478ce..335c3a9 100644
>> > --- a/tools/perf/util/session.c
>> > +++ b/tools/perf/util/session.c
>> > @@ -557,15 +557,63 @@ int
On Mon, 17 Nov 2014 16:55:53 +0100, Jiri Olsa wrote:
> On Fri, Nov 14, 2014 at 08:44:12AM -0500, kan.li...@intel.com wrote:
>
> SNIP
>
>> +if (lbr) {
>> +for (i = 0; i < chain_nr; i++) {
>> +if (chain->ips[i] == PERF_CONTEXT_USER)
>> +
On Tue, 18 Nov 2014 14:01:32 +0800 Lai Jiangshan wrote:
> On 11/18/2014 12:27 PM, NeilBrown wrote:
> >
> > When there is serious memory pressure, all workers in a pool could be
> > blocked, and a new thread cannot be created because it requires memory
> > allocation.
> >
> > In this situation
On Mon, Nov 17, 2014 at 02:35:34PM +0100, Antoine Tenart wrote:
> This series adds the support for ChipIdea USB2 (ci13xxx) controllers,
> the USB PHYs of the Marvell Berlin SoCs and also adds a reset
> controller for these SoCs.
>
> The reset controller is used by the PHY driver and shares the
>
From: Byungchul Park
Currently, function graph tracer prints "!" or "+" just before
function execution time to signal a function overhead, depending
on the time. Even it is usually enough to do that, we sometimes
need to be signaled for bigger execution time than 100 micro seconds.
For example,
On 11/18/2014 12:27 PM, NeilBrown wrote:
>
> When there is serious memory pressure, all workers in a pool could be
> blocked, and a new thread cannot be created because it requires memory
> allocation.
>
> In this situation a WQ_MEM_RECLAIM workqueue will wake up the
> rescuer thread to do some
From: Byungchul Park
Currently, some tracers tracing latency print "!" or "+" just after time
to signal overhead, depending on the interval between events. Even it is
usually enough to do that, we sometimes need to be signaled for bigger
interval than 100 micro seconds.
Signed-off-by: Byungchul
From: Byungchul Park
Usually, "msecs" notation means milli-seconds, and "usecs" notation
means micro-seconds. Since the unit used in the code is micro-seconds,
the notation should be replaced from msecs to usecs.
Signed-off-by: Byungchul Park
---
kernel/trace/trace_functions_graph.c | 12
From: Byungchul Park
Changes since v3
* re-position define macro and undef explicitly
* enhance readablity
Changes since v2
* use inline function instead of macro
* enhance readablity
Changes since v1
* update Document/trace/ftrace.txt
* seperate the implementation as a macro
* apply the
On 11/17/2014 12:35 AM, Pali Rohár wrote:
On Thursday 23 October 2014 18:45:07 Guenter Roeck wrote:
On Thu, Oct 23, 2014 at 12:37:34PM +0200, Pali Rohár wrote:
On Wednesday 22 October 2014 19:10:05 Guenter Roeck wrote:
On Wed, Oct 22, 2014 at 06:35:53PM +0200, Pali Rohár wrote:
On Wednesday
On Fri, 14 Nov 2014 08:44:10 -0500, kan liang wrote:
> From: Kan Liang
>
> Currently, there are two call chain recording options, fp and dwarf.
> Haswell has a new feature that utilizes the existing LBR facility to
> record call chains. So it provides the third options to record call
> chain.
On Mon, Nov 17, 2014 at 02:35:41PM +0100, Antoine Tenart wrote:
> The generic plaftorm device for ChipIdea drivers is probed by calling
> ci_hdrc_probe. The device structure used is not the one of the specific
> ChipIdea driver but the one of the generic ChipIdea platform device.
>
> This results
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, November 18, 2014 9:58 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 2/2] f2fs:
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, November 18, 2014 9:58 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 1/2] f2fs: fix to call
After commit 5d097109257c03a71845729f8db6b5770c4bbedc
("tun: only queue packets on device"), NETDEV_TX_OK was returned for
dropped packets. This will confuse pktgen since dropped packets were
counted as sent ones.
Fixing this by returning NET_XMIT_DROP to let pktgen count it as error
packet.
Cc:
Hi,
On Monday 17 November 2014 09:10 PM, Heikki Krogerus wrote:
> On Thu, Nov 13, 2014 at 07:03:01PM +0530, Vivek Gautam wrote:
>> How about adding the change in attached patch [1] on top of this patch.
>> Just introduced the phy pointer in "phy_lookup" structure, and
>> modified phy_find()
A Discussion on lennart poettering, systemd, sysv
http://youtu.be/2toVPMHRo8M
--
SystemD Blues.
--
SystemBlues
sdbl...@fastmail.com
--
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
On 2014/11/18 8:59, Thomas Gleixner wrote:
> On Mon, 17 Nov 2014, Jiang Liu wrote:
>> This patch set is based on tip/irq/irqdomain and tries to refine
>> interfaces to support irqdomain for generic MSI and PCI MSI.
>
> So to make progress on that matter I picked that up along with a few
> other
Free software worked great for a time, it was a movement
on the upswing. Then it was noticed. Feminists appeared
and lobbied to have those of unclean mind excluded from
the free/opensource movement, only those who believed
the correct thing were allowed to stay. Code nor contribution
mattered
Kudos to Josselin Mouette a different systemd proponent.
There is an exception to every rule. The rule has been that every
proponent
of systemd thusfar has been a social justice warrior, well really just
an anglo-type feminist (hates men, works to restrict men and raise woman
in his place, there
Blues song about systemd.
A friend of mine and I, we sat down one afternoon,
and there was something bothering us. I for one
couldn't get it out of my head. It was a feeling,
and it wasn't good.
It was the feeling of getting dicked down
by SystemD.
We put this feeling, the feeling we've never
https://www.youtube.com/watch?v=0akuZk_SQpk
Requiem for Linux. Killed by PC, Coup de grace - SystemD (Song included)
GNU/Linux is dead. The final blow being SystemD, brought
to you by the social justice warrior (aka: (male) feminist)
known as Lennart Poettering. A turn coat against all
other
Eventual lament (nylon string guitar):
I was recording one evening and at some point wandered into a lament.
http://youtu.be/PCJ-CWYoY9s
I though many would feel the same, once comes in full lennart's reign.
Please don't let it happen.
(C) Gnu GPL v2
--
To unsubscribe from this list: send the
Dear Mr Schubert;
"He has not contributed anything to the open source community."
This is a complete lie. I've contributed gigabytes of media alone.
I've done years and years of programming work.
I have done far more than you ever will.
"His songs and "games" are not worth looking at,"
Your
On Tue, 18 Nov 2014 07:09:02 +0900, Masami Hiramatsu wrote:
> (2014/11/17 12:17), Masami Hiramatsu wrote:
>> (2014/11/17 12:08), Namhyung Kim wrote:
>>> I prefer this too. But I'd like make the 'add' part a subcommand rather
>>> than option like we do in perf kmem/kvm/list/lock/mem/sched ... And
Hi Arnaldo,
On Mon, 17 Nov 2014 16:58:57 -0200, Arnaldo Carvalho de Melo wrote:
> Em Mon, Nov 17, 2014 at 12:08:59PM +0900, Namhyung Kim escreveu:
>> I prefer this too. But I'd like make the 'add' part a subcommand rather
>> than option like we do in perf kmem/kvm/list/lock/mem/sched ... And it
In the first example, the loads into 'x' and 'y' on CPU 2 doesn't
match the sequence of events described below it. To match the
sequence of events, the values of 'A' and 'B' should be loaded
into 'x' and 'y' respectively.
Signed-off-by: Srikanth Thokala
---
Documentation/memory-barriers.txt |
Hi Masami,
On Mon, 17 Nov 2014 12:17:31 +0900, Masami Hiramatsu wrote:
> (2014/11/17 12:08), Namhyung Kim wrote:
>> I prefer this too. But I'd like make the 'add' part a subcommand rather
>> than option like we do in perf kmem/kvm/list/lock/mem/sched ... And it
>> can handle multiple files at
On Tue, Nov 18, 2014 at 09:21:24AM +0800, Kever Yang wrote:
> After we implement the bus_suspend/resume, auto suspend id enabled.
> The root hub will be auto suspend if there is no device connected,
> we need to resume the root hub when a device connect detect.
>
> This patch tested on rk3288.
>
Jiri reported that the commit 96d78059d6d9 ("perf tools: Make vmlinux
short name more like kallsyms short name") segfaults on perf script.
When processing kernel mmap event, it should access the 'kernel'
variable as sometimes it cannot find a matching dso from build-id
table so 'dso' might be
When there is serious memory pressure, all workers in a pool could be
blocked, and a new thread cannot be created because it requires memory
allocation.
In this situation a WQ_MEM_RECLAIM workqueue will wake up the
rescuer thread to do some work.
The rescuer will only handle requests that are
On 11/17/2014 03:26 PM, Mark Brown wrote:
On Mon, Nov 17, 2014 at 01:00:09PM -0800, Guenter Roeck wrote:
On Fri, Oct 17, 2014 at 08:17:03AM -0700, Guenter Roeck wrote:
To avoid the problem, prepend the debugfs directory name for a regulator
with its parent device name if available, but only
Hi kan,
On Mon, 17 Nov 2014 09:52:19 -0500, kan liang wrote:
> From: Kan Liang
>
> Sometime, especially debugging scaling issue, the function level diff
> may be high granularity. The user may want to do deeper diff analysis
> for some cache or lock issue. The "symoff" key can let the user sort
On Thu, Oct 30, 2014 at 07:40:29PM -0400, Dave Jones wrote:
> WARNING: CPU: 3 PID: 5167 at kernel/events/core.c:1133
> add_event_to_ctx+0x1ce/0x1f0()
> CPU: 3 PID: 5167 Comm: trinity-c4 Not tainted 3.18.0-rc2+ #79
> 0009 71bbcfa0 880235ef3c48 bd86ef44
>
On Tue, Nov 18, 2014 at 02:51:45AM +, Tobenna Peter, Igwe wrote:
> On Mon, Nov 17, 2014 at 05:59:47PM -0800, Greg KH wrote:
> > On Tue, Nov 18, 2014 at 01:45:41AM +, Tobenna P. Igwe wrote:
> > > This patch fixes the following sparse warning:
> > >
> > >
"Rafael J. Wysocki" writes:
> From: Rafael J. Wysocki
>
> The number of and dependencies between high-level power management
> Kconfig options make life much harder than necessary. Several
> conbinations of them have to be tested and supported, even though
> some of those combinations are very
On 11/17/2014 03:17 PM, Paul E. McKenney wrote:
On Mon, Nov 17, 2014 at 01:11:57PM -0800, Alexander Duyck wrote:
On 11/17/2014 12:18 PM, Paul E. McKenney wrote:
On Mon, Nov 17, 2014 at 09:18:13AM -0800, Alexander Duyck wrote:
There are a number of situations where the mandatory barriers
(2014/11/15 3:34), Rafael Aquini wrote:
> Minor fixlet to perform the reserved pages counter aggregation
> for each node, at show_mem()
>
> Signed-off-by: Rafael Aquini
> ---
Acked-by: Yasuaki Ishimatsu
Thanks,
Yasuaki Ishimatsu
> lib/show_mem.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On 11/17/2014 06:11 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 17, 2014 at 10:44:30AM +0100, Cornelia Huck wrote:
>> On Mon, 17 Nov 2014 11:37:01 +0200
>> "Michael S. Tsirkin" wrote:
>>
>>> On Mon, Nov 17, 2014 at 05:17:17PM +0800, Jason Wang wrote:
Buggy host may advertised buggy host
Hi Brian,
On 11/17/2014 19:00, bri wrote:
Yeah, the device ID in the driver is only for tracking devices internally
and setting sane default LED values. It has no meaning outside of the
module. Like Antonio said, if you want the system number for a controller
you are better off just getting
So far the only difference between v5 I have is that I split the update
of tracing_fill_pipe_page() out of "tracing: Use trace_seq_used() and
seq_buf_used() instead of len", and this:
-- Steve
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 9f1ffc707f3b..9023446b2c2b 100644
---
On 11/17/2014 04:39 PM, Benjamin Herrenschmidt wrote:
On Mon, 2014-11-17 at 12:24 -0800, Alexander Duyck wrote:
Yes and no. So for example on ARM I used the dmb() operation, however
I
have to use the barrier at the system level instead of just the inner
shared domain. However on many other
Now in f2fs, we have three inode cache: ORPHAN_INO, APPEND_INO, UPDATE_INO,
and we manage fields related to inode cache separately in struct f2fs_sb_info
for each inode cache type.
This makes codes a bit messy, so that this patch intorduce a new struct
inode_management to wrap inner fields as
Because we have checked the contrary condition in case of "if" judgment, we do
not need to check the condition again in case of "else" judgment. Let's remove
it.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/super.c
In f2fs_remount, we will stop gc thread and set need_restart_gc as true when new
option is set without BG_GC, then if any error occurred in the following
procedure, we can restore to start the gc thread.
But after that, We will fail to restore gc thread in start_gc_thread as BG_GC is
not set in
On Fri, Nov 14, 2014 at 10:33:01AM +, Mel Gorman wrote:
> > > diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> > > index 4593567..3d090af 100644
> > > --- a/include/linux/mmzone.h
> > > +++ b/include/linux/mmzone.h
> > > @@ -431,6 +431,15 @@ struct zone {
> > > */
> > >
On Mon, Nov 17, 2014 at 11:31 PM, Geert Uytterhoeven
wrote:
> It doesn't make much sense to make some (possible expensive) calls to
> gpio_is_valid() first, and to ignore the result if the base number is
> negative. Check for a positive base number first.
Sure.
Reviewed-by: Alexandre Courbot
On Mon, 17 Nov 2014 21:44:11 -0500
Steven Rostedt wrote:
> On Tue, 18 Nov 2014 09:49:12 +0900
> Namhyung Kim wrote:
>
> > > - ret = trace_seq_printf(s, "%s(", entry->name);
> > > - if (!ret)
> > > - return TRACE_TYPE_PARTIAL_LINE;
> > > + trace_seq_printf(s, "%s(", entry->name);
> > >
On 11/17/2014 06:08 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 17, 2014 at 05:17:18PM +0800, Jason Wang wrote:
>> This patch tries to detect the possible buggy features advertised by host
>> and sanitize them. One example is booting virtio-net with only ctrl_vq
>> disabled, qemu may still
Kever,
On Mon, Nov 17, 2014 at 5:21 PM, Kever Yang wrote:
> After we implement the bus_suspend/resume, auto suspend id enabled.
> The root hub will be auto suspend if there is no device connected,
> we need to resume the root hub when a device connect detect.
>
> This patch tested on rk3288.
>
>
On Mon, 17 Nov 2014 18:50:52 -0800
Joe Perches wrote:
> On Mon, 2014-11-17 at 21:37 -0500, Steven Rostedt wrote:
> > On Mon, 17 Nov 2014 17:48:37 -0800
> > Joe Perches wrote:
> > > On Mon, 2014-11-17 at 20:24 -0500, Steven Rostedt wrote:
> > > > On Mon, 17 Nov 2014 17:07:58 -0800
> > > > Joe
From: "Kweh, Hock Leong"
When using request_firmware_nowait() with FW_ACTION_NOHOTPLUG param to
expose user helper interface, if the user do not react immediately, after
120 seconds there will be a hung task warning message dumped as below:
[ 3000.784235] INFO: task kworker/0:0:8259 blocked for
On Mon, Nov 17, 2014 at 05:59:47PM -0800, Greg KH wrote:
> On Tue, Nov 18, 2014 at 01:45:41AM +, Tobenna P. Igwe wrote:
> > This patch fixes the following sparse warning:
> >
> > drivers/staging/rtl8723au/hal/rtl8723a_bt-coexist.c:343:36: warning:
> > cast to restricted __le16
> >
> > by
On Mon, Nov 17, 2014 at 6:39 PM, Dave Jones wrote:
>
> So it could be that I'm just generating a lot more load now.
> I could drop that back down and see if it 'goes away' or at least
> happens less, but it strikes me that there's something here that needs
> fixing regardless.
Oh, absolutely.
On Mon, 2014-11-17 at 21:37 -0500, Steven Rostedt wrote:
> On Mon, 17 Nov 2014 17:48:37 -0800
> Joe Perches wrote:
> > On Mon, 2014-11-17 at 20:24 -0500, Steven Rostedt wrote:
> > > On Mon, 17 Nov 2014 17:07:58 -0800
> > > Joe Perches wrote:
> > > > > Look at the next patch.
> > > > I don't have
I observe that dl task can't be migrated to other cpus during cpu hotplug,
in addition, task may/may not be running again if cpu is added back. The
root cause which I found is that dl task will be throtted and removed from
dl rq after comsuming all budget, which leads to stop task can't pick it up
On Tue, 18 Nov 2014 09:49:12 +0900
Namhyung Kim wrote:
> On Thu, 13 Nov 2014 20:12:55 -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > The functions trace_seq_printf() and friends will not be returning values
> > soon and will be void functions. To know if they
1 - 100 of 1742 matches
Mail list logo
