From: Steve Twiss stwiss.opensou...@diasemi.com
This patch set adds OnKey driver support for the Dialog
Semiconductor DA9063 PMIC.
[PATCH V1 1/2]: kernel driver onkey support
[PATCH V1 2/2]: device tree bindings document
Thank you,
Steve Twiss, Dialog Semiconductor Ltd.
S Twiss (2):
input
From: Steve Twiss stwiss.opensou...@diasemi.com
Add device tree bindings for the DA9063 OnKey driver
This patch is dependent on PATCH V1 1/2
Signed-off-by: Steve Twiss stwiss.opensou...@diasemi.com
---
This patch applies against linux-next and v4.0-rc6
Documentation/devicetree/bindings
trying to set the local lock then I think we
probably don't want to return success. So...
Acked-by: Jeff Layton jeff.lay...@primarydata.com
--
Thanks,
Steve
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
to the page
* by clearing the hardware PTE. Currently Linux does not flush the TLB
- * for us in this case, which means the TLB will retain the transation
+ * for us in this case, which means the TLB will retain the transaction
Don't you mean translation rather than transaction?
Cheers,
--
Steve
0m0.005s
--
Thanks,
Steve
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
get more benefit from
notifications than a mount on a local file system would.
--
Thanks,
Steve
--
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 http://vger.kernel.org/majordomo-info.html
for this, and apologies for getting to this late...
I've had a good read through the patches in this series, and have some comments.
Cheers,
--
Steve
The is patch depends on:
[PATCH 1/2] Move the pt_regs_offset struct definition from arch to
common include file
[PATCH 2/2
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: David A. Long dave.l...@linaro.org
Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64.
Signed-off-by: David A. Long dave.l...@linaro.org
---
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/ptrace.h |
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: William Cohen wco...@redhat.com
The trampoline code is used by kretprobes to capture a return from a probed
function. This is done by saving the registers, calling the handler, and
restoring the registers. The code then
flags in PSTATE, which are not safe for
probing.
Thanks to Steve Capper and Pratyush Anand for several suggested
Changes.
Signed-off-by: Sandeepa Prabhu sandeepa.pra...@linaro.org
Signed-off-by: Steve Capper steve.cap...@linaro.org
Signed-off-by: David A. Long dave.l...@linaro.org
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: Sandeepa Prabhu sandeepa.pra...@linaro.org
Kprobes needs simulation of instructions that cannot be stepped
from different memory location, e.g.: those instructions
that uses PC-relative addressing. In simulation, the
Hi David,
Some comments below.
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: David A. Long dave.l...@linaro.org
Certain instructions are hard to execute correctly out-of-line (as in
kprobes). Test functions are added to insn.[hc] to identify these. The
instructions
unable to
thus far with 4.1-rc2 on a Xgene and Seattle systems.
Also, I tried the memhog + pages_to_scan suggestion from Andrea.
Maybe a silly question, where is your root filesystem located? Is
there anything network mounted?
Cheers,
--
Steve
--
To unsubscribe from this list: send the line
On 26 May 2015 at 15:35, Christoffer Dall christoffer.d...@linaro.org wrote:
Hi Steve,
On Tue, May 26, 2015 at 03:24:20PM +0100, Steve Capper wrote:
On Sun, May 24, 2015 at 09:34:04PM +0200, Christoffer Dall wrote:
Hi all,
I noticed a regression on my arm64 APM X-Gene system a couple
accesses to DAIF flags in PSTATE, which are not safe for
probing.
Thanks to Steve Capper and Pratyush Anand for several suggested
Changes.
Signed-off-by: Sandeepa Prabhu sandeepa.s.pra...@gmail.com
Signed-off-by: Steve Capper steve.cap...@linaro.org
Please remove my SoB, we can replace
Hi Suzuki,
Is is possible to tell the user that the kernel has failed to boot due
to the kernel granule being unsupported?
Cheers,
--
Steve
--
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 http
filesystems. You'll have to find someone willing to take it
into some overarching tree (Al's perhaps, or maybe Andrew's?), or break
it up into several per-fs patches and shepherd it into different
maintainers' trees.
Reviewed-by: Steve French smfre...@gmail.com
Do you want me to merge the fs
On 29 June 2015 at 19:36, David Long dave.l...@linaro.org wrote:
On 06/29/15 13:23, Steve Capper wrote:
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: David A. Long dave.l...@linaro.org
Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64.
Signed-off-by: David
On 29 June 2015 at 19:16, William Cohen wco...@redhat.com wrote:
On 06/29/2015 01:25 PM, Steve Capper wrote:
On 15 June 2015 at 20:07, David Long dave.l...@linaro.org wrote:
From: William Cohen wco...@redhat.com
The trampoline code is used by kretprobes to capture a return from a probed
On Wed, Jul 29, 2015 at 03:37:34PM +0200, Paolo Bonzini wrote:
Do not compute TMR in advance. Instead, set the TMR just before the interrupt
is accepted into the IRR. This limits the coupling between IOAPIC and LAPIC.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
; however, the IOAPIC does not have to
do anything special for these interrupts anyway.
This again limits the interactions between the IOAPIC and the LAPIC,
making it easier to move the former to userspace.
Inspired by a patch from Steve Rutherford.
Signed-off-by: Paolo Bonzini pbonz
On Wed, Jul 29, 2015 at 03:28:57PM +0200, Paolo Bonzini wrote:
The PIT is only created if irqchip_in_kernel returns true, so the
check is superfluous.
I poked around. Looks to me like the existence of an IOAPIC is not
checked on the creation of the in-kernel PIT. Userspace might limit itself to
On Wed, Jul 29, 2015 at 03:28:58PM +0200, Paolo Bonzini wrote:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 2d62229aac26..23e47a0b054b 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -3626,30 +3626,25 @@ long kvm_arch_vm_ioctl(struct file *filp,
and I'd prefer to keep it minimal.
This is a good point. I did briefly thing about this at one point.
Perhaps Steve can answer this. It would be trivial to move it back to
uapi if needed. Would you be ok with it in include/linux/audit.h for
now?
I have no problem with it in include
On Thu, Jul 30, 2015 at 11:26:28PM +, Zhang, Yang Z wrote:
Paolo Bonzini wrote on 2015-07-29:
Do not compute TMR in advance. Instead, set the TMR just before the
interrupt is accepted into the IRR. This limits the coupling between
IOAPIC and LAPIC.
Uh.., it back to original way
to see if someone gets a shell from it. There are a
lot of cases where it could be useful.
-Steve
--
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 http://vger.kernel.org/majordomo-info.html
Please
updates the kprobe example code s.t. _do_fork is targeted
instead, and the examples work as expected.
Signed-off-by: Steve Capper steve.cap...@linaro.org
---
samples/kprobes/jprobe_example.c| 8
samples/kprobes/kprobe_example.c| 2 +-
samples/kprobes/kretprobe_example.c | 2 +-
3
argument via C rather than pt_regs magic
Now everything appears to go through _do_fork rather than do_fork.
I'll send a fixup shortly, but if anyone else is running these modules
and worrying about a lack of events... worry less :-).
Cheers,
--
Steve
--
To unsubscribe from this list: send the line
short
[unsigned] [assigned] [usertype] len
drivers/staging/rtl8723au/core/rtw_recv.c:1557:21:got restricted __be16
[usertype] noident
Signed-off-by: Steve Pennington sgp...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_recv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
-by: Steve Capper steve.cap...@linaro.org
---
Hello,
This RFC is meant to sit on top of Suzuki's set at:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/358990.html
On systems with different core types (for instance big.LITTLE systems),
we need to be *very* careful that the REVIDR
] [usertype] len
drivers/staging/rtl8723au/core/rtw_recv.c:1557:21:got restricted __be16
[usertype] noident
Signed-off-by: Steve Pennington sgp...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_recv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging
-Original Message-
From: Nicholas Krause [mailto:xerofo...@gmail.com]
Sent: Wednesday, July 15, 2015 9:38 PM
To: sw...@chelsio.com
Cc: dledf...@redhat.com; sean.he...@intel.com; hal.rosenst...@gmail.com;
linux-r...@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: [PATCH]
Is this change really worth the effort?
-Original Message-
From: Nicholas Krause [mailto:xerofo...@gmail.com]
Sent: Thursday, July 16, 2015 1:34 PM
To: sw...@chelsio.com
Cc: dledf...@redhat.com; sean.he...@intel.com; hal.rosenst...@gmail.com;
linux-r...@vger.kernel.org;
From: Steve Twiss stwiss.opensou...@diasemi.com
Fix a missing DVC_RDY interrupt mask in struct regmap_irq definition.
The original submission of this driver did not contain all interrupt
masking definitions in the struct regmap_irq contained in the file
da9063-irq.c
The solution is to add
will be noted.
Thanks for doing this. Its a much needed feature.
In looking over it...does this add an AUDIT_VERSION_ define and use it in the
feature mask so that I can tell what kernels support this? I might have missed
it, but I can't find one.
Thanks,
-Steve
Here's a sample run:
Test for addition
ion. If we go the
> printk route and people really don't want to see anything in their
> logs, I suppose we could always add a sysctl knob to turn off the
> message completely (we would still need to do whatever audit records
> are required, see below).
>
> Wearing my audit ha
or the cifs.ko client which
currently rely on a cifs specific xattr).
In cifs.ko I still need to enable the SMB3 ACL helper functions
(currently only enabled for the older cifs dialect) since that will
make it easier, and figure out a way to allow helper tools to view
"claims based ACLs"
to transition
to the IDLE state MUST fail with an Immediate Error. If none of the
prior conditions are true, a Modify QP to the Idle state MUST take
the QP to the Idle state. No other state transitions out of Error
are supported. Any attempt to transition the QP to a state other
than
\n", ret);
return;
}
ret = ib_post_send(qp, , _swr);
if (ret) {
WARN_ONCE(ret, "failed to drain send queue: %d\n", ret);
return;
}
wait_for_completion();
wait_for_completion();
}
Thoughts?
This won't work for iWARP as per my previous
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org
> [mailto:linux-rdma-ow...@vger.kernel.org] On Behalf Of Sagi Grimberg
> Sent: Monday, November 16, 2015 12:38 PM
> To: Steve Wise; 'Christoph Hellwig'; linux-r...@vger.kernel.org
> Cc: bart.vanass.
> -Original Message-
> From: Steve Wise [mailto:sw...@opengridcomputing.com]
> Sent: Monday, November 16, 2015 10:38 AM
> To: Sagi Grimberg; Christoph Hellwig; linux-r...@vger.kernel.org
> Cc: bart.vanass...@sandisk.com; ax...@fb.com; linux-s...@vger.kernel.org;
On 11/02/2015 06:02 AM, Peter Zijlstra wrote:
> On Wed, Oct 28, 2015 at 08:30:42AM +0530, Viresh Kumar wrote:
>> These are the last memories I have around upstreaming this governor:
>> http://marc.info/?l=linux-kernel=132867057910479=2
>>
>> Has anything changed after that? Or we decided to go
int
>>> default "14" if (ARM64_64K_PAGES && TRANSPARENT_HUGEPAGE)
>>> + default "12" if (ARM64_16K_PAGES && TRANSPARENT_HUGEPAGE)
>>> default "11"
>>
>>
>> I'm a little lost h
On 08/25/2015 03:45 AM, Juri Lelli wrote:
> But, it is true that if the above events happened the other way around
> (we trigger an update after load balancing and a new task arrives), we
> may miss the opportunity to jump to max with the new task. In my mind
> this is probably not a big deal, as
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Provide an additional case entry for DA9053_BC in the find_regulator_info()
function in order to support BB type silicon for the DA9053 device.
Signed-off-by: Steve Twiss <stwiss.opensou...@diasemi.com>
---
This patch applies agains
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Definitions for GPIO registers 8, 9, 10, 11, 12 and 13 are added into
the register header file.
- DA9052_GPIO_8_9_REG25
- DA9052_GPIO_10_11_REG 26
- DA9052_GPIO_12_13_REG 27
A modification is also made to the MFD core code to
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Two patches to add missing registers and add support for DA9053-BB
silicon in the regulators component. These patches modify existing
files for the Dialog Power Management IC driver for the DA9052/53
devices.
In this patch set the fol
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Provide an additional case entry for DA9053_BC in the find_regulator_info()
function in order to support BC type silicon for the DA9053 device.
Signed-off-by: Steve Twiss <stwiss.opensou...@diasemi.com>
---
Changes since PATCH V2
elow.
I would recommend running the next version of this series through
the libhugetlbfs test suite, as that may pick up a few things too.
Cheers,
--
Steve
>
> Signed-off-by: David Woods <dwo...@ezchip.com>
> Reviewed-by: Chris Metcalf <cmetc...@ezchip.com>
> ---
> arch/arm6
Hi Juri,
On 07/07/2015 11:24 AM, Morten Rasmussen wrote:
> From: Juri Lelli
>
> When a CPU is going idle it is pointless to ask for an OPP update as we
> would wake up another task only to ask for the same capacity we are already
> running at (utilization gets moved to
On 10/09/2015 02:14 AM, Juri Lelli wrote:
>> Though I understand the initial stated motivation here (avoiding a
>> > redundant capacity request upon idle entry), releasing the CPU's
>> > capacity request altogether on idle seems like it could be a contentious
>> > policy decision.
>> >
>> > An
ing SIDs to
UIDs (CIFS ACLs already have the same issue of SID to UID mapping
which we handle with upcalls) and Samba has various pluggable ways to
handle UID mapping and is easily extensible. Similarly NFSv4 ACLs,
although closely related to CIFS/NTFS ACLs have to be map usernames to
uids.
Hello,
If a daemon using FANOTIFY needs to open a file on a watched filesystem and
its wanting OPEN_PERM events, we get deadlock. (This could happen because
of a library the daemon is using suddenly decides it needs to look in a new
file.) Even though the man page says that the daemon should
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Provide an additional case entry for DA9053_BC in the find_regulator_info()
function in order to support BB type silicon for the DA9053 device.
Signed-off-by: Steve Twiss <stwiss.opensou...@diasemi.com>
---
Changes since PATCH V1
own non-POSIX ACLs, such as HFS,
> NTFS, ZFS would presumably also need to map the in-kernel Richacl format to
> their on-disk format.
Will be interesting to see whether in the long run can have some
common code in NTFS, CIFS/SMB3 (and even NFSv4.x) ACL parsing since
their formats are qu
On 08/17/2015 05:19 AM, Juri Lelli wrote:
>> Nah, just maybe: (capacity << SCHED_CAPACITY_SHIFT) / capacity_orig_of()
>> > such that you don't have to export that knowledge to this thing.
>> >
> Oh, right. I guess we can just go with something like:
>
> req_cap = get_cpu_usage(cpu) *
On 6 October 2015 at 10:09, Russell King - ARM Linux
wrote:
> On Mon, Oct 05, 2015 at 06:02:10PM +0100, Suzuki K. Poulose wrote:
>> +static int __init cpuinfo_regs_init(void)
>> +{
>> + int cpu, ret;
>> +
>> + for_each_present_cpu(cpu) {
>> + struct
On 6 October 2015 at 11:25, Mark Rutland <mark.rutl...@arm.com> wrote:
> On Tue, Oct 06, 2015 at 11:18:42AM +0100, Steve Capper wrote:
>> On 6 October 2015 at 10:09, Russell King - ARM Linux
>> <li...@arm.linux.org.uk> wrote:
>> > On Mon, Oct 05, 2015 at 06:02
On 07/09/2015 10:16 AM, Jan Kara wrote:
On Tue 07-07-15 13:06:05, Steven J. Magnani wrote:
For a UDF filesystem configured with an Unallocated Space Table,
a filesystem operation that triggers an update to the table results
in on-disk corruption that prevents remounting:
udf_read_tagged:
take it with Steve to come up with a complete solution for
this bit.
Thoughts?
Yes, let's drop it for now.
Fine with me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
-Original Message-
From: Nicholas Krause [mailto:xerofo...@gmail.com]
Sent: Wednesday, August 26, 2015 7:22 PM
To: sw...@chelsio.com
Cc: dledf...@redhat.com; sean.he...@intel.com; hal.rosenst...@gmail.com;
linux-r...@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: [PATCH]
Acked-by: Steve Wise sw...@opengridcomputing.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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Aug 13, 2015 at 09:31:48AM +0200, Paolo Bonzini wrote:
Pinging this thread.
Should I put together a patch to make split irqchip work properly with the old
TMR behavior?
>
>
> On 13/08/2015 08:35, Zhang, Yang Z wrote:
> >> You may be right. It is safe if no future hardware plans to use
destroy_cq(>rhp->rdev, >cq,
> + ucontext ? >uctx : >cq.rdev->uctx);
> kfree(chp);
> - return 0;
> + return ret;
> }
The SW CQ is destroyed regardless of any errors returned by destroy_cq(). So
c4iw_destroy_cq() shouldn't return
ll
always be or if they can be combined.
> + * capacity_orig is the cpu_capacity available at * the highest frequency
spurious *
thanks,
Steve
--
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
6KB granule we *can* have a contiguous bit being used by level
2 descriptors (i.e. PMDs), so the pmd_contig logic could perhaps be
used in combination with Suzuki's 16KB PAGE_SIZE series at:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/370117.html
I will read through the rest of th
iding possibly a simpler interface?
Sure. I'm just communicating requirements I've seen :) .
> I agree with you that all the current scenarios must be supported by
> the new proposal. We should probably start by listing them and come
> out with a set of test cases that allow to verify where we are wrt
> the state of the art.
Sounds like a good plan to me... Perhaps we could discuss some mobile
usecases next week at Linaro Connect?
cheers,
Steve
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
't that hopefully reduce the likelihood that someone feels the
need to roll their own stack of kernel modifications which never make it
upstream?
cheers,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordo
f wimpy compiler optimizer will not move
the constant initializer out of the loop? I bet if you compare binary
sizes/code it will be exactly the same, and you added some characters
of code. Reorganizing code for readability is fine, but for compiler
(in)efficiency seems like a bad idea.
Regards, Stev
Hi David,
Some initial comments below.
Cheers,
--
Steve
On Tue, Sep 15, 2015 at 02:01:57PM -0400, David Woods wrote:
> The arm64 MMU supports a Contiguous bit which is a hint that the TTE
> is one of a set of contiguous entries which can be cached in a single
> TLB entry. Supporting
from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thanks,
Steve
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Jeremy,
One quick comment for now below.
I ran into a problem testing this on my Seattle board, and needed the fix below.
Cheers,
--
Steve
On 16 September 2015 at 20:03, Jeremy Linton <jeremy.lin...@arm.com> wrote:
> With 64k pages, the next larger segment size is 512M. The linux
Corrected endian error and repushed
https://git.samba.org/?p=sfrench/cifs-2.6.git;a=patch;h=79a5296f14b26ac8644239286ffd7a62dbbc385e
On Thu, Sep 17, 2015 at 6:41 PM, Steve French <smfre...@gmail.com> wrote:
> Nice catch.
>
> Merged into cifs-2.6.git for-next
--
n
> energy-efficient way, how much we want to reduce power or boost
> performances.
The provided links definitely establish the need for (1) but I am still
wondering about the motivation for (2), because I don't think it's going
to be possible to boil everything down to a single slider tunable
without losing flexibility/functionality.
cheers,
Steve
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
/grsecurity team
Signed-off-by: Steve French <steve.fre...@primarydata.com>
Reported-by: PaX Team <pagee...@freemail.hu>
CC: Emese Revfy <re.em...@gmail.com>
CC: Brad Spengler <spen...@grsecurity.net>
CC: Stable <sta...@vger.kernel.org>
---
fs/cifs/inode.c | 34
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Fix misleading and inconsistent copyright header wording.
Alter the copyright header text and MODULE_LICENSE macro to ensure the
GPL v2 licence description is correctly represented.
It will remove the incorrectly LGPL worded text.
On 08/14/2015 06:02 AM, Morten Rasmussen wrote:
> To be sure not to break smp_nice, we have defined over-utilization as
> when:
>
> cpu_rq(any)::cfs::avg::util_avg + margin > cpu_rq(any)::capacity
>
> is true for any cpu in the system. IOW, as soon as one cpu is (nearly)
> 100% utilized, we
On 09/20/2015 03:03 PM, Leo Yan wrote:
> In this case of CPU is running at fmax, it's true that
> task_fits_capacity() will return true. But here i think
> cpu_overutilized() also will return true, so that means scheduler will
> go back to use CFS's old way for loading balance. Finally tasks also
Hi Punit,
On 09/28/2015 09:48 AM, Punit Agrawal wrote:
> Hi Mike,
>
> I ran into an issue when using this patch. Posting it here as this is
> the latest posting I can find.
>
> Morten Rasmussen writes:
>
>> From: Michael Turquette
>>
...
>>
y derail the
efforts of the EAS algorithm, which I'm still working on digesting.
Perhaps a unified sched/cpufreq policy could go there.
thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More maj
, energy_aware_wake_cpu() would not
consider condensing them on a single cluster. Leo was this the issue you
were seeing?
However I think there may be negative side effects with the proposed
policy above as well - won't this cause us to pack the first cluster
until it's 100% full (running at fm
ally use name=value for everything important. Reset by itself
will get dropped by auparse. action=reset (or something similar) would
be better.
-Steve
> + audit_log_lost(s);
> audit_pid = 0;
>
On 21 September 2015 at 09:44, David Woods <dwo...@ezchip.com> wrote:
>
> Steve,
Hi Dave,
>
> Thanks for your review and comments. I take your points about the 16k
> granule - it's helpful to know that support is in the works. However, I'm
> not sure I agree with your
From: Steve Twiss <stwiss.opensou...@diasemi.com>
This fix alters the ordering of the IRQ and device registrations in the RTC
driver probe function. This change will apply to the RTC driver that supports
both DA9063 and DA9062 PMICs.
A problem could occur with the existing RTC
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Stop reporting KEY_SLEEP for a short key-press and report KEY_POWER instead
This change applied to both DA9063 and DA9062 ONKEY drivers.
Signed-off-by: Steve Twiss <stwiss.opensou...@diasemi.com>
---
This patch applies agains
t load balancing related calls to reduce the
number of triggers.
[smuc...@linaro.org: resolve merge conflicts, define task_new,
use renamed static key sched_freq]
cc: Ingo Molnar <mi...@redhat.com>
cc: Peter Zijlstra <pet...@infradead.org>
Signed-off-by: Juri Lelli <juri.le...@arm.com&
org>
Signed-off-by: Michael Turquette <mturque...@baylibre.com>
Signed-off-by: Steve Muckle <smuc...@linaro.org>
---
drivers/cpufreq/cpufreq.c | 6 ++
include/linux/cpufreq.h | 9 +
2 files changed, 15 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/c
tasks from rt_avg metric and directly use
the average bandwidth of deadline scheduler in scale_rt_capacity.
Based in part on a similar patch from Luca Abeni <luca.ab...@unitn.it>.
Signed-off-by: Vincent Guittot <vincent.guit...@linaro.org>
Signed-off-by: Steve Muckle <smuc...@linaro.o
fork()
sched/fair: cpufreq_sched triggers for load balancing
Michael Turquette (2):
cpufreq: introduce cpufreq_driver_is_slow
sched: scheduler-driven cpu frequency selection
Morten Rasmussen (1):
sched: Compute cpu capacity available at current frequency
Steve Muckle (1):
sched/fair:
/article.gmane.org/gmane.linux.kernel/1499836
[smuc...@linaro.org: various additions and fixes, revised commit text]
CC: Ricky Liang <jcli...@chromium.org>
Signed-off-by: Michael Turquette <mturque...@baylibre.com>
Signed-off-by: Juri Lelli <juri.le...@arm.com>
Signed-off-by: Steve Muck
: Ingo Molnar <mi...@redhat.com>
cc: Peter Zijlstra <pet...@infradead.org>
Signed-off-by: Morten Rasmussen <morten.rasmus...@arm.com>
Signed-off-by: Steve Muckle <smuc...@linaro.org>
---
kernel/sched/fair.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/kern
ake up path of RT tasks.
Signed-off-by: Vincent Guittot <vincent.guit...@linaro.org>
Signed-off-by: Steve Muckle <smuc...@linaro.org>
---
kernel/sched/rt.c | 49 -
1 file changed, 48 insertions(+), 1 deletion(-)
diff --git a/kernel/sched/r
ancing. This requirement is already
fulfilled by __update_cpu_load so the call in sched_rt_avg_update,
which is part of the hotpath, is useless.
Signed-off-by: Vincent Guittot <vincent.guit...@linaro.org>
Signed-off-by: Steve Muckle <smuc...@linaro.org>
---
kernel/sched/sched.h | 1 -
1 file c
es an additional flag in sched.h that is only set at
fork() time and it is then consumed in enqueue_task_fair() for our purpose.
cc: Ingo Molnar <mi...@redhat.com>
cc: Peter Zijlstra <pet...@infradead.org>
Signed-off-by: Juri Lelli <juri.le...@arm.com>
Signed-off-by: Steve Muckl
. This is also done to try to harm the performance of
a task the least.
Original fair-class only version authored by Juri Lelli
<juri.le...@arm.com>.
cc: Ingo Molnar <mi...@redhat.com>
cc: Peter Zijlstra <pet...@infradead.org>
Signed-off-by: Juri Lelli <juri.le...@arm.com>
Sig
t;
cc: Peter Zijlstra <pet...@infradead.org>
Signed-off-by: Juri Lelli <juri.le...@arm.com>
Signed-off-by: Steve Muckle <smuc...@linaro.org>
---
kernel/sched/fair.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/ker
their predicate and
> are not (technically) executed are also not treated as a hit kprobe. Steve
> Capper has suggested that the probe handling should still take place because
> we stepped through the instruction even if it was effectively a nop. This
> would be a significant chang
From: Steve Twiss <stwiss.opensou...@diasemi.com>
Stop reporting KEY_SLEEP for a short key-press and report KEY_POWER instead
This change applies to both DA9063 and DA9062 ONKEY drivers.
A previous application used for testing by the developer required a KEY_SLEEP
and KEY_POWER input_repo
On 12/14/2015 06:24 PM, Yuyang Du wrote:
>>> On Fri, Dec 11, 2015 at 06:01:45PM -0800, Steve Muckle wrote:
>>>> In init_entity_runnable_average() the last_update_time is initialized to
>>>> zero. The task is given max load and utilization as a
ested_freq.
I agree, it's incorrect. As I replied earlier I believe setting the task
state back to TASK_RUNNING at the top of the else block is the easiest fix.
thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vg
801 - 900 of 5727 matches
Mail list logo