allmodconfig
powerpc allyesconfig
powerpc allmodconfig
i386 randconfig-a006-20201119
i386 randconfig-a005-20201119
i386 randconfig-a002-20201119
i386 randconfig-a001
This change converts the simple allocations in the driver to used
device-managed allocation functions.
This removes the error path entirely in the probe function, and reduces
some code in the remove function.
Signed-off-by: Alexandru Ardelean
---
drivers/uio/uio_dmem_genirq.c | 34
This moves move pm_runtime_disable on a devm_add_action_or_reset() handler.
And with the use of the devm_uio_register_device() function, the remove
hook is no longer required.
Signed-off-by: Alexandru Ardelean
---
drivers/uio/uio_dmem_genirq.c | 28 ++--
1 file changed,
On Fri, Nov 20, 2020 at 5:51 AM Finn Thain wrote:
> The idea behind iop_preinit() was to put the SCC IOP into bypass mode.
> However, that remains unimplemented and implementing it would be
> difficult. Let the comments and code reflect this. Even if iop_preinit()
> worked as described in the
Hi,
I was recently asked to explain how schedutil works, the below write-up
is the result of that and I figured we might as well stick it in the
tree.
Not as a patch for easy reading and commenting.
---
NOTE; all this assumes a linear relation between frequency and work capacity,
we know this
On Fri, 20 Nov 2020 15:48:49 +0800
Qinglang Miao wrote:
> put_device calls release function which do kfree() inside.
> So following use of sch would cause use-after-free bugs.
>
> Fix these by simply adjusting the position of put_device.
>
> Fixes: 37db8985b211 ("s390/cio: add basic protected
On Fri, Nov 20, 2020 at 06:21:55AM +, Alice Guo wrote:
> > > + soc:
> > > +type: object
> > > +properties:
> > > + compatible:
> > > +oneOf:
> > > + - description: new version DTS for i.MX8M SoCs
> > > +items:
> > > + - enum:
> > > +
From: Kaixu Xia
The body of the if statement can be executed only when the variable
vlan_count equals to 32, so the condition of the while statement can
not be true and the while statement is dead code. Remove it.
Reported-by: Tosk Robot
Signed-off-by: Kaixu Xia
---
On Thu, 19 Nov 2020, Miquel Raynal wrote:
> On Mon, 2020-11-09 at 18:22:06 UTC, Lee Jones wrote:
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/mtd/devices/powernv_flash.c:129: warning: Cannot understand *
> > @mtd: the device
> >
On Fri 20-11-20 14:43:07, Muchun Song wrote:
> The purpose of introducing HUGETLB_PAGE_FREE_VMEMMAP is to configure
> whether to enable the feature of freeing unused vmemmap associated
> with HugeTLB pages. Now only support x86.
Why is the config option necessary? Are code savings with the
Hi Finn,
On Fri, Nov 20, 2020 at 5:51 AM Finn Thain wrote:
> Don't add platform resources that won't be used. This avoids a
> recently-added warning from the driver core, that can show up on a
> multi-platform kernel when !MACH_IS_MAC.
>
> [ cut here ]
> WARNING: CPU: 0
In dcon_probe(), when platform_device_add() failes to add the device,
it jumps to call platform_device_unregister() to remove the device,
which is unnecessary. So use platform_device_put() instead.
Fixes: 53c43c5ca133 ("Revert "Staging: olpc_dcon: Remove obsolete driver"")
Signed-off-by: Jing
There's a proximity sensor on Lazor devices, but only for LTE SKUs.
Enable it only on the LTE SKUs and also configure it properly so it
works.
Cc: Douglas Anderson
Cc: Matthias Kaehlcke
Signed-off-by: Stephen Boyd
---
Changes from v1
On Thu, 19 Nov 2020, Dmitry Torokhov wrote:
> On Fri, Nov 13, 2020 at 07:55:25AM +, Lee Jones wrote:
> > On Thu, 12 Nov 2020, Dmitry Torokhov wrote:
> >
> > > On Thu, Nov 12, 2020 at 11:01:55AM +, Lee Jones wrote:
> > > > Fixes the following W=1 kernel build warning(s):
> > > >
> > > >
kfree(cdev) is called in put_device in the error branch. So that
device_unlock(>dev) would raise a use-after-free bug. In fact,
there's no need to call device_unlock after put_device.
Fix it by adding simply return after put_device.
Fixes: a6ef15652d26 ("s390/cio: fix use after free in cmb
When put_device(>dev) being called, kfree(bridge) is inside
of release function, so the following device_del would cause a
use-after-free bug.
Fixes: 37d6a0a6f470 ("PCI: Add pci_register_host_bridge() interface")
Reported-by: Hulk Robot
Signed-off-by: Qinglang Miao
---
drivers/pci/probe.c | 2
kfree(host->card) has been called in put_device so that
another kfree would raise cause a double-free bug.
Fixes: 0193383a5833 ("memstick: core: fix device_register() error handling")
Reported-by: Hulk Robot
Signed-off-by: Qinglang Miao
---
drivers/memstick/core/memstick.c | 1 -
1 file
put_device calls release function which do kfree() inside.
So following use of sch would cause use-after-free bugs.
Fix these by simply adjusting the position of put_device.
Fixes: 37db8985b211 ("s390/cio: add basic protected virtualization support")
Fixes: 74bd0d859dc3 ("s390/cio: fix unlocked
On Fri, Nov 20, 2020 at 03:30:35PM +0800, David Gow wrote:
> On Fri, Nov 20, 2020 at 2:27 PM Moritz Fischer wrote:
> >
> > Hi David,
> >
> > On Thu, Nov 19, 2020 at 12:22:09AM -0800, David Gow wrote:
> > > Because dfl.c uses the 'devm_ioremap', 'devm_iounmap',
> > > 'devm_ioremap_resource', and
kfree(port) is called in put_device(>dev) so that following
use would cause use-after-free bug.
The former put_device is redundant for device_unregister contains
put_device already. So just remove it to fix this.
Fixes: 86bdf218a717 ("[SCSI] zfcp: cleanup unit sysfs attribute usage")
kfree(port) is called in put_device(>dev) so that following
use would cause use-after-free bug.
the former put_device is redundant for device_unregister contains
put_device already. So just remove it to fix this.
Fixes: 83d4e1c33d93 ("[SCSI] zfcp: cleanup port sysfs attribute usage")
kfree(dev) has been called inside put_device so anther
kfree would cause a use-after-free bug/
Fixes: 8286ae03308c ("MIPS: Add CDMM bus support")
Reported-by: Hulk Robot
Signed-off-by: Qinglang Miao
---
drivers/bus/mips_cdmm.c | 1 -
1 file changed, 1 deletion(-)
diff --git
kfree(conn) is called inside put_device(>dev) so that
another one would cause use-after-free. Besides, device_unregister
should be used here rather than put_device.
Fixes: f3c893e3dbb5 ("scsi: iscsi: Fail session and connection on transport
registration failure")
Reported-by: Hulk Robot
kfree(dev) is called in put_device(>device) so that following
use would cause use-after-free bug.
There are two inappropriate use of put_device:
1. In create_visor_device, put dev_err before put_device to fix this.
2. In remove_visor_device, the former put_device is redundant because
On Fri, 2020-11-20 at 07:54 +0100, Greg Kroah-Hartman wrote:
> On Fri, Nov 20, 2020 at 02:48:50PM +0800, Min Guo wrote:
> > Hi greg k-h:
> > On Wed, 2020-11-18 at 12:48 +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Nov 17, 2020 at 04:21:25PM +0800, min@mediatek.com wrote:
> > > > From: Min
We should not be configuring the controller as a wakeup source in the
driver, but rather rely on I2C core to mark it as such by either
instantiating as I2C_CLIENT_WAKEUP or specifying "wakeup-source" device
property.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/adp5589-keys.c | 2
The J7200 SOM have additional io expander which is used to control several
SOM level muxes to make sure that the correct signals are routed to the
correct pin on the SOM <-> CPB connectors.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Vignesh Raghavendra
---
If device is set up as a wakeup source, I2C core configures the interrupt
line as wake IRQ and PM core automatically configures it for waking up the
system on system suspend transition, so we do not have to explicitly call
enable_irq_wake() and disable_irq_wake() in suspend/resume.
Signed-off-by:
This DT property can be 0, 16, and then 64, but not 32. The math here
doesn't recognize this slight bump in the power of 2 numbers and
translates a DT property of 64 into the register value '3' when it
really should be '2'. Fix it by subtracting one more if the number being
translated is larger
On Fri, Nov 20, 2020 at 5:51 AM Finn Thain wrote:
> Cc: Joshua Thompson
> Signed-off-by: Finn Thain
Reviewed-by: Geert Uytterhoeven
i.e. will queue in the m68k for-v5.11 branch.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
J7200 main_i2c1 is connected to the i2c bus on the CPB marked as main_i2c3
The i2c1 devices on the CPB are _not_ connected to the SoC, they are not
usable with the J7200 SOM.
Correct the expander name from exp4 to exp3 and at the same time add the
line names as well.
Signed-off-by: Peter
On Fri, Nov 20, 2020 at 5:51 AM Finn Thain wrote:
> There is still some missing hardware support that affects all models,
> such as sound chip and localtalk support. However, many models are well
> supported, including the Quadra 800 emulated by QEMU. Missing hardware
> support is mostly
Hi,
Changes since v1:
- Added REviewed-by from Vignesh
- Comment block to explain main_i2c1 connection to CPB
The main_i2c0 missed the ioexpander present on the SOM itself to control muxes
to route signals to CPB connectors.
The main_i2c1 of J7200 is _not_ connected to the i2c1 of CPB, it is
Hi Finn,
thanks for your patch!
Tested on Atari Falcon (with falconide, and pata_falcon modules).
Reviewed-by: Michael Schmitz
Tested-by: Michael Schmitz
Am 20.11.2020 um 17:39 schrieb Finn Thain:
It is possible that bus_reset_cleanup() or .eh_abort_handler could
be invoked during
On Thu, Nov 19, 2020 at 10:35:22PM -0800, Prashant Malani wrote:
> The commit to introduce the num_altmodes attribute for partner had an
> error where one of the parameters was named differently in the comment
> and the function signature. Fix the version in the comment to align with
> what is in
Hi Finn,
thanks for your patch!
Tested on Atari Falcon (with falconide, and pata_falcon modules).
Reviewed-by: Michael Schmitz
Tested-by: Michael Schmitz
Am 20.11.2020 um 17:39 schrieb Finn Thain:
Refactor to avoid needless calls to NCR5380_maybe_release_dma_irq().
This makes the machine
On Thu, Nov 05, 2020 at 06:03:05PM -0800, Prashant Malani wrote:
> On occasion, the Chrome Embedded Controller (EC) can send a mux
> configuration which doesn't map to a particular data mode. For instance,
> dedicated Type C chargers, when connected, may cause only
> USB_PD_MUX_POLARITY_INVERTED
On Fri, Nov 20, 2020 at 2:27 PM Moritz Fischer wrote:
>
> Hi David,
>
> On Thu, Nov 19, 2020 at 12:22:09AM -0800, David Gow wrote:
> > Because dfl.c uses the 'devm_ioremap', 'devm_iounmap',
> > 'devm_ioremap_resource', and 'devm_platform_ioremap_resource'
> > functions, it should depend on
Hello,
syzbot found the following issue on:
HEAD commit:03430750 Add linux-next specific files for 20201116
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=123c946a50
kernel config: https://syzkaller.appspot.com/x/.config?x=a1c4c3f27041fdb8
dashboard
On Fri, Nov 20, 2020 at 10:59:59AM +0800, tanhuazhong wrote:
> On 2020/11/20 6:02, Michal Kubecek wrote:
> >
> > We could use a similar approach as struct ethtool_link_ksettings, e.g.
> >
> > struct kernel_ethtool_coalesce {
> > struct ethtool_coalesce base;
> > /*
Hello again Dimitry,
I haven't received any response yet, so I will ask again.
I would like to know, the current status about my other patches for goodix and
atmel input.
Are there any problems, or what I have to do, to be applied?
Thanks,
Andrej
> Hello Dimitry,
>
> Thank you for that.
>
On Thu, Nov 19, 2020 at 9:53 PM Jakub Kicinski wrote:
>
> On Thu, 19 Nov 2020 10:53:23 -0800 Edwin Peer wrote:
> > > Fix to return a negative error code from the error handling
> > > case instead of 0, as done elsewhere in this function.
> > >
> > > Fixes: c0c050c58d84 ("bnxt_en: New Broadcom
[15561.391527] [ cut here ]
[15561.391560] WARNING: CPU: 0 PID: 20957 at
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x4a/0x50 [nouveau]
[15561.391562] Modules linked in: nls_utf8(E) isofs(E) fuse(E) msr(E)
xt_comment(E) br_netfilter(E) xt_physdev(E)
On Fri, Nov 20, 2020 at 01:04:23PM +0800, Minchan Kim wrote:
> On Thu, Nov 19, 2020 at 11:34:32AM +0800, Zhenhua Huang wrote:
> > On Wed, Nov 04, 2020 at 07:27:03AM +0800, Minchan Kim wrote:
> > > Sorry if this mail corrupts the mail thread or had heavy mangling
> > > since I lost this mail from
On 19/11/2020 18.10, Vignesh Raghavendra wrote:
>
>
> On 11/19/20 6:56 PM, Peter Ujfalusi wrote:
>> J7200 main_i2c1 is connected to the i2c bus on the CPB marked as main_i2c3
>>
>> The i2c1 devices on the CPB are _not_ connected to the SoC, they are not
>> usable with the J7200 SOM.
>>
>>
On Thu, 2020-11-19 at 21:21 -0800, Jakub Kicinski wrote:
> We do have our own comment style rule in networking since the beginning
> of time, and reverse xmas tree, so it's not completely crazy.
reverse xmas tree is completely crazy.
But I posted a patch to checkpatch to suggest it for net/
and
Adding Guy Damary
Guy, can you help with this one? I believe there is a bugzilla issue
for this already...
--
Cheers,
Luca.
On Thu, 2020-11-19 at 17:42 +0100, Gonsolo wrote:
> Hi!
>
> Sporadically my wifi hangs. Any idea why?
> This is on a 5.10.0-051000rc2-lowlatency kernel from
>
On Sun, Nov 15, 2020 at 07:08:07PM +, Corentin Labbe wrote:
> This patch fixes the following smatch warnings:
> drivers/crypto/allwinner/sun8i-ce/sun8i-ce-hash.c:412
> sun8i_ce_hash_run() warn: possible memory leak of 'result'
> Note: "buf" is leaked as well.
>
> Furthermore, in case of
On Fri, Nov 13, 2020 at 05:32:35PM +0800, Yang Shen wrote:
> The patch 'irqchip/gic-v3-its: Balance initial LPI affinity across CPUs'
> set the IRQ to an uncentain CPU. If an IRQ is bound to the CPU used by the
> thread which is sending request, the throughput will be just half.
>
> So allocate a
On Thu, Nov 12, 2020 at 01:07:02PM -0700, Nathan Chancellor wrote:
> Clang warns:
>
> drivers/crypto/amcc/crypto4xx_core.c:921:60: warning: operator '?:' has
> lower precedence than '|'; '|' will be evaluated first
> [-Wbitwise-conditional-parentheses]
>
On Thu, Nov 12, 2020 at 11:21:46AM +0200, Horia Geantă wrote:
>
> Wang Qing reports that IS_ERR_OR_NULL() should be matched with
> PTR_ERR_OR_ZERO(), not PTR_ERR().
>
> As it turns out, the error path always returns an error code,
> i.e. NULL is never returned.
> Update the code accordingly -
On Fri, Nov 20, 2020 at 02:48:50PM +0800, Min Guo wrote:
> Hi greg k-h:
> On Wed, 2020-11-18 at 12:48 +0100, Greg Kroah-Hartman wrote:
> > On Tue, Nov 17, 2020 at 04:21:25PM +0800, min@mediatek.com wrote:
> > > From: Min Guo
> > >
> > > Remove unused 'devctl' variable to fix compile
fixed the following warnings
drivers/gpu/drm/nouveau/nouveau_bo.c:1227:17: warning: variable ‘dev’
set but not used [-Wunused-but-set-variable]
drivers/gpu/drm/nouveau/nouveau_bo.c:1251:17: warning: variable ‘dev’
set but not used [-Wunused-but-set-variable]
Signed-off-by: Tian Tao
---
We only can free the unused vmemmap to the buddy system when the
size of struct page is a power of two.
Signed-off-by: Muchun Song
---
mm/hugetlb_vmemmap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c
index
There are only `RESERVE_VMEMMAP_SIZE / sizeof(struct page)` struct pages
can be used when CONFIG_HUGETLB_PAGE_FREE_VMEMMAP, so add a BUILD_BUG_ON
to catch this invalid usage of tail struct page.
Signed-off-by: Muchun Song
---
mm/hugetlb_vmemmap.c | 3 +++
1 file changed, 3 insertions(+)
diff
Hi greg k-h:
On Wed, 2020-11-18 at 12:48 +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 17, 2020 at 04:21:25PM +0800, min@mediatek.com wrote:
> > From: Min Guo
> >
> > Remove unused 'devctl' variable to fix compile warnings:
> >
> > drivers/usb/musb/musbhsdma.c: In function
For hugetlb page, there are more metadata to save in the struct
page. But the head struct page cannot meet our needs, so we have
to abuse other tail struct page to store the metadata. In order
to avoid conflicts caused by subsequent use of more tail struct
pages, we can gather these discrete
Merge pte to huge pmd if it has ever been split. Now only support
gigantic page which's vmemmap pages size is an integer multiple of
PMD_SIZE. This is the simplest case to handle.
Signed-off-by: Muchun Song
---
arch/x86/include/asm/hugetlb.h | 8 +++
mm/hugetlb_vmemmap.c | 118
We should flush work when dissolving a hugetlb page to make sure that
the hugetlb page is freed to the buddy.
Signed-off-by: Muchun Song
---
mm/hugetlb.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index
Add a kernel parameter hugetlb_free_vmemmap to disable the feature of
freeing unused vmemmap pages associated with each hugetlb page on boot.
Signed-off-by: Muchun Song
---
Documentation/admin-guide/kernel-parameters.txt | 9 +
Documentation/admin-guide/mm/hugetlbpage.rst| 3 +++
When we allocate hugetlb page from buddy, we may need split huge pmd
to pte. When we free the hugetlb page, we can merge pte to pmd. So
we need to distinguish whether the previous pmd has been split. The
page table is not allocated from slab. So we can reuse the PG_slab
to indicate that the pmd
Because we reuse the first tail page, if we set PageHWPosion on a
tail page. It indicates that we may set PageHWPoison on a series
of pages. So we can use the head[4].mapping to record the real
error page index and set the raw error page PageHWPoison later.
Signed-off-by: Muchun Song
---
The gigantic page is allocated by bootmem, if we want to free the
unused vmemmap pages. We also should allocate the page table. So
we also allocate page tables from bootmem.
Signed-off-by: Muchun Song
---
include/linux/hugetlb.h | 3 +++
mm/hugetlb.c| 5 +
mm/hugetlb_vmemmap.c
The __free_huge_page_pmd_vmemmap and __remap_huge_page_pmd_vmemmap are
almost the same code. So introduce remap_free_huge_page_pmd_vmemmap
helper to simplify the code.
Signed-off-by: Muchun Song
---
mm/hugetlb_vmemmap.c | 108 +--
1 file changed,
In the subsequent patch, we will allocate the vmemmap pages when free
huge pages. But update_and_free_page() is be called from a non-task
context(and hold hugetlb_lock), we can defer the actual freeing in
a workqueue to prevent use GFP_ATOMIC to allocate the vmemmap pages.
Signed-off-by: Muchun
When we allocate a hugetlb page from the buddy, we should free the
unused vmemmap pages associated with it. We can do that in the
prep_new_huge_page().
Signed-off-by: Muchun Song
---
arch/x86/include/asm/hugetlb.h | 9 ++
arch/x86/include/asm/pgtable_64_types.h | 8 ++
mm/hugetlb.c
When we free a hugetlb page to the buddy, we should allocate the vmemmap
pages associated with it. We can do that in the __free_hugepage().
Signed-off-by: Muchun Song
---
mm/hugetlb.c | 2 ++
mm/hugetlb_vmemmap.c | 100 +++
In the later patch, we will use the vmemmap page table lock to
guard the splitting of the vmemmap PMD. So initialize the vmemmap
page table lock.
Signed-off-by: Muchun Song
---
mm/hugetlb_vmemmap.c | 69
1 file changed, 69 insertions(+)
diff
The page->private shares storage with page->ptl. In the later patch,
we will use the page->ptl. So here we combine bootmem info and type
into page->freelist so that we can do not use page->private.
Signed-off-by: Muchun Song
---
arch/x86/mm/init_64.c| 2 +-
include/linux/bootmem_info.h
In the later patch, we can use the free_vmemmap_page() to free the
unused vmemmap pages and initialize a page for vmemmap page using
via prepare_vmemmap_page().
Signed-off-by: Muchun Song
---
include/linux/bootmem_info.h | 24
1 file changed, 24 insertions(+)
diff
On x86_64, vmemmap is always PMD mapped if the machine has hugepages
support and if we have 2MB contiguous pages and PMD alignment. If we
want to free the unused vmemmap pages, we have to split the huge PMD
firstly. So we should pre-allocate pgtable to split PMD to PTE.
Signed-off-by: Muchun Song
Every HugeTLB has more than one struct page structure. The 2M HugeTLB
has 512 struct page structure and 1G HugeTLB has 4096 struct page
structures. We __know__ that we only use the first 4(HUGETLB_CGROUP_MIN_ORDER)
struct page structures to store metadata associated with each HugeTLB.
There are a
In the later patch, we will use {get,put}_page_bootmem() to initialize
the page for vmemmap or free vmemmap page to buddy. So move them out of
CONFIG_MEMORY_HOTPLUG_SPARSE. This is just code movement without any
functional change.
Signed-off-by: Muchun Song
Acked-by: Mike Kravetz
Reviewed-by:
Hi all,
This patch series will free some vmemmap pages(struct page structures)
associated with each hugetlbpage when preallocated to save memory.
The struct page structures (page structs) are used to describe a physical
page frame. By default, there is a one-to-one mapping from a page frame to
The purpose of introducing HUGETLB_PAGE_FREE_VMEMMAP is to configure
whether to enable the feature of freeing unused vmemmap associated
with HugeTLB pages. Now only support x86.
Signed-off-by: Muchun Song
---
arch/x86/mm/init_64.c | 2 +-
fs/Kconfig| 14 ++
2 files
Move bootmem info registration common API to individual bootmem_info.c
for later patch use. This is just code movement without any functional
change.
Signed-off-by: Muchun Song
Acked-by: Mike Kravetz
Reviewed-by: Oscar Salvador
---
arch/x86/mm/init_64.c | 1 +
Hi Stephen,
On Fri, Nov 20, 2020 at 04:15:06PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
>
> drivers/usb/typec/class.c:632: warning: Excess function parameter
> 'num_alt_modes' description in
The commit to introduce the num_altmodes attribute for partner had an
error where one of the parameters was named differently in the comment
and the function signature. Fix the version in the comment to align with
what is in the function signature.
This fixes the following htmldocs warning:
Hi Daniel,
On Wed, 18 Nov 2020 at 13:16, Daniel Vetter wrote:
>
> On Wed, Nov 18, 2020 at 3:40 AM John Stultz wrote:
> > On Fri, Nov 13, 2020 at 12:39 PM Daniel Vetter wrote:
> > > On Thu, Nov 12, 2020 at 08:11:02PM -0800, John Stultz wrote:
> > > > On Thu, Nov 12, 2020 at 1:32 AM Daniel
Add all other man pages to the "see also" list except for
perf-script-perl and perf-script-python that are linked to from
perf-script.
v2. Fix accidentally listing perf-top twice.
Signed-off-by: Ian Rogers
---
tools/perf/Documentation/perf.txt | 12
1 file changed, 12
Add health reporters for RVU NPA block.
NPA Health reporters handle following HW event groups
- GENERAL events
- ERROR events
- RAS events
- RVU event
An event counter per event is maintained in SW.
Output:
# devlink health
pci/0002:01:00.0:
reporter npa
state healthy error 0
Add health reporters for RVU NIX block.
NIX Health reporter handle following HW event groups
- GENERAL events
- RAS events
- RVU event
An event counter per event is maintained in SW.
Output:
# ./devlink health
pci/0002:01:00.0:
reporter npa
state healthy error 0 recover 0
reporter
Add all other man pages to the "see also" list except for
perf-script-perl and perf-script-python that are linked to from
perf-script.
Signed-off-by: Ian Rogers
---
tools/perf/Documentation/perf.txt | 12
1 file changed, 12 insertions(+)
diff --git
Add basic devlink and devlink health reporters.
Devlink health reporters are added for NPA and NIX blocks.
These reporters report the error count in respective blocks.
Address Jakub's comment to add devlink support for error reporting.
https://www.spinics.net/lists/netdev/msg670712.html
Add devlink support to AF driver. Basic devlink support is added.
Currently info_get is the only supported devlink ops.
devlink ouptput looks like this
# devlink dev
pci/0002:01:00.0
# devlink dev info
pci/0002:01:00.0:
driver octeontx2-af
versions:
fixed:
mbox version: 9
Hi David,
On Thu, Nov 19, 2020 at 12:22:09AM -0800, David Gow wrote:
> Because dfl.c uses the 'devm_ioremap', 'devm_iounmap',
> 'devm_ioremap_resource', and 'devm_platform_ioremap_resource'
> functions, it should depend on HAS_IOMEM.
>
> This fixes make allyesconfig under UML (ARCH=um), which
Hi Russ,
On Thu, Nov 19, 2020 at 06:39:44PM -0800, Russ Weight wrote:
>
>
> On 11/15/20 3:03 PM, Moritz Fischer wrote:
> > Hi Russ,
> >
> > On Thu, Nov 05, 2020 at 05:08:59PM -0800, Russ Weight wrote:
> >> Create the FPGA Security Manager class driver. The security
> >> manager provides
Since the information whether the adaptive behavior is implemented
by DIM or driver custom is useful, so add new attribute to
ETHTOOL_MSG_COALESCE_GET/ETHTOOL_MSG_COALESCE_SET commands to control
the type of adaptive coalescing.
In order to compatible with ioctl code, add a extended coalescing
Add dynamic interrupt moderation support for the HNS3 driver,
and add ethtool support for controlling the type of adaptive.
Signed-off-by: Huazhong Tan
---
drivers/net/ethernet/hisilicon/Kconfig | 1 +
drivers/net/ethernet/hisilicon/hns3/hns3_enet.c| 87 +-
#2 will add DIM for the HNS3 ethernet driver, then there will
be two implemation of IRQ adaptive coalescing (DIM and driver
custiom, so #1 adds a new netlink attribute to the
ETHTOOL_MSG_COALESCE_GET/ETHTOOL_MSG_COALESCE_SET commands
which controls the type of adaptive coalescing.
change log:
V2:
On Thu, Nov 19, 2020 at 10:18:28PM -0800, Jakub Kicinski wrote:
> On Fri, 20 Nov 2020 11:45:12 +0530 Manivannan Sadhasivam wrote:
> > Jakub, can you please provide your ack so that I can take it?
>
> Sure:
>
> Acked-by: Jakub Kicinski
Patch applied to mhi-ath11k-immutable.
Thanks,
Mani
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: 2020年11月17日 15:36
> To: Alice Guo
> Cc: robh...@kernel.org; shawn...@kernel.org; s.ha...@pengutronix.de;
> dl-linux-imx ; Peng Fan ;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
>
发件人: Paul E. McKenney
发送时间: 2020年11月20日 2:12
收件人: Zhang, Qiang
抄送: jiangshan...@gmail.com; rost...@goodmis.org; j...@joshtriplett.org;
r...@vger.kernel.org; linux-kernel@vger.kernel.org
主题: Re: [PATCH] srcu: Remove srcu_cblist_invoking member from sdp
On 2020/11/18 22:01, Liu Song via Linux-f2fs-devel wrote:
From: Liu Song
Since sync_inodes_sb has been used, there is no need to
use writeback_inodes_sb, so remove it.
Signed-off-by: Liu Song
Reviewed-by: Chao Yu
Thanks,
On Fri, 20 Nov 2020 11:45:12 +0530 Manivannan Sadhasivam wrote:
> Jakub, can you please provide your ack so that I can take it?
Sure:
Acked-by: Jakub Kicinski
On Thu, Nov 19, 2020 at 09:10:46PM -0800, Jakub Kicinski wrote:
> On Wed, 18 Nov 2020 10:20:25 -0800 Bhaumik Bhatt wrote:
> > Reset MHI device channels when driver remove is called due to
> > module unload or any crash scenario. This will make sure that
> > MHI channels no longer remain enabled
Commit c604abc3f6e3 ("vmlinux.lds.h: Split ELF_DETAILS from STABS_DEBUG")
after should add a missing ELF_DETAILS, at the same time, the .comment
section has been included in the ELF_DETAILS.
Signed-off-by: Youling Tang
---
arch/m68k/kernel/vmlinux-nommu.lds | 2 +-
On Mon, Nov 16, 2020 at 02:46:22PM -0800, Hemant Kumar wrote:
> Loopback test opens the MHI device file node and writes
> a data buffer to it. MHI UCI kernel space driver copies
> the data and sends it to MHI uplink (Tx) LOOPBACK channel.
> MHI device loops back the same data to MHI downlink (Rx)
Commit eaf937075c9a ("vmlinux.lds.h: Move NOTES into RO_DATA") after
should remove redundant NOTES.
Signed-off-by: Youling Tang
---
arch/m68k/kernel/vmlinux-nommu.lds | 1 -
arch/m68k/kernel/vmlinux-std.lds | 1 -
arch/m68k/kernel/vmlinux-sun3.lds | 1 -
3 files changed, 3 deletions(-)
diff
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-5.10b-rc5-tag
xen: branch for v5.10-rc5
It contains a single fix for avoiding WARN splats when booting a Xen
guest with nosmt.
Thanks.
Juergen
arch/x86/xen/spinlock.c | 12
1 - 100 of 1560 matches
Mail list logo
