On Thursday 22 October 2015 08:34:53 Appana Durga Kedareswara Rao wrote:
> > On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
> > > The driver only supports memory-mapped I/O [by ioremap()], so
> > > readl/writel is actually the right thing to do, IMO.
> > > During the validation
On Wed, Oct 21, 2015 at 02:16:14PM +0100, Nikesh Oswal wrote:
> From: Nikesh Oswal
If you are going to use your non-opensource email, might as well
use the cirrus one here.
>
> A binary search is much more efficient rather than iterating
> over the rbtree in ascending order which the current
On Wed, Oct 21, 2015 at 10:07:44PM -0600, Jens Axboe wrote:
> On 10/21/2015 06:31 PM, Tejun Heo wrote:
> >Hello, Jens.
> >
> >This is one of hopefully final adjustments to cgroup v2 behavior
> >before lifting the devel mask. If the patch is okay, can I route the
> >patch through cgroup/for-4.4 so
On Thu, Oct 22, 2015 at 10:21:36AM +0900, Minchan Kim wrote:
> Hello Hugh,
>
> On Wed, Oct 21, 2015 at 05:59:59PM -0700, Hugh Dickins wrote:
> > On Thu, 22 Oct 2015, Minchan Kim wrote:
> > >
> > > I added the code to check it and queued it again but I had another oops
> > > in this time but
On Thu, Oct 22, 2015 at 11:40 AM, Christoph Hellwig wrote:
> On Tue, Oct 20, 2015 at 01:53:42PM +0300, Daniel Baluta wrote:
>> We don't want to hardcode default groups at subsystem
>> creation time. We export:
>> * configfs_register_group
>> * configfs_unregister_group
>> to allow
On Thursday 22 October 2015 10:21:58 Marc Kleine-Budde wrote:
> On 10/22/2015 10:14 AM, Arnd Bergmann wrote:
> > On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
> >> The driver only supports memory-mapped I/O [by ioremap()],
> >> so readl/writel is actually the right thing to
On Thu, 22 Oct 2015 10:47:35 +0200
Maxime Ripard wrote:
> Not really. The uart0 reset is the bit 16, in the reset register 4.
>
> 4 * 32 + 16 = 44.
>
> Not 112, but still not 208 either.
The registers are numbered 1..5, then
(4 - 1) * 32 + 16 = 112
--
Ken ar c'hentañ | **
Hello,
On Wed, Oct 21, 2015 at 10:39:32AM +0530, Vinayak Kale wrote:
...
> > diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
> > index 0d7f0da..5b0a5ab 100644
> > --- a/drivers/ata/libata-scsi.c
> > +++ b/drivers/ata/libata-scsi.c
> > @@ -2914,12 +2914,14 @@
Hi,
On 22-10-15 09:49, Jens Kuske wrote:
Hi,
On 21/10/15 21:18, Hans de Goede wrote:
Great to see that you've started working on this again. Last weekend I
ended up working on this too together with Reinder E.N. de Haan
(added to the Cc).
We took a slightly different approach for the
Hello,
On Mon, Oct 19, 2015 at 07:40:13AM -0700, Zhangqing Luo wrote:
> So every time blk_mq_freeze_queue_start, it runs in this way
>
> blk_mq_freeze_queue_start
> ->percpu_ref_kill->percpu_ref_kill_and_confirm
> ->__percpu_ref_switch_to_atomic
>
On Thu, Oct 22, 2015 at 10:29:59AM +0200, Jean-Francois Moine wrote:
> On Thu, 22 Oct 2015 10:05:08 +0200
> Maxime Ripard wrote:
>
> > > + uart0: serial@01c28000 {
> > > + compatible = "snps,dw-apb-uart";
> > > + reg = <0x01c28000 0x400>;
> > > +
* Arnaldo Carvalho de Melo wrote:
> > 5) --no-children
> >
> > I agree that 'perf top -g --no-children' looks more intuitive than 'perf
> > top -g'.
>
> So, what do you propose, to switch back the default to --no-children, for
> both
> tools, top and report? Now that I am getting used to
Since nested variants of mdiobus_read/write are used in multiple
drivers, add nested variants in the mdiobus core.
Suggested-by: Andrew Lunn
Signed-off-by: Neil Armstrong
---
drivers/net/phy/mdio_bus.c | 55 ++
include/linux/phy.h| 2 ++
2
In order to avoid locked signal false positive for nested mdiobus
read/write calls, nested code was introduced in mv88e6xxx and
mdio-mux.
But mv88e6060 also needs such nested mdiobus read/write calls.
For sake of refactoring, introduce nested variants of mdiobus read/write
and make them used by
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde [mailto:m...@pengutronix.de]
> Sent: Thursday, October 22, 2015 1:52 PM
> To: Arnd Bergmann; linux-arm-ker...@lists.infradead.org
> Cc: Appana Durga Kedareswara Rao; Anirudha Sarangi; w...@grandegger.com;
> Michal Simek; Soren
On Tue, Oct 20, 2015 at 01:53:42PM +0300, Daniel Baluta wrote:
> We don't want to hardcode default groups at subsystem
> creation time. We export:
> * configfs_register_group
> * configfs_unregister_group
> to allow drivers to programatically create/destroy groups
> later, after module
Like mv88e6xxx and mdio-mux, to avoid lockdep give false positives
because of nested MDIO busses, switch to previously introduced
nested mdiobus_read/write variants.
Signed-off-by: Neil Armstrong
---
drivers/net/dsa/mv88e6060.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
This reuses the code of drivers/tty/serial/8250/8250_early.c except
- Overwrite device->port.iotype and device->port.regshift for
UPIO_MEM32 because of_setup_earlycon() has set them for UPIO_MEM.
- Set device->baud to zero to prevent early8250_setup() from
initializing the divisor
Make the mv88e6xxx driver use the previously introduced nested
variants of mdiobus_read/write functions.
Signed-off-by: Neil Armstrong
---
drivers/net/dsa/mv88e6xxx.c | 46 +
1 file changed, 9 insertions(+), 37 deletions(-)
diff --git
On Thu, Oct 22, 2015 at 01:27:28AM -0400, Jason Wang wrote:
> This path introduces a helper which can give a hint for whether or not
> there's a work queued in the work list.
>
> Signed-off-by: Jason Wang
> ---
> drivers/vhost/vhost.c | 6 ++
> drivers/vhost/vhost.h | 1 +
> 2 files
Hi!
On Wed, Oct 21, 2015 at 04:33:53PM -0700, Stephen Boyd wrote:
> These APIs aren't used, so remove them. This can be reverted if
> we get a user at some point.
>
> Cc: Maxime Ripard
> Suggested-by: Michael Turquette
> Signed-off-by: Stephen Boyd
Reviewed-by: Maxime Ripard
Thanks!
Maxime
Hello Anand,
On 10/22/2015 07:03 AM, Anand Moon wrote:
> Hi Javier,
>
> On 22 October 2015 at 08:22, Javier Martinez Canillas
> wrote:
>> Hello Krzysztof,
>>
>> On 10/22/2015 03:43 AM, Krzysztof Kozlowski wrote:
>>> On 22.10.2015 10:20, Javier Martinez Canillas wrote:> Hello Krzysztof,
Hi Arnd,
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Thursday, October 22, 2015 1:45 PM
> To: linux-arm-ker...@lists.infradead.org
> Cc: Appana Durga Kedareswara Rao; Anirudha Sarangi; w...@grandegger.com;
> m...@pengutronix.de; Michal Simek; Soren
Destroy mcb_ida on module_unload
Signed-off-by: Johannes Thumshirn
---
drivers/mcb/mcb-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mcb/mcb-core.c b/drivers/mcb/mcb-core.c
index 9018ab8..a4be451 100644
--- a/drivers/mcb/mcb-core.c
+++ b/drivers/mcb/mcb-core.c
@@ -409,6
> On 22 okt. 2015, at 19:28, Taku Izumi wrote:
>
> commit-0f96a99 introduces the following warning message:
>
> drivers/firmware/efi/fake_mem.c:186:20: warning: cast to pointer
> from integer of different size [-Wint-to-pointer-cast]
>
> new_memmap_phy was defined as a u64 value and casted
Hi Vinod,
Thanks for your review, please see my comments inline.
Best Regards,
Yuan Yao
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Monday, October 05, 2015 10:37 PM
> To: Yuan Yao-B46683
> Cc: shawn@linaro.org; dan.j.willi...@intel.com;
>
Hi,
On Thu, Oct 22, 2015 at 01:21:26AM -0700, josef.gajdu...@gmail.com wrote:
> Hi everyone,
>
> I might be missing something, but why is the PL* GPIO bank not
> declared here?
Because it's in the PRCM. This one was adding support for the main
port controller.
Maxime
--
Maxime Ripard, Free
On Thu, 22 Oct 2015 10:05:08 +0200
Maxime Ripard wrote:
> > + uart0: serial@01c28000 {
> > + compatible = "snps,dw-apb-uart";
> > + reg = <0x01c28000 0x400>;
> > + interrupts = ;
> > + reg-shift = <2>;
> > +
commit-0f96a99 introduces the following warning message:
drivers/firmware/efi/fake_mem.c:186:20: warning: cast to pointer
from integer of different size [-Wint-to-pointer-cast]
new_memmap_phy was defined as a u64 value and casted to void*.
This causes a warning of int-to-pointer-cast on x86
d page futexes with the following panic:
[ 33.465456] general protection fault: [#1] SMP
[ 33.465991] CPU: 1 PID: 523 Comm: tst Not tainted 4.3.0-rc6-next-20151022
#139
[ 33.466585] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.7.5-20140709_153950- 04/01/2014
[
* Namhyung Kim wrote:
> Currently 'perf top --call-graph' option is same as 'perf record'. But
> 'perf top' also need to receive display options in 'perf report'. To do
> that, change parse_callchain_report_opt() to allow record options too.
>
> Now perf top can receive display options like
On 10/22/2015 10:14 AM, Arnd Bergmann wrote:
> On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
>> The driver only supports memory-mapped I/O [by ioremap()],
>> so readl/writel is actually the right thing to do, IMO.
>> During the validation of this driver or IP on ARM 64-bit
The IER has already been masked in early_serial8250_setup(), there is
no reason to save and restore it every time early_serial8250_write()
is called.
Let wait_for_xmitr() melt into serial_putc().
Signed-off-by: Masahiro Yamada
---
drivers/tty/serial/8250/8250_early.c | 20 ++--
On Wed, Oct 21, 2015 at 06:30:46PM +0200, Jens Kuske wrote:
> The H3 uses the same pin controller as previous SoC's from Allwinner.
> Add support for the pins controlled by the main PIO controller.
>
> Signed-off-by: Jens Kuske
Acked-by: Maxime Ripard
Thanks!
Maxime
--
Maxime Ripard, Free
On Thursday 22 October 2015 10:16:02 Kedareswara rao Appana wrote:
> The driver only supports memory-mapped I/O [by ioremap()],
> so readl/writel is actually the right thing to do, IMO.
> During the validation of this driver or IP on ARM 64-bit processor
> while sending lot of packets observed
On 10/21/2015 06:14 PM, Andrew Lunn wrote:
> On Wed, Oct 21, 2015 at 05:37:45PM +0200, Neil Armstrong wrote:
>> Like the change made for mv88e6xxx, use mutex_lock_nested() to avoid
>> lockdep to give false positives because of nested MDIO busses.
>
> Hi Neil
>
> We now have three instances of
On 10/21/2015 06:14 PM, Andrew Lunn wrote:
> On Wed, Oct 21, 2015 at 05:37:45PM +0200, Neil Armstrong wrote:
>> Like the change made for mv88e6xxx, use mutex_lock_nested() to avoid
>> lockdep to give false positives because of nested MDIO busses.
>
> Hi Neil
>
> We now have three instances of
This patch changes return type of pstore_is_mounted from int to bool.
Signed-off-by: Geliang Tang
---
fs/pstore/inode.c| 2 +-
fs/pstore/internal.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
index 3586491..d8c439d 100644
---
On 2015/10/22 15:53, Namhyung Kim wrote:
On Thu, Oct 22, 2015 at 4:29 PM, Wangnan (F) wrote:
[SNIP]
I understand the need of using aliases but I think it's more natural
to use event name for simple cases..
I will consider this. However, if we allow using event name directly like
this:
Hi,
On Wed, Oct 21, 2015 at 06:20:27PM +0200, Jens Kuske wrote:
> The Allwinner H3 is a home entertainment system oriented SoC with
> four Cortex-A7 cores and a Mali-400MP2 GPU.
>
> Signed-off-by: Jens Kuske
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 499
>
On Mon, Oct 19, 2015 at 06:00:04PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 16, 2015 at 12:40:54PM +0200, Jiri Olsa escreveu:
> > It'll server as base event for additional event attributes
> > details, that are not part of the attr event.
> >
> > At the moment this event is just dummy
This patch adds a comment before waitqueue_active noting that memory
barriers are required.
In the following code, the wake_up thread might fail to wake up the
waiting thread and leave it sleeping due to lack of memory barriers.
wake_up thread waiting thread
* Namhyung Kim wrote:
> +#define CALLCHAIN_HELP "setup and enables call-graph (stack chain/backtrace)
> recording: "
> +
> +#ifdef HAVE_DWARF_UNWIND_SUPPORT
> +#define CALLCHAIN_RECORD_HELP CALLCHAIN_HELP "fp dwarf lbr"
> +#else
> +#define CALLCHAIN_RECORD_HELP CALLCHAIN_HELP "fp lbr"
>
On Tue, 20 Oct 2015, Thomas Gleixner wrote:
> On Tue, 20 Oct 2015, Russell King - ARM Linux wrote:
> > I think Rob's patches need another review in light of this, to determine
> > how much breakage there is here, and a decision how to proceed made on
> > that basis.
>
> I'll go over them tomorrow
Peter Zijlstra wrote:
> On Fri, Oct 09, 2015 at 12:35:59AM +, Kosuke Tatsukawa wrote:
>> This patch adds a comment before waitqueue_active noting that a memory
>> barrier is required.
>>
>> Besides the original problem in drivers/tty/n_tty.c which caused a
>> program stall (described in
On Wed, 21 Oct 2015 21:18:45 +0200
Hans de Goede wrote:
> Great to see that you've started working on this again. Last weekend I
> ended up working on this too together with Reinder E.N. de Haan
>
> (added to the Cc).
>
> We took a slightly different approach for the gates clocks, see:
>
>
>
> When migrating anonymous memory from system memory to device memory
> CPU pte are replaced with special HMM swap entry so that page fault,
> get user page (gup), fork, ... are properly redirected to HMM helpers.
>
> This patch only add the new swap type entry and hooks HMM helpers
>
On Wed, Oct 21, 2015 at 06:20:26PM +0200, Jens Kuske wrote:
> Adding a new compatible allows us to define SoC specific behaviour
> if necessary, for example forcing a particular device out of reset
> even if no driver is actually using it.
>
> Signed-off-by: Jens Kuske
Acked-by: Maxime Ripard
On Mon, Oct 19, 2015 at 05:45:02PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 16, 2015 at 12:40:40PM +0200, Jiri Olsa escreveu:
> > Adding cpu_map event to pass/store cpu maps
> > as data in pipe/perf.data.
> >
> > We store maps in 2 formats:
> > - list of cpus
> > - mask of cpus
>
On 2015/10/22 15:39, Ingo Molnar wrote:
* Wangnan (F) wrote:
[SNIP]
In summary, your either-or logic doesn't hold in BPF world. A BPF
program can only access perf event in a highly restricted way. We
don't allow it calling perf_event_read_local() across core, so it
can't.
Urgh, that's
On Thu, Oct 22, 2015 at 4:29 PM, Wangnan (F) wrote:
>
>
> On 2015/10/22 15:16, Namhyung Kim wrote:
>>
>> Hi,
>>
>> On Wed, Oct 21, 2015 at 10:00 PM, Wangnan (F) wrote:
>>>
>>>
>>> On 2015/10/21 16:53, Namhyung Kim wrote:
Hi,
On Wed, Oct 14, 2015 at 12:41:37PM +, Wang Nan
On Thursday 22 October 2015 07:02:14 subha...@codeaurora.org wrote:
> >
> > Required properties:
> > -- compatible: compatible list, contains "jedec,ufs-1.1"
> > +- compatible: compatible list, contains "jedec,ufs-1.1" or
> > + "qcom,msm8994-ufshc" or
On 22/10/15 02:15, Julian Calaby wrote:
>
> This hunk should be in patch 1:
Indeed, Thanks.
Jens
>
>> @@ -1000,9 +1005,8 @@ static void __init sunxi_divs_clk_setup(struct
>> device_node *node,
>>
>> for (i = 0; i < SUNXI_DIVS_BASE_NAME_MAX_LEN - 1 &&
>>
Hi,
On 21/10/15 21:18, Hans de Goede wrote:
>
> Great to see that you've started working on this again. Last weekend I
> ended up working on this too together with Reinder E.N. de Haan
>
> (added to the Cc).
>
> We took a slightly different approach for the gates clocks, see:
>
>
Hello,
> diff --git a/include/linux/eventfd.h b/include/linux/eventfd.h
> index ff0b981..87de343 100644
> --- a/include/linux/eventfd.h
> +++ b/include/linux/eventfd.h
>
> -/*
> - * CAREFUL: Check include/uapi/asm-generic/fcntl.h when defining
> - * new flags, since they might collide with O_*
The caller callchain order is useful with --children option since it can
show 'overview' style output, but other commands which don't use
--children feature like 'perf script' or even 'perf report/top' without
--children are better to keep callee order.
Cc: Adrian Hunter
Cc: Borislav Petkov
On Thu, 22 Oct 2015, Yang Yingliang wrote:
> I use the kernel-4.1.6 running on arm64.
> My testcase is that it calls clock_settime and clock_adjtime alternately with
> random params on each core. My system has 32 cores.
>
> I found the cpu stalling in hrtimer_intterrupts(). So I added some debug
* Wangnan (F) wrote:
>
>
> On 2015/10/22 0:57, Peter Zijlstra wrote:
> >On Wed, Oct 21, 2015 at 11:06:47PM +0800, pi3orama wrote:
> >>>So explain; how does this eBPF stuff work.
> >>I think I get your point this time, and let me explain the eBPF stuff to
> >>you.
> >>
> >>You are aware that
On 2015/10/22 14:21, Alexei Starovoitov wrote:
On 10/21/15 10:31 PM, Wangnan (F) wrote:
+if ((attr->type != PERF_TYPE_RAW &&
+ !(attr->type == PERF_TYPE_SOFTWARE &&
+ attr->config == PERF_COUNT_SW_BPF_OUTPUT) &&
+ attr->type != PERF_TYPE_HARDWARE) ||
+
Hi Ingo,
On Thu, Oct 22, 2015 at 4:32 PM, Ingo Molnar wrote:
>
> * Namhyung Kim wrote:
>
>> The caller callchain order is useful with --children option since it can
>> show 'overview' style output, but other commands which don't use
>> --children feature like 'perf script' or even 'perf
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 43e41adc9e8c36545888d78fed2ef8d102a938dc:
>
> perf record: Add ability to sample call branches (2015-10-20 10:30:55 +0200)
>
> are available in the git
Hi Andrew,
On 10/21/2015 06:14 PM, Andrew Lunn wrote:
> On Wed, Oct 21, 2015 at 05:37:45PM +0200, Neil Armstrong wrote:
>> Like the change made for mv88e6xxx, use mutex_lock_nested() to avoid
>> lockdep to give false positives because of nested MDIO busses.
>
> Hi Neil
>
> We now have three
* Namhyung Kim wrote:
> The caller callchain order is useful with --children option since it can
> show 'overview' style output, but other commands which don't use
> --children feature like 'perf script' or even 'perf report/top' without
> --children are better to keep caller order.
>
> Cc:
earliest_dl.next is used to cache the next earliest ready task
which also is pushable in order to be a candidate of pushable
tasks during pull algorithm. If the earliest_dl.next deadline
of the sr_rq is earlier than the earliest_dl.curr deadline of
current rq, the task from the sr_rq can be
On 2015/10/22 15:16, Namhyung Kim wrote:
Hi,
On Wed, Oct 21, 2015 at 10:00 PM, Wangnan (F) wrote:
On 2015/10/21 16:53, Namhyung Kim wrote:
Hi,
On Wed, Oct 14, 2015 at 12:41:37PM +, Wang Nan wrote:
From: He Kuang
This patch adds new bison rules for specifying an alias name to a
On Sat, Oct 17, 2015 at 11:33 PM, Alexey Khoroshilov
wrote:
> There is an error path in mcb_pci_probe() where
> it returns zero instead of error code.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
> ---
> drivers/mcb/mcb-pci.c | 1 +
>
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: 21 October 2015 23:15
> To: Wangzhou (B)
> Cc: Bjorn Helgaas; jingooh...@gmail.com; pratyush.an...@gmail.com; Arnd
> Bergmann; li...@arm.linux.org.uk; thomas.petazz...@free-electrons.com;
> Gabriele Paoloni;
On Thu, 2015-10-22 at 04:16 +0530, Muhammad Falak R Wani wrote:
> Remove boilerplate code by using macro module_pci_driver.
> For drivers whose __init and __exit paths only register and
> unregister to the pci API, it is preferred to use this macro.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
On Thu, 2015-10-22 at 03:53 +0530, Muhammad Falak R Wani wrote:
> Use struct pci_device_id instead of DEFINE_PCI_DEVICE_TABLE with
> the goal of getting rid of this macro completely, as this macro
> is deprecated.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
> drivers/scsi/wd719x.c | 2 +-
>
Looks good to me.
Reviewed-by: Subhash Jadavani
> When sending a query to the device returns with a timeout error,
> we clear the corresponding bit in the DOORBELL register but
> we don't clear the outstanding_request field as we should.
> This patch fixes this bug.
>
> Signed-off-by: Yaniv
Looks good to me.
Reviewed-by: Subhash Jadavani
> A race condition appear to exist between request completion when
> scsi_done() is called to end the request and set the tag back to
> -1 (at blk_queue_end_tag() scsi_end_request), and scsi layer error
> handling which aborts the command and
Hi,
On Wed, Oct 21, 2015 at 10:00 PM, Wangnan (F) wrote:
>
>
> On 2015/10/21 16:53, Namhyung Kim wrote:
>>
>> Hi,
>>
>> On Wed, Oct 14, 2015 at 12:41:37PM +, Wang Nan wrote:
>>>
>>> From: He Kuang
>>>
>>> This patch adds new bison rules for specifying an alias name to a perf
>>> event,
Hi Fida,
On 10/21/2015 12:58 PM, Fida Mohammad wrote:
Use of resource managed function devm_led_classdev_register to
make initialization path simpler. Also removed redundant remove
function.
Signed-off-by: Fida Mohammad
---
drivers/leds/leds-wrap.c | 26 --
1 file
Looks good to me.
Reviewed-by: Subhash Jadavani
> Some of the data structures (like response UPIU) and/or its elements
> (unused fields) should be cleared before sending out the respective
> command to UFS device.
>
> This change clears the UPIU response data structure for query commands
> and
Integer metric needs fixed point arithmetic. In sched/fair, a few
metrics, e.g., weight, load, load_avg, util_avg, freq, and capacity,
may have different fixed point ranges, which makes their update and
usage error-prone.
In order to avoid the errors relating to the fixed point range, we
definie
After cleaning up the sched metrics, these two definitions that cause
ambiguity are not needed any more. Use NICE_0_LOAD_SHIFT and NICE_0_LOAD
instead (the names suggest clearly who they are).
Suggested-by: Ben Segall
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c | 4 ++--
Currently, load_avg = scale_load_down(load) * runnable%. This does
not make much sense, because load_avg is primarily the load that
takes runnable time ratio into account.
We therefore remove scale_load_down() for load_avg. But we need to
carefully consider the overflow risk if load has higher
Hi Peter and Ingo,
As discussed recently, the sched metrics need a little bit cleanup. This
series of patches attempt to do that: refactor, rename, remove...
Thanks a lot to Ben, Morten, Dietmar, Vincent, and others who provided
valuable comments.
v2 changes:
- Rename SCHED_RESOLUTION_SHIFT to
Rename scale_load() and scale_load_down() to user_to_kernel_load()
and kernel_to_user_load() respectively, to allow the names to bear
what they are really about.
Signed-off-by: Yuyang Du
[update calculate_imbalance]
Signed-off-by: Vincent Guittot
---
kernel/sched/core.c | 8
These sched metrics have become complex enough. We introduce them
at their definition.
Signed-off-by: Yuyang Du
---
include/linux/sched.h | 60 +--
1 file changed, 49 insertions(+), 11 deletions(-)
diff --git a/include/linux/sched.h
The increased load resolution (fixed point arithmetic range) is
unconditionally deactivated with #if 0.
As the increased load range is still used somewhere (e.g., in Google),
we want to keep this feature. We define CONFIG_CFS_INCREASE_LOAD_RANGE
and it depends on FAIR_GROUP_SCHED and 64BIT and
Hi Ingi,
Thanks for catching this, applied.
On 10/22/2015 03:14 AM, Ingi Kim wrote:
flash-timeout-us property name is changed to flash-max-timeout-us.
This patch fixes that name
Signed-off-by: Ingi Kim
---
Documentation/devicetree/bindings/leds/leds-aat1290.txt | 8
1 file
>
> -int copy_page_range(struct mm_struct *dst, struct mm_struct *src,
> - struct vm_area_struct *vma);
> +int copy_page_range(struct mm_struct *dst_mm, struct mm_struct *src_mm,
> + struct vm_area_struct *dst_vma,
> + struct vm_area_struct
Hi,
On 10/22/2015 07:35 AM, Wanpeng Li wrote:
[...]
Now, if I understand correctly the issue is that dl_task_timer() does:
rq = task_rq_lock(p, );
[...]
if (has_pushable_dl_tasks(rq))
push_dl_task(rq);
with task_rq_lock() that pins rq->lock and push_tl_task() that invokes
Looks good to me.
Reviewed-by: Subhash Jadavani
> New revisions of UFS host controller supports the new UniPro
> hardware controller (referred as QUniPro). This patch adds
> the support to enable this new UniPro controller hardware.
>
> This change also adds power optimization for bus scaling
Looks good to me.
Reviewed-by: Subhash Jadavani
> Adds support for configuring and reading the test bus and debug
> registers. This change also adds another vops in order to print the
> debug registers.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 165
>
Comments inline below:
> This change turns the UFS variant (SCSI_UFS_QCOM) into a UFS
> a platform device.
> In order to do so a few additional changes are required:
> 1. The ufshcd-pltfrm is no longer serves as a platform device.
>Now it only serves as a group of platform APIs such as PM
Looks good to me.
Reviewed-by: Subhash Jadavani
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 34 +-
> drivers/scsi/ufs/ufshcd.h | 21 +
> 2 files changed, 38 insertions(+), 17 deletions(-)
>
> diff --git
Looks good to me.
Reviewed-by: Subhash Jadavani
> This change is required in order to be able to build the component
> as a module.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Looks good to me.
Reviewed-by: Subhash Jadavani
> In order to simplify the code a set of wrapper functions is created
> to test and call each of the variant operations.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 1 -
> drivers/scsi/ufs/ufshcd.c | 104
>
On Wed, Oct 21, 2015 at 10:07 PM, Punit Vara wrote:
> Remove int ret suggested by kbuild test robot
>
> This patch is to the wlcore/acx.c file that fixes up warning
> reported by coccicheck:
>
> WARNING: end returns can be simplified if negative or 0 value
>
> Prefer direct return value instead
Looks good to me.
Reviewed-by: Subhash Jadavani
> This change fixes a compilation warning that happens if SCSI_UFS_QCOM
> is compiled as a module.
> Also this patch fixes an error happens when insmod the module:
> "ufs_qcom: module license 'unspecified' taints kernel."
>
> Signed-off-by: Yaniv
The hifn_test function is redundant with test done at register time by
the crypto API, so remove it.
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 58 --
1 file changed, 58 deletions(-)
diff --git a/drivers/crypto/hifn_795x.c
The simple_strtoul function is marked as obsolete.
This patch replace it by kstrtouint at the cost of changing some function
return type from void to int.
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 28
1 file changed, 20 insertions(+), 8
This patch replace all printk by their dev_xx/pr_xx counterpart.
The patch remove also all custom dprintk by pr_debug/dev_debug
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 149 -
1 file changed, 67 insertions(+), 82 deletions(-)
The hifn_795x driver is old and have lots of style issue.
This patch try to solve easy ones.
Signed-off-by: LABBE Corentin
---
drivers/crypto/hifn_795x.c | 301 +
1 file changed, 138 insertions(+), 163 deletions(-)
diff --git
The oom_adj has been replaced by oom_score_adj in kernel,
but the /proc/pid/oom_adj is provided for legacy purposes.
When write/read a value into/from /proc/pid/oom_adj,
there is a transformation between oom_adj and oom_score_adj.
After writing a new value into /proc/pid/oom_adj, then read it.
Am 19.10.2015 um 13:31 schrieb Alexander Holler:
Am 19.10.2015 um 12:57 schrieb Alexander Holler:
Am 18.10.2015 um 12:11 schrieb Alexander Holler:
Am 18.10.2015 um 07:59 schrieb Greg Kroah-Hartman:
On Sun, Oct 18, 2015 at 07:20:34AM +0200, Alexander Holler wrote:
Am 18.10.2015 um 07:14
Similar to the file_inode() helper, provide a helper to lookup the inode for a
raw block device itself.
Cc: Al Viro
Signed-off-by: Dan Williams
---
fs/block_dev.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/fs/block_dev.c b/fs/block_dev.c
index
If an application wants exclusive access to all of the persistent memory
provided by an NVDIMM namespace it can use this raw-block-dax facility
to forgo establishing a filesystem. This capability is targeted
primarily to hypervisors wanting to provision persistent memory for
guests.
Cc: Jan Kara
801 - 900 of 1836 matches
Mail list logo
