Print libpfm4 events with 'perf list pfm' command like others.
When libpfm4 support is not enabled, it'd print nothing.
Also it support glob pattern matching for event name.
$ perf list pfm
List of pre-defined events (to be used in --pfm-events):
ix86arch:
UNHALTED_CORE_CYCLES
It was printed unconditionally even if nothing is printed.
Check if the output list empty when filter is given.
Before:
$ ./perf list duration
List of pre-defined events (to be used in -e):
duration_time [Tool event]
Metric Groups:
After:
$
The sep is already checked being not NULL. The code seems to be a
leftover from some refactoring.
Signed-off-by: Namhyung Kim
diff --git a/tools/perf/builtin-list.c b/tools/perf/builtin-list.c
index 0a7fe4cb..10ab5e40a34f 100644
--- a/tools/perf/builtin-list.c
+++
* Bhaskar Chowdhury [200908 23:08]:
> On 00:56 Wed 09 Sep 2020, Pavel Machek wrote:
> > Would it be possible to create a mailing list on vger.kernel.org?
> > Probably phones@ or phone-devel@? I believe it would be useful to
> > cover hardware-dependend pieces of the phone stack (ofono,
> >
Hi all,
After merging the tty tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/tty/serial/8250/8250_bcm2835aux.c: In function
'bcm2835aux_serial_probe':
drivers/tty/serial/8250/8250_bcm2835aux.c:154:3: warning: ignoring return value
of 'dev_err_probe'
On Tue, Sep 08, 2020 at 05:53:16PM +, Felipe Franciosi wrote:
>
>
> > On Sep 8, 2020, at 3:22 PM, Paolo Bonzini wrote:
> >
> > On 28/08/20 14:21, Matej Genci wrote:
> >> VirtIO 1.0 spec says
> >>The removed and rescan events ... when sent for LUN 0, they MAY
> >>apply to the entire
Hi Pavel,
On 09/09/20 00:22, Pavel Machek wrote:
> Hi!
>
> > This is RFC v2 of Peter's SCHED_DEADLINE server infrastructure
> > implementation [1].
> >
> > SCHED_DEADLINE servers can help fixing starvation issues of low priority
> > tasks (e.g.,
> > SCHED_OTHER) when higher priority tasks
On Tue, 8 Sep 2020 at 21:12, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.64 release.
> There are 129 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
HWCAP name arrays (hwcap_str, compat_hwcap_str, compat_hwcap2_str) that are
scanned for /proc/cpuinfo are detached from their bit definitions making it
vulnerable and difficult to correlate. It is also bit problematic because
during /proc/cpuinfo dump these arrays get traversed sequentially
On Tue, 8 Sep 2020 at 21:05, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.8.8 release.
> There are 186 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
ses on x86_64 with Linux next 20200908 tag
> kernel
> this kernel BUG noticed several times.
>
> metadata:
> git branch: master
> git repo:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git commit: dff9f829e5b0181d4ed9d35aa62d695292399b54
>
Hi all,
After merging the driver-core tree, today's linux-next build (x86_64
allmodconfig) failed like this:
lib/test_firmware.c: In function 'trigger_request_platform_store':
lib/test_firmware.c:517:35: error: 'efi_embedded_fw_list' undeclared (first use
in this function); did you mean
Hi,
here is the new version of the patch based on Peters suggestion
It looks like it works fine. I added the BUG_ON to __crash_kexec,
because it is a precondition, that panic_cpu is set correctly, otherwise
the whole locking logic fails.
The mutex_trylock can still be used, because it is
On Wed, 2020-09-09 at 05:12 +0200, Mike Galbraith wrote:
> On Wed, 2020-09-02 at 17:55 +0200, Sebastian Andrzej Siewior wrote:
> >
> > Known issues
> > - It has been pointed out that due to changes to the printk code the
> >internal buffer representation changed. This is only an issue
-a004-20200908
i386 randconfig-a005-20200908
i386 randconfig-a006-20200908
i386 randconfig-a002-20200908
i386 randconfig-a001-20200908
i386 randconfig-a003-20200908
i386 randconfig-a004-20200907
i386
Fix IOVA reserve failure for memory regions listed in dma-ranges in the
following cases.
- start address of memory region is 0x0.
- end address of a memory region is equal to start address of next memory
region.
Fixes: aadad097cd46f ("iommu/dma: Reserve IOVA for PCIe inaccessible DMA
Hello,
syzbot found the following issue on:
HEAD commit:59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12edb93590
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
On Wed, 9 Sep 2020 00:09:23 +0900
Masami Hiramatsu wrote:
> > > Of course make it lockless then warning is gone.
> > > But even without the lockless patch, this warning can be false-positive
> > > because we prohibit nested kprobe call, right?
> >
> > Yes, because the actual nesting is avoided
On Tue, Sep 8, 2020 at 8:40 PM Arvind Sankar wrote:
>
> On Tue, Sep 08, 2020 at 10:21:32AM -0700, Kees Cook wrote:
> > On Tue, Sep 08, 2020 at 11:39:11AM +0200, Marco Elver wrote:
> > > On Sun, 6 Sep 2020 at 00:23, Arvind Sankar wrote:
> > > >
> > > > String functions can be useful in early
On 08.09.20 22:10, David Hildenbrand wrote:
Let's try to merge system ram resources we add, to minimize the number
of resources in /proc/iomem. We don't care about the boundaries of
individual chunks we added.
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc:
On 08.09.20 22:10, David Hildenbrand wrote:
We soon want to pass flags, e.g., to mark added System RAM resources.
mergeable. Prepare for that.
This patch is based on a similar patch by Oscar Salvador:
https://lkml.kernel.org/r/20190625075227.15193-3-osalva...@suse.de
Acked-by: Wei Liu
Cc:
Fix formating of struct description to avoid warning highlighted
by W=1 compilation.
Signed-off-by: Alain Volmat
---
v2: fixes tag removed
drivers/mailbox/mailbox-sti.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mailbox/mailbox-sti.c
As discussed in [1], KUnit tests have hitherto not had a particularly
consistent naming scheme. This adds documentation outlining how tests
and test suites should be named, including how those names should be
used in Kconfig entries and filenames.
[1]:
There are 438 document files that were licensed under the
free versions of GNU Free Document License.
The free versions are the one that doesn't contain invariant
parts.
The first patch adds the license files. As newer documents
aren't supposed to use them without being dual-licensed
with
SPDX v3.10 gained support for GFDL-1.2 with no invariant sections:
https://spdx.org/licenses/GFDL-1.2-no-invariants-only.html
Let's use it, instead of keeping a license text for this file.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/trace/ring-buffer-design.rst | 26
There are some files under Documentation which uses
deprecated versions of GNU Free Documentation License, on
both versions 1.1 and 1.2.
On all cases, the license is with no Invariant Sections,
Front-Cover Texts or Back-Cover Texts.
Add the text file for them, as we'll start using SPDX
for
On Wed, 2020-09-09 at 05:12 +0200, Mike Galbraith wrote:
> On Wed, 2020-09-02 at 17:55 +0200, Sebastian Andrzej Siewior wrote:
> >
> > Known issues
> > - It has been pointed out that due to changes to the printk code the
> >internal buffer representation changed. This is only an issue
I can't reconcile this hunk:
On Wed, 2020-09-02 at 19:24 -0700, Can Guo wrote:
> @@ -6504,6 +6505,80 @@ static void ufshcd_set_req_abort_skip(struct
> ufs_hba *hba, unsigned long bitmap)
> * issued. To avoid that, first issue UFS_QUERY_TASK to check if the
> command is
> * really issued and
On Sun, 06 Sep 2020 22:58:25 PDT (-0700), Christoph Hellwig wrote:
Stop providing the possibility to override the address space using
set_fs() now that there is no need for that any more.
Signed-off-by: Christoph Hellwig
---
arch/riscv/Kconfig | 1 -
On Sun, 06 Sep 2020 22:58:24 PDT (-0700), Christoph Hellwig wrote:
Implement the non-faulting kernel access helpers directly instead of
abusing the uaccess routines under set_fs(KERNEL_DS).
Signed-off-by: Christoph Hellwig
---
arch/riscv/include/asm/uaccess.h | 20
1 file
On Sun, 06 Sep 2020 22:58:23 PDT (-0700), Christoph Hellwig wrote:
Add new __get_user_nocheck and __put_user_nocheck that switch on the size
and call the actual inline assembly helpers, and move the uaccess enable
/ disable into the actual __get_user and __put_user. This prepares for
natively
On Sun, 06 Sep 2020 22:58:17 PDT (-0700), Christoph Hellwig wrote:
Hi all,
this series converts riscv to the new set_fs less world and is on top of this
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git/log/?h=base.set_fs
The first four patches are general improvements
On Sun, 06 Sep 2020 22:58:22 PDT (-0700), Christoph Hellwig wrote:
This reverts commit adccfb1a805ea84d2db38eb53032533279bdaa97.
Now that the generic uaccess by mempcy code handles unaligned addresses
the generic code can be used for all RISC-V CPUs.
Signed-off-by: Christoph Hellwig
---
While testing livepatch test cases on x86_64 with Linux next 20200908 tag kernel
this kernel BUG noticed several times.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: dff9f829e5b0181d4ed9d35aa62d695292399b54
git
pmd_present() and pmd_trans_huge() are expected to behave in the following
manner during various phases of a given PMD. It is derived from a previous
detailed discussion on this topic [1] and present THP documentation [2].
pmd_present(pmd):
- Returns true if pmd refers to system RAM with a valid
This series enables THP migration on arm64 via ARCH_ENABLE_THP_MIGRATION.
But first this modifies all existing THP helpers like pmd_present() and
pmd_trans_huge() etc per expected generic memory semantics as concluded
from a previous discussion here.
https://lkml.org/lkml/2018/10/9/220
This
In certain page migration situations, a THP page can be migrated without
being split into it's constituent subpages. This saves time required to
split a THP and put it back together when required. But it also saves an
wider address range translation covered by a single TLB entry, reducing
future
I am having difficulty actually reproducing the bug from the supplied C repro
and .config. Perhaps it is some sort of race condition?
On 08-09-20, 22:23, Jassi Brar wrote:
> From the test case Sudeep last shared, the scmi usage on mhu doesn't
> not even hit any bottleneck ... the test "failed" because of the too
> small hardcoded timeout value. Otherwise the current code actually
> shows better numbers.
Its not important on why
Hi Chao,
I have a question about the below flag for decompression.
STEP_DECOMPRESS_NOWQ, /* handle normal cluster data inplace */
According to the comment, you added this for using inplace
decompression but inplace decompression mode is not being activated
now, since we are setting
While booting x86_64 with Linux next 20200908 tag kernel this warning
was noticed.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: dff9f829e5b0181d4ed9d35aa62d695292399b54
git describe: next-20200908
kernel-config
On 08-09-20, 17:38, Amit Kucheria wrote:
> On Tue, Sep 8, 2020 at 5:18 PM Amit Kucheria wrote:
> >
> > On Tue, Sep 8, 2020 at 4:48 PM Viresh Kumar wrote:
> > >
> > > On 08-09-20, 16:41, Manivannan Sadhasivam wrote:
> > > > On 0908, Viresh Kumar wrote:
> > > > > On 08-09-20, 13:27, Manivannan
We already maintain an array of VLANs used by the switch so we can
simply iterate over it to report the occupancy via devlink.
Signed-off-by: Florian Fainelli
---
drivers/net/dsa/b53/b53_common.c | 59 ++--
drivers/net/dsa/b53/b53_priv.h | 1 +
While booting i386 with Linux next 20200908 tag kernel this warning noticed.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: dff9f829e5b0181d4ed9d35aa62d695292399b54
git describe: next-20200908
kernel-config:
http
On Mon, 07 Sep 2020 21:27:08 PDT (-0700), masahi...@kernel.org wrote:
There was a request to preprocess the module linker script like we
do for the vmlinux one. (https://lkml.org/lkml/2020/8/21/512)
The difference between vmlinux.lds and module.lds is that the latter
is needed for external
Hi Chris,
On Tue, Sep 8, 2020 at 11:09 PM Chris Down wrote:
>
> drop_caches by its very nature can be extremely performance intensive -- if
> someone wants to abort after trying too long, they can just send a
> TASK_KILLABLE signal, no? If exiting the loop and returning to usermode
> doesn't
>
On Mon, 2020-08-10 at 15:59 -0700, Joe Perches wrote:
> The logging macros are pretty heavyweight and can be consolidated
> to reduce overall object size.
>
> Joe Perches (2):
> scsi: lpfc: Neaten logging macro #defines
> scsi: lpfc: Add logging functions to reduce object size
>
>
When netvsc_resume() is called, the mlx5 VF NIC has not been resumed yet,
so in the future the host might sliently fail the call netvsc_vf_changed()
-> netvsc_switch_datapath() there, even if the call works now.
Call netvsc_vf_changed() in the NETDEV_CHANGE event handler: at that time
the mlx5 VF
The previous change "hv_netvsc: Switch the data path at the right time
during hibernation" adds the call of netvsc_vf_changed() upon
NETDEV_CHANGE, so it's necessary to avoid the duplicate call and message
when the VF is brought UP or DOWN.
Signed-off-by: Dexuan Cui
---
On Thu, 13 Aug 2020 at 06:50, Jeremy Cline wrote:
>
> Commit d32656373857 ("drm/nouveau/therm/gp100: initial implementation of
> new gp1xx temperature sensor") added support for reading finer-grain
> temperatures, but continued to report temperatures in 1 degree Celsius
> increments via
Let's try to read more information out of more modern cros_ec devices by
using the v2 format first and then fall back to the v1 format. This
gives us more information about things such as DP mode of the typec pins
and the CC state, along with some more things.
Cc: Gwendal Grignou
Cc: Prashant
On 9/8/20 12:58 PM, Roman Gushchin wrote:
On Tue, Sep 08, 2020 at 11:09:25AM -0400, Zi Yan wrote:
On 7 Sep 2020, at 3:20, Michal Hocko wrote:
On Fri 04-09-20 14:10:45, Roman Gushchin wrote:
On Fri, Sep 04, 2020 at 09:42:07AM +0200, Michal Hocko wrote:
[...]
Something like
Some integrated OHCI controller hubs do not expose all ports of the hub
to pins on the SoC. In some cases the unconnected ports generate
spurious over-current events. For example the Broadcom 56060/Ranger 2 SoC
contains a nominally 3 port hub but only the first port is wired.
Default behaviour
> -Original Message-
> From: Palmer Dabbelt
> Sent: 09 September 2020 08:42
> To: Christoph Hellwig ; dkang...@cadence.com
> Cc: Yash Shah ; robh...@kernel.org; Paul
> Walmsley ( Sifive) ; b...@alien8.de;
> mche...@kernel.org; tony.l...@intel.com; devicet...@vger.kernel.org;
>
On Tue, Sep 8, 2020 at 8:19 PM Matthew Wilcox wrote:
>
> On Tue, Sep 08, 2020 at 04:18:29PM +0300, Amir Goldstein wrote:
> > On Tue, Sep 8, 2020 at 3:53 PM Xiaoming Ni wrote:
> > > For example, in fs/coredump.c, do_coredump() calls filp_open() to
> > > generate core files.
> > > In this
On Tue, 2020-09-08 at 14:21 -0600, Rob Herring wrote:
> On Mon, Sep 07, 2020 at 08:08:50PM +0800, Jianjun Wang wrote:
> > Add YAML schemas documentation for Gen3 PCIe controller on
> > MediaTek SoCs.
>
> dt-bindings: PCI: mediatek: ... for the subject.
>
> >
> > Acked-by: Ryder Lee
> >
On Wed, Sep 9, 2020 at 11:16 AM Ritesh Harjani wrote:
>
> If we hit the UINT_MAX limit of bio->bi_iter.bi_size and so we are anyway
> not merging this page in this bio, then it make sense to make same_page
> also as false before returning.
>
> Without this patch, we hit below WARNING in iomap.
>
On 09/09, Chao Yu wrote:
> On 2020/9/9 10:36, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > Made f2fs_vmap() wrapper to handle vm_map_ram() stuff.
> >
> > Signed-off-by: Daeho Jeong
>
> LGTM,
>
> I think it should be merged into original patch. :)
>
> Maybe Jaeguek could help to do that.
From: Alex Elder
Date: Tue, 8 Sep 2020 19:21:23 -0500
> We take a single IPA clock reference to keep the clock running
> until we get a system suspend operation. When a system suspend
> request arrives, we drop that reference, and if that's the last
> reference (likely) we'll proceed with
On Tue, Sep 8, 2020 at 4:15 AM Arnd Bergmann wrote:
>
> Picking up the old thread again after and getting pinged by multiple
> colleagues about it (thanks!) reading through the history.
>
> On Fri, Jun 12, 2020 at 7:29 AM Viresh Kumar wrote:
> >
> > On 11-06-20, 19:34, Jassi Brar wrote:
> > > In
On 2020/9/9 10:36, Daeho Jeong wrote:
From: Daeho Jeong
Made f2fs_vmap() wrapper to handle vm_map_ram() stuff.
Signed-off-by: Daeho Jeong
LGTM,
I think it should be merged into original patch. :)
Maybe Jaeguek could help to do that.
Thanks,
---
fs/f2fs/compress.c | 42
t; accounted separately.
>
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-next-20200908
Pulled, thanks David.
From: Christophe JAILLET
Date: Tue, 8 Sep 2020 22:27:47 +0200
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script below and has been
> hand modified to replace GFP_ with a correct flag.
> It has been compile tested.
>
>
From: Christophe JAILLET
Date: Tue, 8 Sep 2020 22:08:39 +0200
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script below and has been
> hand modified to replace GFP_ with a correct flag.
> It has been compile tested.
>
>
On Tue, 2020-09-08 at 15:04 -0500, Bjorn Helgaas wrote:
> On Mon, Sep 07, 2020 at 08:08:50PM +0800, Jianjun Wang wrote:
> > Add YAML schemas documentation for Gen3 PCIe controller on
> > MediaTek SoCs.
>
> Please mention "mediatek" in the subject line so "git log --oneline"
> is more useful.
>
>
If we hit the UINT_MAX limit of bio->bi_iter.bi_size and so we are anyway
not merging this page in this bio, then it make sense to make same_page
also as false before returning.
Without this patch, we hit below WARNING in iomap.
This mostly happens with very large memory system and / or after
On Tue, Sep 08, 2020 at 09:53:11PM +0200, Pavel Machek wrote:
> Hi!
>
> > On machines with much memory (> 2 TByte) and log_mtts_per_seg == 0, a
> > max_order of 31 will be passed to mlx_buddy_init(), which results in
> > s = BITS_TO_LONGS(1 << 31) becoming a negative value, leading to
> >
On Wed, 2020-09-02 at 17:55 +0200, Sebastian Andrzej Siewior wrote:
>
> Known issues
> - It has been pointed out that due to changes to the printk code the
>internal buffer representation changed. This is only an issue if tools
>like `crash' are used to extract the printk
From: Jakub Kicinski
Date: Tue, 8 Sep 2020 10:36:24 -0700
> We run into a unused variable warning in bridge code when
> variable is only used inside the condition of
> rcu_dereference_protected().
>
> #define mlock_dereference(X, br) \
> rcu_dereference_protected(X,
On Sun, 06 Sep 2020 23:11:26 PDT (-0700), Christoph Hellwig wrote:
On Mon, Sep 07, 2020 at 11:17:58AM +0530, Yash Shah wrote:
Add a driver to manage the Cadence DDR controller present on SiFive SoCs
At present the driver manages the EDAC feature of the DDR controller.
Additional features may be
On Tue, 2020-09-08 at 13:50 -0600, Rob Herring wrote:
> On Mon, 07 Sep 2020 20:08:50 +0800, Jianjun Wang wrote:
> > Add YAML schemas documentation for Gen3 PCIe controller on
> > MediaTek SoCs.
> >
> > Acked-by: Ryder Lee
> > Signed-off-by: Jianjun Wang
> > ---
> >
From: Brian Vazquez
Date: Tue, 8 Sep 2020 09:18:12 -0700
> If CONFIG_IPV6=m, the IPV6 functions won't be found by the linker:
>
> ld: net/core/fib_rules.o: in function `fib_rules_lookup':
> fib_rules.c:(.text+0x606): undefined reference to `fib6_rule_match'
> ld: fib_rules.c:(.text+0x611):
Any comments? guys!
On Tue, 1 Sep 2020 at 19:52, wrote:
>
> From: Yulei Zhang
>
> Currently in KVM memory virtulization we relay on mmu_lock to
> synchronize the memory mapping update, which make vCPUs work
> in serialize mode and slow down the execution, especially after
> migration to do
From: Wang Hai
Date: Tue, 8 Sep 2020 22:01:58 +0800
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c:4238: warning: Excess
> function parameter 'netdev' description in 'bnx2x_setup_tc'
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c:4238:
From: Wang Hai
Date: Tue, 8 Sep 2020 22:03:33 +0800
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/wimax/i2400m/control.c:709: warning: Excess function parameter
> 'msg_skb' description in 'i2400m_msg_to_dev'
>
> This parameter is not in use. Remove it.
>
> Reported-by:
On 8/24/2020 11:35 AM, Florian Fainelli wrote:
Changes in v2:
- included missing preliminary patch to define the SB barrier instruction
Will Deacon (2):
arm64: Add support for SB barrier and patch in over DSB; ISB sequences
arm64: entry: Place an SB sequence following an ERET
From: Wang Hai
Date: Tue, 8 Sep 2020 22:05:43 +0800
> Fixes the following W=1 kernel build warning(s):
>
> net/netlabel/netlabel_calipso.c:438: warning: Excess function parameter
> 'audit_secid' description in 'calipso_doi_remove'
> net/netlabel/netlabel_calipso.c:605: warning: Excess function
From: Wang Hai
Date: Tue, 8 Sep 2020 21:59:15 +0800
> Fixes the following W=1 kernel build warning(s):
>
> net/ipv4/cipso_ipv4.c:510: warning: Excess function parameter 'audit_secid'
> description in 'cipso_v4_doi_remove'
>
> Reported-by: Hulk Robot
> Signed-off-by: Wang Hai
Applied.
mptcp_pm_nl_get_local_id may be called in interrupt context, so we need to
use GFP_ATOMIC flag to allocate memory to avoid sleeping in atomic context.
[ 280.209809] BUG: sleeping function called from invalid context at
mm/slab.h:498
[ 280.209812] in_atomic(): 1, irqs_disabled(): 0, non_block:
Hi Qian,
On Thu, 3 Sep 2020 08:38:25 -0400 Qian Cai wrote:
>
> On Wed, Sep 02, 2020 at 08:52:24AM -0400, Qian Cai wrote:
> > On Thu, Aug 06, 2020 at 05:43:26PM +, Uriel Guajardo wrote:
> > > Integrates UBSAN into the KUnit testing framework. It fails KUnit tests
> > > whenever it reports
On Thu, 2020-09-03 at 07:40 +0800, Suman Anna wrote:
> Hi Crystal,
>
> On 8/16/20 10:03 PM, Crystal Guo wrote:
> > Introduce ti_syscon_reset() to integrate assert and deassert together.
> > If some modules need do serialized assert and deassert operations
> > to reset itself, reset_control_reset
On Tue, Sep 08, 2020 at 03:00:59PM -0500, Eddie James wrote:
> Mask the IRQ status to only the bits that the driver checks. This
> prevents excessive driver warnings when operating in slave mode
> when additional bits are set that the driver doesn't handle.
>
> Signed-off-by: Eddie James
From: Wanpeng Li
Moving the call to svm_exit_handlers_fastpath() after svm_complete_interrupts()
since svm_complete_interrupts() consumes rip and reenable the function
handle_fastpath_set_msr_irqoff() call in svm_exit_handlers_fastpath().
Suggested-by: Sean Christopherson
Cc: Paul K.
From: Wanpeng Li
Moving svm_complete_interrupts() into svm_vcpu_run() which can align VMX
and SVM with respect to completing interrupts.
Suggested-by: Sean Christopherson
Cc: Paul K.
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/svm/svm.c | 4 ++--
1 file changed, 2 insertions(+), 2
From: Wanpeng Li
Analysis from Sean:
| svm->next_rip is reset in svm_vcpu_run() only after calling
| svm_exit_handlers_fastpath(), which will cause SVM's
| skip_emulated_instruction() to write a stale RIP.
Let's get rid of handle_fastpath_set_msr_irqoff() in
svm_exit_handlers_fastpath()
From: Wang Sheng Long
When data is transmitted between two serial ports,
the phenomenon of data loss often occurs. The two kinds
of flow control commonly used in serial communication
are hardware flow control and software flow control.
In serial communication, If you only use RX/TX/GND Pins,
From: Wanpeng Li
Moving svm_complete_interrupts() into svm_vcpu_run() which can align VMX
and SVM with respect to completing interrupts.
Suggested-by: Sean Christopherson
Cc: Paul K.
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/svm/svm.c | 4 ++--
1 file changed, 2 insertions(+), 2
From: Wanpeng Li
Moving the call to svm_exit_handlers_fastpath() after svm_complete_interrupts()
since svm_complete_interrupts() consumes rip and reenable the function
handle_fastpath_set_msr_irqoff() call in svm_exit_handlers_fastpath().
Suggested-by: Sean Christopherson
Cc: Paul K.
On Wed, Sep 09, 2020 at 01:53:51AM +0800, Mathieu Poirier wrote:
> Hi Tingwei,
>
> Apologies for the untimely response to this set, I am hoping to get to
> it in the next two weeks.
>
It's fine, Mathieu. Please let me know your comments once you have time.
I'm targeting to get these set merged
From: Wanpeng Li
Analysis from Sean:
| svm->next_rip is reset in svm_vcpu_run() only after calling
| svm_exit_handlers_fastpath(), which will cause SVM's
| skip_emulated_instruction() to write a stale RIP.
Let's get rid of handle_fastpath_set_msr_irqoff() in
svm_exit_handlers_fastpath()
From: Wei Xu
Date: Tue, 8 Sep 2020 11:49:25 +0800
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/smsc/smsc911x.c: In function ‘smsc911x_rx_fastforward’:
> drivers/net/ethernet/smsc/smsc911x.c:1199:16: warning: variable ‘temp’ set
> but not used
Stanley,
> This series fix some defects and introduce host reset mechanism in
> MediaTek UFS platforms. Please consider this patch series for kernel
> v5.10.
Applied to the 5.10 SCSI staging tree. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
From: Jakub Kicinski
Date: Tue, 8 Sep 2020 12:05:38 -0700
> On Tue, 8 Sep 2020 10:59:47 +0800 Huazhong Tan wrote:
>> There are some misc updates for the HNS3 ethernet driver.
>>
>> #1 narrows two local variable range in hclgevf_reset_prepare_wait().
>> #2 adds reset failure check in periodic
On Thu, Aug 27, 2020 at 09:40:22PM -0400, Daniel Jordan wrote:
> I went back to your v1 post to see what motivated you originally, and you had
> some results from aim9 but nothing about where this reared its head in the
> first place. How did you discover the bottleneck? I'm just curious about
Hi,
On Tue, 2020-09-08 at 14:49 -0600, Rob Herring wrote:
> On Fri, Aug 21, 2020 at 06:44:36PM +0800, Hsin-Hsiung Wang wrote:
> > This adds documentation for the SPMI controller found on Mediatek SoCs.
> >
> > Signed-off-by: Hsin-Hsiung Wang
> > ---
> >
On 9/8/20 3:09 PM, Suman Anna wrote:
Hi Santosh,
On 8/31/20 1:34 PM, santosh.shilim...@oracle.com wrote:
On 8/29/20 11:41 AM, Grygorii Strashko wrote:
Hi Santosh,
I've rebased on top of linux-next and identified merge conflict of patch 3
with commit 6da45875fa17 ("arm64: dts: k3-am65:
Ming,
Got it, will try and give you feedback. Thanks,
-Original Message-
From: Ming Lei
Sent: Wednesday, September 9, 2020 10:39 AM
To: Zhao, Haifeng
Cc: Christoph Hellwig ; ax...@kernel.dk;
bhelg...@google.com; linux-bl...@vger.kernel.org; linux-kernel@vger.kernel.org;
On Tue, 2020-09-08 at 17:06 +0200, Sebastian Andrzej Siewior wrote:
>
> This should cure it:
It did.
-Mike
Hello Haifeng,
On Wed, Sep 09, 2020 at 02:11:20AM +, Zhao, Haifeng wrote:
> Ming, Christoph,
> Could you point out the patch aimed to fix this issue ? I would like to
> try it. This issue blocked my other PCI patch developing and verification
> work,
> I am not a BLOCK/NVMe expert,
Hi all,
After merging the pci tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: modpost: "dw_pcie_link_set_max_speed" [vmlinux] is a static
EXPORT_SYMBOL_GPL
Introduced by commit
3af45d34d30c ("PCI: dwc: Centralize link gen setting")
--
Cheers,
1 - 100 of 1840 matches
Mail list logo
