On Fri, 5 Oct 2018, Mel Gorman wrote:
> > This causes, on average, a 13.9% access latency regression on Haswell, and
> > the regression would likely be more severe on Naples and Rome.
> >
>
> That assumes that fragmentation prevents easy allocation which may very
> well be the case. While it
On Fri, 5 Oct 2018, Mel Gorman wrote:
> > This causes, on average, a 13.9% access latency regression on Haswell, and
> > the regression would likely be more severe on Naples and Rome.
> >
>
> That assumes that fragmentation prevents easy allocation which may very
> well be the case. While it
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
These are the last 3 patches from the "macrofying inline asm" series
after rebasing on TIP, per Ingo's request.
For the record: the new commit log was written by Ingo.
Link:
https://lore.kernel.org/lkml/20181003213100.189959-11-na...@vmware.com/T/#m28ed17da046354dd8d897ff9703561ac3fd71410
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
These are the last 3 patches from the "macrofying inline asm" series
after rebasing on TIP, per Ingo's request.
For the record: the new commit log was written by Ingo.
Link:
https://lore.kernel.org/lkml/20181003213100.189959-11-na...@vmware.com/T/#m28ed17da046354dd8d897ff9703561ac3fd71410
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
As described in:
77b0bf55bc67: ("kbuild/Makefile: Prepare for using macros in inline assembly
code to work around asm() related GCC inlining bugs")
GCC's inlining heuristics are broken with common asm() patterns used in
kernel code, resulting in the effective disabling of inlining.
The
Hi Philipp,
I apologize, but I just realized that I forgot to test this patch
against the SoCFPGA ARM64 platform. I just tested against that platform
and this patch is preventing that board from booting.
I need to redo this patch.
If its not too late, can you remove this patch from reset/next?
Hi Philipp,
I apologize, but I just realized that I forgot to test this patch
against the SoCFPGA ARM64 platform. I just tested against that platform
and this patch is preventing that board from booting.
I need to redo this patch.
If its not too late, can you remove this patch from reset/next?
On Fri, 5 Oct 2018 01:22:26 +0800, Guo Ren wrote:
> Dt-bingdings doc for C-SKY SMP system setting.
>
> Changelog:
> - Drop the interrupt-parent.
>
> Signed-off-by: Guo Ren
> ---
> .../devicetree/bindings/timer/csky,mptimer.txt | 42
> ++
> 1 file changed, 42
On Fri, 5 Oct 2018 01:22:26 +0800, Guo Ren wrote:
> Dt-bingdings doc for C-SKY SMP system setting.
>
> Changelog:
> - Drop the interrupt-parent.
>
> Signed-off-by: Guo Ren
> ---
> .../devicetree/bindings/timer/csky,mptimer.txt | 42
> ++
> 1 file changed, 42
On Fri, 5 Oct 2018 01:22:22 +0800, Guo Ren wrote:
> Dt-bindings doc about C-SKY Multi-processors interrupt controller.
>
> Changelog:
> - Should be: '#interrupt-cells' not 'interrupt-cells'
>
> Signed-off-by: Guo Ren
> ---
> .../bindings/interrupt-controller/csky,mpintc.txt | 40
>
On Fri, 5 Oct 2018 01:22:22 +0800, Guo Ren wrote:
> Dt-bindings doc about C-SKY Multi-processors interrupt controller.
>
> Changelog:
> - Should be: '#interrupt-cells' not 'interrupt-cells'
>
> Signed-off-by: Guo Ren
> ---
> .../bindings/interrupt-controller/csky,mpintc.txt | 40
>
On Fri, Oct 05, 2018 at 01:22:28AM +0800, Guo Ren wrote:
> Dt-bindings doc for gx6605s SOC's system timer.
>
> Signed-off-by: Guo Ren
> ---
> .../bindings/timer/csky,gx6605s-timer.txt | 42
> ++
> 1 file changed, 42 insertions(+)
> create mode 100644
>
On Fri, Oct 05, 2018 at 01:22:28AM +0800, Guo Ren wrote:
> Dt-bindings doc for gx6605s SOC's system timer.
>
> Signed-off-by: Guo Ren
> ---
> .../bindings/timer/csky,gx6605s-timer.txt | 42
> ++
> 1 file changed, 42 insertions(+)
> create mode 100644
>
On Thu, Oct 4, 2018 at 8:54 AM Mark Brown wrote:
>
> On Thu, Oct 04, 2018 at 01:32:13PM +0200, Linus Walleij wrote:
> > On Thu, Oct 4, 2018 at 12:50 PM Mark Brown wrote:
> > > On Thu, Oct 04, 2018 at 11:06:54AM +0200, Linus Walleij wrote:
>
> > > > Optional properties:
> > > > -- gpio: gpio to
On Thu, Oct 4, 2018 at 8:54 AM Mark Brown wrote:
>
> On Thu, Oct 04, 2018 at 01:32:13PM +0200, Linus Walleij wrote:
> > On Thu, Oct 4, 2018 at 12:50 PM Mark Brown wrote:
> > > On Thu, Oct 04, 2018 at 11:06:54AM +0200, Linus Walleij wrote:
>
> > > > Optional properties:
> > > > -- gpio: gpio to
On Fri, 5 Oct 2018 12:27:27 -0700 "Joel Fernandes (Google)"
wrote:
> To support the usecase, this patch adds a new F_SEAL_FS_WRITE seal which
> prevents any future mmap and write syscalls from succeeding while
> keeping the existing mmap active. The following program shows the seal
> working
On Fri, 5 Oct 2018 12:27:27 -0700 "Joel Fernandes (Google)"
wrote:
> To support the usecase, this patch adds a new F_SEAL_FS_WRITE seal which
> prevents any future mmap and write syscalls from succeeding while
> keeping the existing mmap active. The following program shows the seal
> working
On 10/5/18 8:17 AM, Jason Gunthorpe wrote:
> On Thu, Oct 04, 2018 at 09:02:24PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
>>
>> Introduces put_user_page(), which simply calls put_page().
>> This provides a way to update all get_user_pages*() callers,
>> so that they call
On 10/5/18 8:17 AM, Jason Gunthorpe wrote:
> On Thu, Oct 04, 2018 at 09:02:24PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
>>
>> Introduces put_user_page(), which simply calls put_page().
>> This provides a way to update all get_user_pages*() callers,
>> so that they call
On Fri, 5 Oct 2018 15:45:26 +1000 Dave Chinner wrote:
> From: Dave Chinner
>
> We've recently seen a workload on XFS filesystems with a repeatable
> deadlock between background writeback and a multi-process
> application doing concurrent writes and fsyncs to a small range of a
> file.
>
>
Em Fri, Oct 05, 2018 at 09:27:16AM -0700, Colin McCabe escreveu:
> Hmm. Did you consider setting the ifdefs you can set to always get the POSIX
> version of strerror_r?
Yes, didn't work for tools/perf, that uses _GNU_SOURCE, so we would have
the headers with that and the .c with an explicit
On Fri, 5 Oct 2018 15:45:26 +1000 Dave Chinner wrote:
> From: Dave Chinner
>
> We've recently seen a workload on XFS filesystems with a repeatable
> deadlock between background writeback and a multi-process
> application doing concurrent writes and fsyncs to a small range of a
> file.
>
>
Em Fri, Oct 05, 2018 at 09:27:16AM -0700, Colin McCabe escreveu:
> Hmm. Did you consider setting the ifdefs you can set to always get the POSIX
> version of strerror_r?
Yes, didn't work for tools/perf, that uses _GNU_SOURCE, so we would have
the headers with that and the .c with an explicit
On Mon, Oct 01, 2018 at 04:20:09PM +0200, Vitaly Kuznetsov wrote:
> MMU reconfiguration in init_kvm_tdp_mmu()/kvm_init_shadow_mmu() can be
> avoided if the source data used to configure it didn't change; enhance
> MMU extended role with the required fields and consolidate common code in
>
On Mon, Oct 01, 2018 at 04:20:09PM +0200, Vitaly Kuznetsov wrote:
> MMU reconfiguration in init_kvm_tdp_mmu()/kvm_init_shadow_mmu() can be
> avoided if the source data used to configure it didn't change; enhance
> MMU extended role with the required fields and consolidate common code in
>
On Mon, Oct 01, 2018 at 04:20:08PM +0200, Vitaly Kuznetsov wrote:
> MMU re-initialization is expensive, in particular,
> update_permission_bitmask() and update_pkru_bitmask() are.
>
> Cache the data used to setup shadow EPT MMU and avoid full re-init when
> it is unchanged.
>
> Signed-off-by:
On Mon, Oct 01, 2018 at 04:20:08PM +0200, Vitaly Kuznetsov wrote:
> MMU re-initialization is expensive, in particular,
> update_permission_bitmask() and update_pkru_bitmask() are.
>
> Cache the data used to setup shadow EPT MMU and avoid full re-init when
> it is unchanged.
>
> Signed-off-by:
On Fri, 5 Oct 2018 20:12:43 +0200
Ricardo Ribalda Delgado wrote:
>
> I think I know what might be the issue. on cfi_cmdset_002.c
> cfi_amdstd_reset can be called in parrallel to cfi_amdstd_destroy.
>
> maybe we should call
> unregister_reboot_notifier(>reboot_notifier);
> before
>
On Fri, 5 Oct 2018 20:12:43 +0200
Ricardo Ribalda Delgado wrote:
>
> I think I know what might be the issue. on cfi_cmdset_002.c
> cfi_amdstd_reset can be called in parrallel to cfi_amdstd_destroy.
>
> maybe we should call
> unregister_reboot_notifier(>reboot_notifier);
> before
>
Hi arm-soc maintainers,
Please merge the following updates for next.
v2: updated tree to include dependency patches by merging soc-fsl-fix-v4.19-2
Regards,
Leo
The following changes since commit 56740a7167cbbbda99ebfd3e8b4e4d51ae39bd06:
Merge tag 'soc-fsl-fix-v4.19-2' into HEAD (2018-10-05
Hi arm-soc maintainers,
Please merge the following updates for next.
v2: updated tree to include dependency patches by merging soc-fsl-fix-v4.19-2
Regards,
Leo
The following changes since commit 56740a7167cbbbda99ebfd3e8b4e4d51ae39bd06:
Merge tag 'soc-fsl-fix-v4.19-2' into HEAD (2018-10-05
Clang warns when one enumerated type is implicitly converted to another.
drivers/spi/spi-ep93xx.c:342:62: warning: implicit conversion from
enumeration type 'enum dma_transfer_direction' to different enumeration
type 'enum dma_data_direction' [-Wenum-conversion]
nents =
Clang warns when one enumerated type is implicitly converted to another.
drivers/spi/spi-ep93xx.c:342:62: warning: implicit conversion from
enumeration type 'enum dma_transfer_direction' to different enumeration
type 'enum dma_data_direction' [-Wenum-conversion]
nents =
Android uses ashmem for sharing memory regions. We are looking forward
to migrating all usecases of ashmem to memfd so that we can possibly
remove the ashmem driver in the future from staging while also
benefiting from using memfd and contributing to it. Note staging drivers
are also not ABI and
Android uses ashmem for sharing memory regions. We are looking forward
to migrating all usecases of ashmem to memfd so that we can possibly
remove the ashmem driver in the future from staging while also
benefiting from using memfd and contributing to it. Note staging drivers
are also not ABI and
On Mon, Oct 01, 2018 at 04:20:05PM +0200, Vitaly Kuznetsov wrote:
> When EPT is used for nested guest we need to re-init MMU as shadow
> EPT MMU (nested_ept_init_mmu_context() does that). When we return back
> from L2 to L1 kvm_mmu_reset_context() in nested_vmx_load_cr3() resets
> MMU back to
On Mon, Oct 01, 2018 at 04:20:05PM +0200, Vitaly Kuznetsov wrote:
> When EPT is used for nested guest we need to re-init MMU as shadow
> EPT MMU (nested_ept_init_mmu_context() does that). When we return back
> from L2 to L1 kvm_mmu_reset_context() in nested_vmx_load_cr3() resets
> MMU back to
On Thu 04 Oct 23:59 PDT 2018, Arun Kumar Neelakantam wrote:
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
[..]
> +/**
> + * rpmsg_get_signals() - get the signals for this endpoint
> + * @ept: the rpmsg endpoint
> + *
> + * Returns 0 on success and an appropriate error
On Thu 04 Oct 23:59 PDT 2018, Arun Kumar Neelakantam wrote:
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
[..]
> +/**
> + * rpmsg_get_signals() - get the signals for this endpoint
> + * @ept: the rpmsg endpoint
> + *
> + * Returns 0 on success and an appropriate error
Hi Vinod,
Thanks for looking at this closely.
On Fri, Oct 5, 2018 at 11:57 PM Vinod wrote:
>
> On 13-09-18, 09:51, Masahiro Yamada wrote:
>
> > +#define UNIPHIER_MDMAC_CH_IRQ_STAT 0x010 // current hw status (RO)
> > +#define UNIPHIER_MDMAC_CH_IRQ_REQ0x014 // latched STAT (WOC)
> >
Hi Vinod,
Thanks for looking at this closely.
On Fri, Oct 5, 2018 at 11:57 PM Vinod wrote:
>
> On 13-09-18, 09:51, Masahiro Yamada wrote:
>
> > +#define UNIPHIER_MDMAC_CH_IRQ_STAT 0x010 // current hw status (RO)
> > +#define UNIPHIER_MDMAC_CH_IRQ_REQ0x014 // latched STAT (WOC)
> >
On 05:01-20180927, Vignesh R wrote:
> cbass_wakeup interconnect which is the parent of wakeup_uart node
> defines address-cells=1 and size-cells=1, therefore fix up reg property
> of wakeup_uart node accordingly. Otherwise, this UART instance fails to
> probe if enabled.
>
> Fixes: 4201af2544b3
On 05:01-20180927, Vignesh R wrote:
> cbass_wakeup interconnect which is the parent of wakeup_uart node
> defines address-cells=1 and size-cells=1, therefore fix up reg property
> of wakeup_uart node accordingly. Otherwise, this UART instance fails to
> probe if enabled.
>
> Fixes: 4201af2544b3
Commit-ID: 99c19e6a8fe4a95fa0dac191207a1d40461b1604
Gitweb: https://git.kernel.org/tip/99c19e6a8fe4a95fa0dac191207a1d40461b1604
Author: Andy Lutomirski
AuthorDate: Fri, 5 Oct 2018 11:02:43 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 5 Oct 2018 21:03:23 +0200
x86/vdso: Rearrange
Commit-ID: 99c19e6a8fe4a95fa0dac191207a1d40461b1604
Gitweb: https://git.kernel.org/tip/99c19e6a8fe4a95fa0dac191207a1d40461b1604
Author: Andy Lutomirski
AuthorDate: Fri, 5 Oct 2018 11:02:43 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 5 Oct 2018 21:03:23 +0200
x86/vdso: Rearrange
I have not reviewed them yet. I am waiting for Masayoshi to send a new
series with correct order as Ingo requested.
Pavel
On 10/2/18 10:01 AM, Michal Hocko wrote:
> On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
>> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>>
>>> This patch series are the
I have not reviewed them yet. I am waiting for Masayoshi to send a new
series with correct order as Ingo requested.
Pavel
On 10/2/18 10:01 AM, Michal Hocko wrote:
> On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
>> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>>
>>> This patch series are the
RK3899 has one cluster with 4 small cores, and another one with 2 big
cores, with cores in different clusters having different OPPs and thus
needing separate set of tunables. Let's enable this via
"have_governor_per_policy" platform data.
Signed-off-by: Dmitry Torokhov
---
v2 changes: commit
RK3899 has one cluster with 4 small cores, and another one with 2 big
cores, with cores in different clusters having different OPPs and thus
needing separate set of tunables. Let's enable this via
"have_governor_per_policy" platform data.
Signed-off-by: Dmitry Torokhov
---
v2 changes: commit
On 10/2/18 10:01 AM, Michal Hocko wrote:
> On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
>> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>>
>>> This patch series are the fix for movable_node boot option
>>> issue which was introduced by commit 124049decbb1 ("x86/e820:
>>> put !E820_TYPE_RAM
On 10/2/18 10:01 AM, Michal Hocko wrote:
> On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
>> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>>
>>> This patch series are the fix for movable_node boot option
>>> issue which was introduced by commit 124049decbb1 ("x86/e820:
>>> put !E820_TYPE_RAM
On Thu, Oct 04, 2018 at 09:23:50PM +0200, Takashi Iwai wrote:
> On Thu, 04 Oct 2018 20:58:21 +0200,
> Michael Pobega wrote:
> >
> > The Elo VuPoint 15MX has two headphone jacks of which neither work by
> > default. Disabling automute allows ALSA to work normally with the
> > speakers & left
On Thu, Oct 04, 2018 at 09:23:50PM +0200, Takashi Iwai wrote:
> On Thu, 04 Oct 2018 20:58:21 +0200,
> Michael Pobega wrote:
> >
> > The Elo VuPoint 15MX has two headphone jacks of which neither work by
> > default. Disabling automute allows ALSA to work normally with the
> > speakers & left
On Fri, Oct 05, 2018 at 10:14:07AM +0200, Martin Kepplinger wrote:
> This is how userspace checks for touchscreen devices most reliably.
>
> Signed-off-by: Martin Kepplinger
Applied, thank you.
> ---
> drivers/input/touchscreen/st1232.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Fri, Oct 05, 2018 at 10:14:07AM +0200, Martin Kepplinger wrote:
> This is how userspace checks for touchscreen devices most reliably.
>
> Signed-off-by: Martin Kepplinger
Applied, thank you.
> ---
> drivers/input/touchscreen/st1232.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Fri, 5 Oct 2018, Tim Chen wrote:
> On 10/02/2018 10:58 AM, Thomas Gleixner wrote:
> > On Tue, 25 Sep 2018, Tim Chen wrote:
> >>
> >> +void arch_set_dumpable(struct task_struct *tsk, struct mm_struct *mm, int
> >> value)
> >> +{
> >> + if (!static_branch_unlikely(_v2_app_lite))
> >> +
On Fri, 5 Oct 2018, Tim Chen wrote:
> On 10/02/2018 10:58 AM, Thomas Gleixner wrote:
> > On Tue, 25 Sep 2018, Tim Chen wrote:
> >>
> >> +void arch_set_dumpable(struct task_struct *tsk, struct mm_struct *mm, int
> >> value)
> >> +{
> >> + if (!static_branch_unlikely(_v2_app_lite))
> >> +
Building an image with KVM_AMD=y, CRYPTO_DEV_SP_PSP=y, and
CRYPTO_DEV_CCP_DD=m fails with the following error messages.
arch/x86/kvm/svm.c:6287: undefined reference to `sev_issue_cmd_external_user'
arch/x86/kvm/svm.o: In function `sev_unbind_asid':
arch/x86/kvm/svm.c:1747: undefined reference to
Building an image with KVM_AMD=y, CRYPTO_DEV_SP_PSP=y, and
CRYPTO_DEV_CCP_DD=m fails with the following error messages.
arch/x86/kvm/svm.c:6287: undefined reference to `sev_issue_cmd_external_user'
arch/x86/kvm/svm.o: In function `sev_unbind_asid':
arch/x86/kvm/svm.c:1747: undefined reference to
On Fri 05 Oct 01:46 PDT 2018, Philipp Zabel wrote:
> Hi Sibi, Bjorn,
>
> On Thu, 2018-10-04 at 23:57 +0530, Sibi Sankar wrote:
> > On 09/04/2018 01:06 AM, Bjorn Andersson wrote:
> [...]
> > > Philipp, there's no compile time dependencies between the PDC and
> > > remoteproc patches in this
On Fri 05 Oct 01:46 PDT 2018, Philipp Zabel wrote:
> Hi Sibi, Bjorn,
>
> On Thu, 2018-10-04 at 23:57 +0530, Sibi Sankar wrote:
> > On 09/04/2018 01:06 AM, Bjorn Andersson wrote:
> [...]
> > > Philipp, there's no compile time dependencies between the PDC and
> > > remoteproc patches in this
This adds a "base attached" switch definition to the MKBP protocol that
is used by Whiskers driver to properly determine device state (clamshell
vs tablet mode).
Signed-off-by: Dmitry Torokhov
---
v2 changes: None
Lee, I was wondering if it would be OK for cros_ec_commands.h to be
merged
Whiskers is a foldable base, and thus requires combining "base presence"
signal coming from EC with base state signal (folded/unfolded) coming
from USB/HID interface to produce proper SW_TABLET_MODE event.
Signed-off-by: Nicolas Boichat
Signed-off-by: Dmitry Torokhov
---
v2 changes (addressing
This adds a "base attached" switch definition to the MKBP protocol that
is used by Whiskers driver to properly determine device state (clamshell
vs tablet mode).
Signed-off-by: Dmitry Torokhov
---
v2 changes: None
Lee, I was wondering if it would be OK for cros_ec_commands.h to be
merged
Whiskers is a foldable base, and thus requires combining "base presence"
signal coming from EC with base state signal (folded/unfolded) coming
from USB/HID interface to produce proper SW_TABLET_MODE event.
Signed-off-by: Nicolas Boichat
Signed-off-by: Dmitry Torokhov
---
v2 changes (addressing
In the process of upstreaming architecture support for ARM/NUVOTON NPCM
include/dt-bindings/clock/nuvoton,npcm7xx-clks.h was renamed
include/dt-bindings/clock/nuvoton,npcm7xx-clock.h without updating
MAINTAINERS. This updates the MAINTAINERS pattern to match the new name
of this file.
Fixes:
In the process of upstreaming architecture support for ARM/NUVOTON NPCM
include/dt-bindings/clock/nuvoton,npcm7xx-clks.h was renamed
include/dt-bindings/clock/nuvoton,npcm7xx-clock.h without updating
MAINTAINERS. This updates the MAINTAINERS pattern to match the new name
of this file.
Fixes:
at 10:02 AM, Andy Lutomirski wrote:
> On Thu, Oct 4, 2018 at 9:31 AM Nadav Amit wrote:
>> at 7:11 AM, Andy Lutomirski wrote:
>>
>>> On Oct 3, 2018, at 9:59 PM, Nadav Amit wrote:
>>>
This RFC proposes to return part of the entry-area back to the fixmap to
improve system-call
at 10:02 AM, Andy Lutomirski wrote:
> On Thu, Oct 4, 2018 at 9:31 AM Nadav Amit wrote:
>> at 7:11 AM, Andy Lutomirski wrote:
>>
>>> On Oct 3, 2018, at 9:59 PM, Nadav Amit wrote:
>>>
This RFC proposes to return part of the entry-area back to the fixmap to
improve system-call
This change makes it so that we call the asynchronous probe routines on a
CPU local to the device node. By doing this we should be able to improve
our initialization time significantly as we can avoid having to access the
device from a remote node which may introduce higher latency.
This change makes it so that we probe devices asynchronously instead of the
driver. This results in us seeing the same behavior if the device is
registered before the driver or after. This way we can avoid serializing
the initialization should the driver not be loaded until after the devices
have
This change makes it so that we use the device specific version of the
async_schedule commands to defer various tasks related to power management.
By doing this we should see a slight improvement in performance as any
device that is sensitive to latency/locality in the setup will now be
This change makes it so that we call the asynchronous probe routines on a
CPU local to the device node. By doing this we should be able to improve
our initialization time significantly as we can avoid having to access the
device from a remote node which may introduce higher latency.
This change makes it so that we probe devices asynchronously instead of the
driver. This results in us seeing the same behavior if the device is
registered before the driver or after. This way we can avoid serializing
the initialization should the driver not be loaded until after the devices
have
This change makes it so that we use the device specific version of the
async_schedule commands to defer various tasks related to power management.
By doing this we should see a slight improvement in performance as any
device that is sensitive to latency/locality in the setup will now be
This patch set provides functionality that will help to improve the
locality of the async_schedule calls used to provide deferred
initialization.
This patch set originally started out with me focused on just the one call
to async_schedule_domain in the nvdimm tree that was being used to
defer the
This patch provides a new function queue_work_near which is meant to
schedule work on a "random" CPU of the requested NUMA node. The main
motivation for this is to help assist asynchronous init to better improve
boot times for devices that are local to a specific node.
For now we just default to
This patch set provides functionality that will help to improve the
locality of the async_schedule calls used to provide deferred
initialization.
This patch set originally started out with me focused on just the one call
to async_schedule_domain in the nvdimm tree that was being used to
defer the
This patch provides a new function queue_work_near which is meant to
schedule work on a "random" CPU of the requested NUMA node. The main
motivation for this is to help assist asynchronous init to better improve
boot times for devices that are local to a specific node.
For now we just default to
This patch introduces four new variants of the async_schedule_ functions
that allow scheduling on a specific NUMA node.
The first two functions are async_schedule_near and
async_schedule_near_domain which end up mapping to async_schedule and
async_schedule_domain but provide NUMA node specific
This patch introduces four new variants of the async_schedule_ functions
that allow scheduling on a specific NUMA node.
The first two functions are async_schedule_near and
async_schedule_near_domain which end up mapping to async_schedule and
async_schedule_domain but provide NUMA node specific
On Fri, Oct 05, 2018 at 03:47:21PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/swap.h
>
> between commit:
>
> 0f83d16b8f1f ("mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS")
>
> from the btrfs-kdave
On Fri, Oct 05, 2018 at 03:47:21PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/swap.h
>
> between commit:
>
> 0f83d16b8f1f ("mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS")
>
> from the btrfs-kdave
Hi Quentin,
On 05.10.2018 11:29, Quentin Schulz wrote:
> Hi Oskari,
>
> On Thu, Oct 04, 2018 at 10:34:10PM +0300, Oskari Lemmela wrote:
>> AXP803 PMIC is register compatible with AXP813.
>>
>> Added support for AXP803/AXP813 AC power supply.
>> AXP8x3 is capable to limit input current and minimum
Hi Quentin,
On 05.10.2018 11:29, Quentin Schulz wrote:
> Hi Oskari,
>
> On Thu, Oct 04, 2018 at 10:34:10PM +0300, Oskari Lemmela wrote:
>> AXP803 PMIC is register compatible with AXP813.
>>
>> Added support for AXP803/AXP813 AC power supply.
>> AXP8x3 is capable to limit input current and minimum
Signed-off-by: Tamir Carmeli
---
drivers/staging/emxx_udc/Makefile | 2 +-
drivers/staging/emxx_udc/emxx_udc.c | 69 +++--
drivers/staging/emxx_udc/emxx_udc.h | 2 +-
3 files changed, 38 insertions(+), 35 deletions(-)
diff --git
Signed-off-by: Tamir Carmeli
---
drivers/staging/emxx_udc/Makefile | 2 +-
drivers/staging/emxx_udc/emxx_udc.c | 69 +++--
drivers/staging/emxx_udc/emxx_udc.h | 2 +-
3 files changed, 38 insertions(+), 35 deletions(-)
diff --git
On 21/09/2018 17:30, David Howells wrote:
From: Al Viro
Allow a detached tree created by open_tree(..., OPEN_TREE_CLONE) to be
attached by move_mount(2).
If by the time of final fput() of OPEN_TREE_CLONE-opened file its tree is
not detached anymore, it won't be dissolved. move_mount(2) is
On 21/09/2018 17:30, David Howells wrote:
From: Al Viro
Allow a detached tree created by open_tree(..., OPEN_TREE_CLONE) to be
attached by move_mount(2).
If by the time of final fput() of OPEN_TREE_CLONE-opened file its tree is
not detached anymore, it won't be dissolved. move_mount(2) is
On Sat, 6 Oct 2018, James Morris wrote:
> On Fri, 5 Oct 2018, David Howells wrote:
>
> > James Morris wrote:
> >
> > > > + if (strcmp(encoding, "raw") == 0) {
> > > > + strcpy(alg_name, pkey->pkey_algo);
> > > > + return 0;
> > > > + }
> > >
> > > Can
On Sat, 6 Oct 2018, James Morris wrote:
> On Fri, 5 Oct 2018, David Howells wrote:
>
> > James Morris wrote:
> >
> > > > + if (strcmp(encoding, "raw") == 0) {
> > > > + strcpy(alg_name, pkey->pkey_algo);
> > > > + return 0;
> > > > + }
> > >
> > > Can
On Fri, 5 Oct 2018, Jarkko Sakkinen wrote:
> Hi James,
>
> These are the updates to v4.20. The only new feature is non-blocking
> operation for /dev/tpm0.
Thanks, pulled to next-tpm and next-testing.
--
James Morris
On Fri, 5 Oct 2018, Jarkko Sakkinen wrote:
> Hi James,
>
> These are the updates to v4.20. The only new feature is non-blocking
> operation for /dev/tpm0.
Thanks, pulled to next-tpm and next-testing.
--
James Morris
Hi Boris
On Fri, Oct 5, 2018 at 6:29 PM Boris Brezillon
wrote:
>
> On Fri, 5 Oct 2018 17:40:44 +0200
> Ricardo Ribalda Delgado wrote:
>
> > Hi Boris
> > On Fri, Oct 5, 2018 at 4:52 PM Boris Brezillon
> > wrote:
> > >
> > > On Fri, 5 Oct 2018 16:06:57 +0200
> > > Ricardo Ribalda Delgado wrote:
Hi Boris
On Fri, Oct 5, 2018 at 6:29 PM Boris Brezillon
wrote:
>
> On Fri, 5 Oct 2018 17:40:44 +0200
> Ricardo Ribalda Delgado wrote:
>
> > Hi Boris
> > On Fri, Oct 5, 2018 at 4:52 PM Boris Brezillon
> > wrote:
> > >
> > > On Fri, 5 Oct 2018 16:06:57 +0200
> > > Ricardo Ribalda Delgado wrote:
201 - 300 of 1296 matches
Mail list logo
