I noticed that commits in your branch are not up to date with latest
Jarkoo reviews on my patches (see changes since v2). There is no
conflict if you replace conflicting patches from your branch by patches
from this series. Could you replace your duplicate commits with this
patch series?
On 28/01
On 2021-01-28 00:38, Jianxiong Gao wrote:
NVMe driver relies on the address offset to function properly.
This patch adds the offset preserve mask to NVMe driver when mapping
via dma_map_sg_attrs and unmapping via nvme_unmap_sg. The mask
depends on the page size defined by CC.MPS register of NVMe
The parameters were advertised for the "soft" synth, but they are
available for all synths.
Signed-off-by: Samuel Thibault
---
Documentation/ABI/stable/sysfs-driver-speakup | 30 +--
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/Documentation/ABI/stable/sysfs-dr
In case the serial port or cable got faulty, we may not be getting
acknowledgements any more. The driver then currently waits for 4s to
avoid jamming the device. This makes this delay configurable.
Signed-off-by: Samuel Thibault
---
Documentation/ABI/stable/sysfs-driver-speakup | 7 +++
dr
Fixes the following W=1 kernel build warning(s):
drivers/ata/libata-sata.c:1085: warning: expecting prototype for port_alloc().
Prototype was for ata_sas_port_alloc() instead
drivers/ata/libata-sata.c:1140: warning: expecting prototype for
ata_port_stop(). Prototype was for ata_sas_port_stop()
Fixes the following W=1 kernel build warning(s):
drivers/ata/libata-transport.c:258: warning: Function parameter or member 'ap'
not described in 'ata_tport_delete'
drivers/ata/libata-transport.c:258: warning: Excess function parameter 'port'
description in 'ata_tport_delete'
drivers/ata/libat
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
This is set 1 out of 3 sets required.
Lee Jones (20):
ata: ahci_dm816: Ignore -Woverride-init
ata: libata-transport: Fix some potential doc-rot
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
On Thu, Jan 28, 2021 at 12:11:06PM +0530, Prasanna Vengateshan wrote:
> The Microchip LAN937X switches have a tagging protocol which is
> very similar to KSZ tagging. So that the implementation is added to
> tag_ksz.c and reused common APIs
>
> Signed-off-by: Prasanna Vengateshan
> ---
> include
Fixes the following W=1 kernel build warning(s):
drivers/ata/libata-pmp.c:76: warning: Function parameter or member 'val' not
described in 'sata_pmp_write'
drivers/ata/libata-pmp.c:76: warning: Excess function parameter 'r_val'
description in 'sata_pmp_write'
Cc: Jens Axboe
Cc: Tejun Heo
Cc
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_artop.c:278: warning: expecting prototype for
artop_6210_qc_defer(). Prototype was for artop6210_qc_defer() instead
drivers/ata/pata_artop.c:359: warning: Function parameter or member 'id' not
described in 'artop_init_one'
driv
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_ali.c:119: warning: Function parameter or member 'mask' not
described in 'ali_20_filter'
drivers/ata/pata_ali.c:119: warning: Excess function parameter 'ap'
description in 'ali_20_filter'
drivers/ata/pata_ali.c:322: warning: Fu
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_amd.c:179: warning: Excess function parameter 'adev'
description in 'amd_fifo_setup'
drivers/ata/pata_amd.c:331: warning: Function parameter or member 'link' not
described in 'nv_pre_reset'
drivers/ata/pata_amd.c:331: warning:
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_hpt366.c:200: warning: Function parameter or member 'mask'
not described in 'hpt366_filter'
Cc: Jens Axboe
Cc: Andre Hedrick
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/ata/pata_hpt366.c | 1 +
1 file c
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Fixes the following W=1 kernel build warning(s):
drivers/ata/sata_mv.c:1162: warning: Function parameter or member 'ap' not
described in 'mv_start_edma'
drivers/ata/sata_mv.c:1162: warning: Function parameter or member 'port_mmio'
not described in 'mv_start_edma'
drivers/ata/sata_mv.c:1162: w
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_hpt37x.c:283: warning: Function parameter or member 'mask'
not described in 'hpt370_filter'
drivers/ata/pata_hpt37x.c:301: warning: Function parameter or member 'mask'
not described in 'hpt370a_filter'
drivers/ata/pata_hpt37x.c
Masami,
Care to review?
Thanks!
-- Steve
On Thu, 28 Jan 2021 20:44:27 +0800
Wang ShaoBo wrote:
> Our system encountered a re-init error when re-registering same kretprobe,
> where the kretprobe_instance in rp->free_instances is illegally accessed
> after re-init.
>
> Implementation to avo
On 28/01/21 19:04, Sean Christopherson wrote:
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
On 06/11/20 02:16, Yang Weijiang wrote:
Control-flow Enforcement Technology (CET) provides protection against
Return/Jump-Oriented Programming (ROP/JOP) attack. There're two CET
sub-features: Shadow Stack (
On Thu, Jan 28, 2021 at 04:26:09PM +0100, Geert Uytterhoeven wrote:
> Hi Naresh,
>
> On Thu, Jan 28, 2021 at 3:25 PM Naresh Kamboju
> wrote:
> > arm, sh and riscv architecture build failed on today's Linux next tag
> > 20210128.
> >
> > FYI,
> >
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> On 06/11/20 02:16, Yang Weijiang wrote:
> > Control-flow Enforcement Technology (CET) provides protection against
> > Return/Jump-Oriented Programming (ROP/JOP) attack. There're two CET
> > sub-features: Shadow Stack (SHSTK) and Indirect Branch Tracking
On Thu, Jan 28, 2021 at 05:09:05PM +0800, Hillf Danton wrote:
> On Thu, 28 Jan 2021 15:52:40 +0800 Xing Zhengjun wrote:
[ . . . ]
> >I test the patch 4 times, no warning appears in the kernel log.
>
> Thank you so much Zhengjun!
>
> And the overall brain dump so far is
>
> 1/ before and after
On 28/01/21 18:54, Paolo Bonzini wrote:
On 06/11/20 02:16, Yang Weijiang wrote:
Pass through all CET MSRs when the associated CET component (kernel vs.
user) is enabled to improve guest performance. All CET MSRs are context
switched, either via dedicated VMCS fields or XSAVES.
Co-developed-by:
On Wed, Jan 20, 2021 at 05:21:47PM +0100, Uladzislau Rezki (Sony) wrote:
> From: "Paul E. McKenney"
>
> This commit applies the __GFP_NOMEMALLOC gfp flag to memory allocations
> carried out by the single-argument variant of kvfree_rcu(), thus avoiding
> this can-sleep code path from dipping into
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_ali.c:119: warning: Function parameter or member 'mask' not
described in 'ali_20_filter'
Cc: Jens Axboe
Cc: CJ
Cc: Andre Hedrick
Cc: Alan Cox
Cc: Clear Zhang
Cc: linux-...@vger.kernel.org
Cc: and cc
Signed-off-by: Lee Jones
Samuel Thibault (2):
speakup ABI: Advertise synth parameters for all synths
speakup: Make dectlk flush timeout configurable
Documentation/ABI/stable/sysfs-driver-speakup | 37 +++
.../accessibility/speakup/speakup_dectlk.c| 11 +-
drivers/accessibility/speakup/spk_type
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
Some ATA drivers use the SCSI host template, a series of interwoven
macros, to aid with initialisation. Some of these macros conflict,
resulting in the over-writing of previously set values.
This is known behaviour and can be safely ignored.
Fixes the following W=1 kernel build warning(s):
In
On Thu, Jan 28, 2021 at 04:30:17PM +0100, Uladzislau Rezki wrote:
> On Thu, Jan 28, 2021 at 04:17:01PM +0100, Michal Hocko wrote:
> > On Thu 28-01-21 16:11:52, Uladzislau Rezki wrote:
> > > On Mon, Jan 25, 2021 at 05:25:59PM +0100, Uladzislau Rezki wrote:
> > > > On Mon, Jan 25, 2021 at 04:39:43PM
Fixes the following W=1 kernel build warning(s):
drivers/ata/ahci_xgene.c:564: warning: Function parameter or member 'host' not
described in 'xgene_ahci_handle_broken_edge_irq'
drivers/ata/ahci_xgene.c:564: warning: Excess function parameter 'ata_host'
description in 'xgene_ahci_handle_broken_
find_module is not used by modular code any more, and random driver code
has no business calling it to start with.
Signed-off-by: Christoph Hellwig
---
kernel/module.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 4bf30e4b3eaaa1..981302f616b411 1006
The static inline get_cxl_module function is entirely unused since commit
8bf6b91a5125a ("Revert "powerpc/powernv: Add support for the cxl kernel
api on the real phb"), so remove it.
Signed-off-by: Christoph Hellwig
Reviewed-by: Andrew Donnellan
---
arch/powerpc/platforms/powernv/pci-cxl.c | 22
Hi all,
this series removes support for long term unused export types and
cleans up various loose ends in the module loader.
Changes since v1:
- move struct symsearch to module.c
- rework drm to not call find_module at all
- llow RCU-sched locking for find_module
- keep find_module as a publi
Allow for a RCU-sched critical section around find_module, following
the lower level find_module_all helper, and switch the two callers
outside of module.c to use such a RCU-sched critical section instead
of module_mutex.
Signed-off-by: Christoph Hellwig
---
include/linux/module.h | 2 +-
k
On Wed, Jan 27, 2021 at 04:38:28PM -0800, Jianxiong Gao wrote:
> For devices that need to preserve address offset on mapping through
> swiotlb, this patch adds offset preserving based on page_offset_mask
> and keeps the offset if the mask is non zero. This is needed for
> device drivers like NVMe.
On Thu, Jan 28, 2021 at 05:27:25PM +, Robin Murphy wrote:
> On 2021-01-28 00:38, Jianxiong Gao wrote:
>> Some devices rely on the address offset in a page to function
>> correctly (NVMe driver as an example). These devices may use
>> a different page size than the Linux kernel. The address offs
As far as I can tell this has never been used at all, and certainly
not any time recently.
Signed-off-by: Christoph Hellwig
---
arch/x86/tools/relocs.c | 4 ++--
include/asm-generic/vmlinux.lds.h | 14 --
include/linux/export.h| 1 -
include/linux/module.h
Simplify the calling convention by passing the find_symbol_args structure
to find_symbol instead of initializing it inside the function.
Signed-off-by: Christoph Hellwig
---
kernel/module.c | 113 ++--
1 file changed, 52 insertions(+), 61 deletions(-)
struct symsearch is only used inside of module.h, so move the definition
out of module.h.
Signed-off-by: Christoph Hellwig
---
include/linux/module.h | 11 ---
kernel/module.c| 11 +++
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/include/linux/module.h
Except for two lockdep asserts module_mutex is only used in module.c.
Remove the two asserts given that the functions they are in are not
exported and just called from the module code, and mark module_mutex
static.
Signed-off-by: Christoph Hellwig
---
include/linux/module.h | 2 --
kernel/module
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> On 28/01/21 18:56, Sean Christopherson wrote:
> > On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> > > - vmx->guest_uret_msrs[j].mask =
> > > ~(u64)TSX_CTRL_CPUID_CLEAR;
> > > + if (boot_cpu_has(X86_FEATURE_RTM))
> > > +
The pull request you sent on Thu, 28 Jan 2021 11:27:38 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
> tags/media/v5.11-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fc856f1df788dc9ad13f154167ae0b442e167950
Thank you!
--
Deet-doot-do
On Thu, Jan 28, 2021 at 09:52:59AM -0800, Suren Baghdasaryan wrote:
> On Thu, Jan 28, 2021 at 1:13 AM Christoph Hellwig wrote:
> >
> > On Thu, Jan 28, 2021 at 12:38:17AM -0800, Suren Baghdasaryan wrote:
> > > Currently system heap maps its buffers with VM_PFNMAP flag using
> > > remap_pfn_range. T
On Thu, Jan 28, 2021 at 06:02:20PM +, Lee Jones wrote:
> Some ATA drivers use the SCSI host template, a series of interwoven
> macros, to aid with initialisation. Some of these macros conflict,
> resulting in the over-writing of previously set values.
Please just disable this warning globally
Tom reported that one of the GDB test-cases failed, and Boris bisected
it to commit:
d53d9bc0cf78 ("x86/debug: Change thread.debugreg6 to thread.virtual_dr6")
The debugging session led us to commit:
6c0aca288e72 ("x86: Ignore trap bits on single step exceptions")
Which describes a nice Wi
The pull request you sent on Thu, 28 Jan 2021 09:38:19 +0100 (CET):
> git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/25221c99c593bf888bd8faa67ca25b40f046e9f8
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 28 Jan 2021 16:35:55 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
> tags/asm-generic-fixes-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/228345bf98cd78f91d007478a51f9a471489e44a
Thank you!
--
D
On Thu, Jan 28, 2021 at 06:45:56PM +0200, Nikolay Borisov wrote:
> it would be placed on the __fentry__ (and not endbr64) hence it works.
> So perhaps a workaround outside of bpf could essentially detect this
> scenario and adjust the probe to be on the __fentry__ and not preceding
> instruction if
The dmabuf inode number allows userspace to uniquely identify the buffer
and avoids a dependency on /proc//fd/* when accounting per-process
DMA buffer sizes.
Signed-off-by: Kalesh Singh
---
drivers/dma-buf/dma-buf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dma-buf/dma-buf.c b/
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> On 28/01/21 19:04, Sean Christopherson wrote:
> > On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> > > On 06/11/20 02:16, Yang Weijiang wrote:
> > > > Control-flow Enforcement Technology (CET) provides protection against
> > > > Return/Jump-Oriented Programm
Since fdinfo doesn't permit reading process memory and manipulating
process state, allow accessing fdinfo under PTRACE_MODE_READ_FSCRED.
Suggested-by: Jann Horn
Signed-off-by: Kalesh Singh
---
fs/proc/base.c | 4 ++--
fs/proc/fd.c | 15 ++-
2 files changed, 16 insertions(+), 3 de
follow_hugetlb_page() once it locks the pmd/pud, checks all its
N subpages in a huge page and grabs a reference for each one.
Similar to gup-fast, have follow_hugetlb_page() grab the head
page refcount only after counting all its subpages that are part
of the just faulted huge page.
Consequently w
For a given hugepage backing a VA, there's a rather ineficient
loop which is solely responsible for storing subpages in GUP
@pages/@vmas array. For each subpage we check whether it's within
range or size of @pages and keep increment @pfn_offset and a couple
other variables per subpage iteration.
S
On Thu, 28 Jan 2021, Christoph Hellwig wrote:
> On Thu, Jan 28, 2021 at 06:02:20PM +, Lee Jones wrote:
> > Some ATA drivers use the SCSI host template, a series of interwoven
> > macros, to aid with initialisation. Some of these macros conflict,
> > resulting in the over-writing of previously
Hello Rafael,
I am chasing an issue on 5.4.x+ where scaling_max_freq is decreased to
the first entry in the _PSS table after doing an offline/online of the
cpu (to be 100% clear: scaling_max_freq is fine right after booting).
During intel_pstate_cpu_init(), acpi_processor_get_platform_limit() is
Hey,
While looking at ZONE_DEVICE struct page reuse particularly the last
patch[0], I found two possible improvements for follow_hugetlb_page()
which is solely used for get_user_pages()/pin_user_pages().
The first patch batches page refcount updates while the second tidies
up storing the subpages
On Thu, 28 Jan 2021 11:06:26 +0100, Geert Uytterhoeven wrote:
> If CONFIG_MMU is not set (e.g. m68k/m5272c3_defconfig):
>
> mm/nommu.c:1671:6: error: conflicting types for ‘filemap_map_pages’
> 1671 | void filemap_map_pages(struct vm_fault *vmf,
> | ^
> In
Hi!
On Thu, 2021-01-28 at 15:21 +0300, Nikita Shubin wrote:
> - use predefined constants instead of plain numbers
> - use provided bank IRQ number instead of defined constant
> for port F
>
> Signed-off-by: Nikita Shubin
Acked-by: Alexander Sverdlin
> ---
> drivers/gpio/gpio-ep93xx.c | 12
On Wed, Jan 27, 2021 at 10:58 PM Candle Sun wrote:
>
> From: Candle Sun
>
> Though do_overwritten() follows do_nothing() in source code, the final
> memory address order is determined by the compiler. We can't always
> assume address of do_overwritten() is bigger than do_nothing(). At least
> the
During load-balance, groups classified as group_misfit_task are filtered
out if they do not pass
group_smaller_max_cpu_capacity(, );
which itself employs fits_capacity() to compare the sgc->max_capacity of
both groups.
Due to the underlying margin, fits_capacity(X, 1024) will return false for
When triggering an active load balance, sd->nr_balance_failed is set to
such a value that any further can_migrate_task() using said sd will ignore
the output of task_hot().
This behaviour makes sense, as active load balance intentionally preempts a
rq's running task to migrate it right away, but t
Comparing capacity extrema of local and source sched_group's doesn't make
much sense when at the day of the day the imbalance will be pulled by a
known env->dst_cpu, whose capacity can be anywhere within the local group's
capacity extrema.
Replace group_smaller_{min, max}_cpu_capacity() with compa
Rik noted a while back that a handful of
sd->flags & SD_ASYM_CPUCAPACITY
& family in the CFS load-balancer code aren't guarded by the
sched_asym_cpucapacity static branch.
The load-balancer is already doing a humongous amount of work, but turning
those checks into NOPs for those who don't need
Hi folks,
Here is this year's series of misfit changes. On the menu:
o Patch 1 is an independent active balance cleanup
o Patch 2 adds some more sched_asym_cpucapacity static branches
o Patch 3 introduces yet another margin for capacity to capacity
comparisons
o Patches 4-6 build on top of patc
From: Stefan Chulski
Signed-off-by: Stefan Chulski
---
Documentation/devicetree/bindings/net/marvell-pp2.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/marvell-pp2.txt
b/Documentation/devicetree/bindings/net/marvell-pp2.txt
index
From: Stefan Chulski
Currently we have PP2v1 and PP2v2 hw-versions, with some different
handlers depending upon condition hw_version = MVPP21/MVPP22.
In a future there will be also PP2v3. Let's use now the generic
"if equal/notEqual MVPP21" for all cases instead of "if MVPP22".
This patch does n
From: Stefan Chulski
To support Flow Control ring size should be at least 1024 descriptors.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
b/drivers/net/eth
Hi!
> Motorola is using a custom TS 27.010 based serial port line discipline
> for various devices on the modem. These devices can be accessed on
> dedicated channels using Linux kernel serdev-ngsm driver.
>
> For the GNSS on these devices, we need to kick the GNSS device at a
> desired rate. Oth
Hi!
On Thu, 2021-01-28 at 15:21 +0300, Nikita Shubin wrote:
> Port F irq's should be statically mapped to EP93XX_GPIO_F_IRQ_BASE.
>
> So we need to specify girq->first otherwise:
>
> "If device tree is used, then first_irq will be 0 and
> irqs get mapped dynamically on the fly"
>
> And that's n
From: Stefan Chulski
Flow Control periodic timer would be used if port in
XOFF to transmit periodic XOFF frames.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 13 +-
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 45
2 files cha
From: Stefan Chulski
RXQ size increased to support Firmware Flow Control.
Minimum depletion thresholds to support FC is 1024 buffers.
Default set to 1024 descriptors and maximum size to 2048.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 4 ++--
1 file changed,
From: Stefan Chulski
Patch check that TX FC firmware is running in CM3.
If not, global TX FC would be disabled.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 1 +
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 42
2 files changed,
From: Stefan Chulski
This patch fix GMAC TX flow control autoneg.
Flow control autoneg wrongly were disabled with enabled TX
flow control.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
Consider the following (hypothetical) asymmetric CPU capacity topology,
with some amount of capacity pressure (RT | DL | IRQ | thermal):
DIE [ ]
MC [][]
0 1 2 3
| CPU | capacity_orig | capacity |
|-+---+--|
| 0 | 870 |
From: Stefan Chulski
New FIFO flow control feature were added in PPv23.
PPv2 FIFO polled by HW and trigger pause frame if FIFO
fill level is below threshold.
FIFO HW flow control enabled with CM3 RXQ&BM flow
control with ethtool.
Current FIFO thresholds is:
9KB for port with maximum speed 10Gb/s
Consider a 4-CPU big.LITTLE system with CPUs 0-1 as LITTLEs and CPUs 2-3 as
bigs. The resulting sched_domain hierarchy is:
DIE [ ]
MC [][]
0 1 2 3
When running a multithreaded CPU-bound workload (i.e. 1 hog per CPU), the
expected behaviour is to have the about-to-i
Misfit tasks can and will be preempted by the stopper to migrate them over
to a higher-capacity CPU. However, when runnable but not current misfit
tasks are scanned by the load balancer (i.e. detach_tasks()), the
task_hot() ratelimiting logic may prevent us from enqueuing said task onto
a higher-ca
From: Stefan Chulski
This patch add RXQ flow control configurations.
Patch do not enable flow control itself, flow control
disabled by default.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 35 +-
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 114
From: Stefan Chulski
Feature double size of BPPI by decreasing number of pools from 16 to 8.
Increasing of BPPI size protect BM drop from BPPI underrun.
Underrun could occurred due to stress on DDR and as result slow buffer
transition from BPPE to BPPI.
New BPPI threshold recommended by spec is:
From: Stefan Chulski
This patch add ethtool flow control configuration support.
Tx flow control retrieved correctly by ethtool get function.
FW per port ethtool configuration capability added.
Patch also takes care about mtu change procedure, if PPv2 switch
BM pools during mtu change.
Signed-o
check_misfit_status() checks for both capacity pressure & available CPUs
with higher capacity. Now that we have a sane(ish) capacity comparison
margin which is used throughout load-balance, this can be condensed into a
single check:
capacity_greater(, );
This has the added benefit of returning
On Thu, 2021-01-28 at 15:21 +0300, Nikita Shubin wrote:
> - replace plain numbers with girq->num_parents in devm_kcalloc
> - replace plain numbers with girq->num_parents for port F
> - refactor i - 1 to i + 1 to make loop more readable
> - combine getting IRQ's loop and setting handler's into singl
From: Stefan Chulski
This patch enables global flow control in FW and in the
phylink validate mask.
Signed-off-by: Stefan Chulski
---
drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 13 ++---
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 30 +++-
2 files changed, 38 i
From: Stefan Chulski
The firmware needs to monitor the RX Non-occupied descriptor
bits for flow control to move to XOFF mode.
These bits need to be unmasked to be functional, but they will
not raise interrupts as we leave the RX exception summary
bit in MVPP2_ISR_RX_TX_MASK_REG clear.
Signed-off
Hi!
On Thu, 2021-01-28 at 15:21 +0300, Nikita Shubin wrote:
> As ->to_irq is redefined in gpiochip_add_irqchip, having it defined
> in
> driver is useless, so let's drop it.
>
> Signed-off-by: Nikita Shubin
Acked-by: Alexander Sverdlin
> ---
> drivers/gpio/gpio-ep93xx.c | 6 --
> 1 file
On 2021-01-28 09:08, Minchan Kim wrote:
On Thu, Jan 28, 2021 at 12:28:37AM -0800, Chris Goldsworthy wrote:
On 2021-01-26 18:59, Matthew Wilcox wrote:
> On Tue, Jan 26, 2021 at 02:59:17PM -0800, Minchan Kim wrote:
> > The release buffer_head in LRU is great improvement for migration
> > point of
On Thu, Jan 28, 2021 at 12:15 PM Colin King wrote:
>
> From: Colin Ian King
>
> The variable rtstatu is being initialized with a value that is never
> read and it is being updated later with a new value. The initialization
> is redundant and can be removed.
>
> Addresses-Coverity: ("Unused value
If the task is not running, run_posix_cpu_timers has nothing
to elapsed, so spare IPI in that case.
Suggested-by: Peter Zijlstra
Signed-off-by: Marcelo Tosatti
Index: linux-2.6/kernel/sched/core.c
===
--- linux-2.6.orig/kernel/sche
When adding a tick dependency to a task, its necessary to
wakeup the CPU where the task resides to reevaluate tick
dependencies on that CPU.
However the current code wakes up all nohz_full CPUs, which
is unnecessary.
Switch to waking up a single CPU, by using ordering of writes
to task->cpu and
Rather than waking up all nohz_full CPUs on the system, only wakeup
the target CPUs of member threads of the signal.
Reduces interruptions to nohz_full CPUs.
Signed-off-by: Marcelo Tosatti
Index: linux-2.6/kernel/time/tick-sched.c
===
When enabling per-CPU posix timers, an IPI to nohz_full CPUs might be
performed (to re-read the dependencies and possibly not re-enter
nohz_full on a given CPU).
A common case is for applications that run on nohz_full= CPUs
to not use POSIX timers (eg DPDK). This patch changes the notification
to
From: Govind Singh
Use request exclusive reset control for wcss reset controls.
Signed-off-by: Govind Singh
Signed-off-by: Gokul Sriram Palanisamy
---
drivers/remoteproc/qcom_q6v5_wcss.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/remoteproc/qcom_q6v5_wcs
On Thu, Jan 28, 2021 at 11:12:50AM -0600, Steve French wrote:
> For the last month my logs have been flooded many times a second with:
>
> "nouveau :01:00.0: [drm] *ERROR* crtc 50: Can't calculate
> constants, dotclock = 0!"
Would indicate someone has a bogus adjusted_mode in their state stru
On 28/01/2021 18:20, Peter Zijlstra wrote:
> --- a/arch/x86/kernel/hw_breakpoint.c
> +++ b/arch/x86/kernel/hw_breakpoint.c
> @@ -496,9 +496,32 @@ static int hw_breakpoint_handler(struct
> dr6_p = (unsigned long *)ERR_PTR(args->err);
> dr6 = *dr6_p;
>
> - /* If it's a single step,
On Thu, Jan 28, 2021 at 03:53:36PM +, Chuck Lever wrote:
> > On Jan 28, 2021, at 10:34 AM, Dan Carpenter
> > wrote:
> > Fixes tags are used for a lot of different things:
> > 1) If there is a fixes tag, then you can tell it does *NOT* have to
> >be back ported because the original commit
201 - 300 of 1344 matches
Mail list logo
