On 3/22/21 7:07 AM, Michal Hocko wrote:
> On Fri 19-03-21 15:42:03, Mike Kravetz wrote:
>> The routine set_max_huge_pages reduces the number of hugetlb_pages,
>> by calling free_pool_huge_page in a loop. It does this as long as
>> persistent_huge_pages() is above a calculated min_count value.
>>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 4bf07f6562a01a488877e05267808da7147f44a5
Gitweb:
https://git.kernel.org/tip/4bf07f6562a01a488877e05267808da7147f44a5
Author:Ingo Molnar
AuthorDate:Mon, 22 Mar 2021 22:39:03 +01:00
Thanks.
Acked-by: Khalil Blaiech
> -Original Message-
> From: Andy Shevchenko
> Sent: Monday, March 22, 2021 12:54 PM
> To: Wolfram Sang ; Khalil Blaiech ;
> Loic Poulain ; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; linux-arm-...@vger.kernel.org
> Cc: Robert Foss ; Andy
On Mon, Mar 22, 2021 at 11:36:19PM +0100, Uladzislau Rezki wrote:
> On Mon, Mar 22, 2021 at 07:38:20PM +, Matthew Wilcox (Oracle) wrote:
> > If we're trying to allocate 4MB of memory, the table will be 8KiB in size
> > (1024 pointers * 8 bytes per pointer), which can usually be satisfied
> >
Hi Paul,
Was working on automation to make it a bit more straightforward to fix
typos within comments (which we tend to reintroduce during
development), and here are the ones it found in the RCU code.
Thanks,
Ingo
=>
From: Ingo Molnar
Date: Mon, 22 Mar 2021 23:57:26 +0100
On 22/03/2021 21:24, Mathieu Poirier wrote:
On Fri, Mar 19, 2021 at 11:55:10AM +, Mike Leach wrote:
HI Suzuki,
On Fri, 19 Mar 2021 at 10:30, Suzuki K Poulose wrote:
Hi Mike
On 8 Mar 2021, at 17:26, Mike Leach wrote:
Hi Suzuki,
On Thu, 25 Feb 2021 at 19:36, Suzuki K Poulose wrote:
On Mon, Mar 22, 2021 at 04:49:04PM -0400, Richard Guy Briggs wrote:
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index c1eb5cdb3033..42ba44890523 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
[...]
> @@ -8006,12 +7938,47 @@
> The solution is to create a user space tool inside the
> drivers/net/ipa directory that will link with the kernel
> source files and will perform all the basic one-time checks
> I want to make.
Hi Alex
Have you found any other driver doing this? Where do they keep there
code?
Could this be a
The test creates two processes where one traces another one. The tracee
executes a system call, the tracer traps it, changes orig_x0, triggers a
signal and checks that the syscall is restarted with the setted
argument.
Test output:
$ ./ptrace_restart_syscall_test
1..3
ok 1 orig_x0: 0x3
ok 2
In system calls, x7 is used to indicate whether a tracee has been
stopped on syscall-enter or syscall-exit and the origin value of x7 is
saved in orig_x7.
Test output:
$ ./ptrace_syscall_test
1..4
ok 1 x7: 0
ok 2 x7: 1
ok 3 x7: 686920776f726c64
ok 4 The child exited with code 0.
# Totals:
We have some ABI weirdness in the way that we handle syscall exit stops
because we indicate whether or not the stop has been signalled from
syscall entry or syscall exit by clobbering a general purpose register
x7 in the tracee and restoring its old value after the stop.
This behavior was
orig_x0 is recorded at the start of the syscall entry and then it is
used for resetting the argument back to its original value during
syscall restarts.
If orig_x0 isn't available from user-space, this makes it tricky to
manage arguments of restarted system calls.
Cc: Keno Fischer
Here are two known problems with registers when a tracee is stopped in
syscall traps.
The first problem is about the x7 register that is used to indicate
whether or not the stop has been signalled from syscall entry or syscall
exit. This means that:
- Any writes by the tracer to this register
On Mon, Mar 22, 2021 at 03:49:16PM +0100, Miklos Szeredi wrote:
> Remove vfs_ioc_setflags_prepare(), vfs_ioc_fssetxattr_check() and
> simple_fill_fsxattr(), which are no longer used.
>
> Signed-off-by: Miklos Szeredi
Woo hoo, so much boilerplate goes away!
Reviewed-by: Darrick J. Wong
--D
>
On Mon, Mar 22, 2021 at 03:49:08PM +0100, Miklos Szeredi wrote:
> Use the miscattr API to let the VFS handle locking, permission checking and
> conversion.
>
> Signed-off-by: Miklos Szeredi
> Cc: Darrick J. Wong
> ---
> fs/xfs/libxfs/xfs_fs.h | 4 -
> fs/xfs/xfs_ioctl.c | 316
On Mon, Mar 22, 2021 at 11:09 PM Martin Sebor wrote:
> On 3/22/21 2:29 PM, Ingo Molnar wrote:
> > * Arnd Bergmann wrote:
> >
> > I.e. the real workaround might be to turn off the
> > -Wstringop-overread-warning,
> > until GCC-11 gets fixed?
>
> In GCC 10 -Wstringop-overread is a subset of
On 22/03/2021 17:28, Rob Herring wrote:
On Mon, Mar 22, 2021 at 10:53 AM Suzuki K Poulose
wrote:
Hi Rob
On 06/03/2021 21:06, Rob Herring wrote:
On Thu, Feb 25, 2021 at 07:35:39PM +, Suzuki K Poulose wrote:
Document the device tree bindings for Embedded Trace Extensions.
ETE can be
> -Original Message-
> From: Ulf Hansson
> Sent: Monday, March 22, 2021 5:51 AM
> To: Liming Sun
> Cc: Adrian Hunter ; Khalil Blaiech
> ; linux-mmc ; Linux
> Kernel Mailing List
> Subject: Re: [PATCH v2] mmc: sdhci-of-dwcmshc: add ACPI support for
> BlueField-3 SoC
>
> On Fri, 19 Mar
This commit adds ACPI support in the sdhci-of-dwcmshc driver for
BlueField-3 SoC. It has changes to only use the clock hierarchy
for Deviec Tree since the clk is not supported by ACPI. Instead,
ACPI can define 'clock-frequency' which is parsed by existing
sdhci_get_property(). This clock value
Fix ~59 single-word typos in the tracing code comments.
Signed-off-by: Ingo Molnar
Cc: Steven Rostedt
Cc: linux-kernel@vger.kernel.org
---
arch/microblaze/include/asm/ftrace.h | 2 +-
arch/nds32/kernel/ftrace.c | 2 +-
arch/powerpc/include/asm/ftrace.h| 4 ++--
On 3/22/21 2:06 PM, Bhaskar Chowdhury wrote:
>
> s/defintion/definition/ .two different places.
>
> Signed-off-by: Bhaskar Chowdhury
Acked-by: Randy Dunlap
> ---
> drivers/gpu/drm/amd/include/atombios.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Mon, Mar 22, 2021 at 09:05:43AM -0700, Sean Christopherson wrote:
> On Sun, Mar 21, 2021, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > PKey faults may now happen on kernel mappings if the feature is enabled.
> > Remove the warning in the fault path if PKS is enabled.
>
> When/why
On 3/22/21 1:58 PM, Bhaskar Chowdhury wrote:
>
> s/defintions/definitions/ two different places.
>
> Signed-off-by: Bhaskar Chowdhury
Acked-by: Randy Dunlap
> ---
> drivers/scsi/bfa/bfa_fc.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Tue, Mar 23, 2021 at 11:06:43AM +1300, Kai Huang wrote:
> This path is called by host SGX driver only, so yes this leaking is done by
> host enclaves only.
Yes, so I was told.
> This patch is purpose is to break EREMOVE out of sgx_free_epc_page() so
> virtual
> EPC code can use
From: Youquan Song
Skylake has a mode where the system administrator can use a BIOS setup
option to request that the memory controller report uncorrected errors
found by the patrol scrubber as corrected. This results in them being
signalled using CMCI, which is less disruptive than a machine
On Mon, Mar 22, 2021 at 07:38:20PM +, Matthew Wilcox (Oracle) wrote:
> If we're trying to allocate 4MB of memory, the table will be 8KiB in size
> (1024 pointers * 8 bytes per pointer), which can usually be satisfied
> by a kmalloc (which is significantly faster). Instead of changing this
>
On Mon, Mar 22, 2021 at 03:48:59PM +0100, Miklos Szeredi wrote:
> There's a substantial amount of boilerplate in filesystems handling
> FS_IOC_[GS]ETFLAGS/ FS_IOC_FS[GS]ETXATTR ioctls.
>
> Also due to userspace buffers being involved in the ioctl API this is
> difficult to stack, as shown by
From: Arnd Bergmann
gcc warns about a couple of instances in which a sanity check
exists but the author wasn't sure how to react to it failing,
which makes it look like a possible bug:
fs/hfsplus/inode.c: In function 'hfsplus_cat_read_inode':
fs/hfsplus/inode.c:503:37: error: suggest braces
Am 2021-03-22 19:42, schrieb Pratyush Yadav:
On 22/03/21 04:32PM, Michael Walle wrote:
Am 2021-03-22 15:21, schrieb Pratyush Yadav:
> On 18/03/21 10:24AM, Michael Walle wrote:
> > +
> > + sfdp->num_dwords = DIV_ROUND_UP(sfdp_size, sizeof(*sfdp->dwords));
>
> The SFDP spec says that
Hi Marc,
On 25/02/2021 19:35, Suzuki K Poulose wrote:
Disable guest access to the Trace Filter control registers.
We do not advertise the Trace filter feature to the guest
(ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest
can still access the TRFCR_EL1 unless we trap it.
This
>
> Btw, I probably have seen this and forgotten again so pls remind me,
> is the amount of pages available for SGX use static and limited by,
> I believe BIOS, or can a leakage in EPC pages cause system memory
> shortage?
>
Yes EPC size is fixed and configured in BIOS. Leaking EPC pages may
On Mon, Mar 22, 2021 at 04:04:01PM +0800, DENG Qingfang wrote:
> On Fri, Mar 19, 2021 at 6:49 PM Vladimir Oltean wrote:
> > Why would you even want to look at the source net device for forwarding?
> > I'd say that if dp->bridge_dev is NULL in the xmit function, you certainly
> > want to bypass
On Thu, Mar 18, 2021 at 4:40 AM Lee Jones wrote:
>
> 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.
>
> v2:
> - Provided some descriptions to exported functions
>
> Lee Jones (10):
> of:
On 3/22/21 12:18 AM, Christoph Hellwig wrote:
I've been running the reproducer on a KASAN enable VM for about
15 minutes now, but haven't been able to reproduce it.
Is there a way to inject this proposed fix into the syzbot queue?
diff --git a/block/partitions/core.c b/block/partitions/core.c
Will, Catalin,
On 25/02/2021 19:35, Suzuki K Poulose wrote:
Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest,
when the trace register accesses are trapped (CPTR_EL2.TTA == 1).
So, the guest will get an undefined instruction, if trusts the
ID registers and access one of the trace
On Mon, Mar 22, 2021 at 02:13:40PM +0900, Namjae Jeon wrote:
> +#define RESPONSE_BUF(w) ((void *)(w)->response_buf)
> +#define REQUEST_BUF(w) ((void *)(w)->request_buf)
Why do you do this obfuscation?
> +#define RESPONSE_BUF_NEXT(w) \
> + ((void
Hi Mark,
On Sun, Mar 21, 2021, at 19:35, Mark Kettenis wrote:
>
> Guess we do need to understand a little bit better how the USB DART
> actually works. My hypothesis (based on our discussion on #asahi) is
> that the XHCI host controller and the peripheral controller of the
> DWC3 block use
On Mon, Mar 22, 2021 at 08:41:56PM +, Luis Chamberlain wrote:
> On Mon, Mar 22, 2021 at 09:37:17AM -0700, Minchan Kim wrote:
> > On Fri, Mar 19, 2021 at 07:09:24PM +, Luis Chamberlain wrote:
> > > Indeed one issue is a consequence of the other but a bit better
> > > description can be put
UFFD_FEATURE_THREAD_ID is supported since Linux 4.14.
Signed-off-by: Peter Xu
---
man2/userfaultfd.2 | 13 +
1 file changed, 13 insertions(+)
diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
index e7dc9f813..555e37409 100644
--- a/man2/userfaultfd.2
+++ b/man2/userfaultfd.2
@@
Write-protect mode is supported starting from Linux 5.7.
Signed-off-by: Peter Xu
---
man2/userfaultfd.2 | 104 -
1 file changed, 102 insertions(+), 2 deletions(-)
diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
index 555e37409..8ad4a71b5 100644
Userfaultfd write-protect mode is supported starting from Linux 5.7.
Signed-off-by: Peter Xu
---
man2/ioctl_userfaultfd.2 | 84 ++--
1 file changed, 81 insertions(+), 3 deletions(-)
diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
index
UFFD_FEATURE_THREAD_ID is supported in Linux 4.14.
Signed-off-by: Peter Xu
---
man2/ioctl_userfaultfd.2 | 5 +
1 file changed, 5 insertions(+)
diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
index 47ae5f473..d4a8375b8 100644
--- a/man2/ioctl_userfaultfd.2
+++
v4:
- Fixed a few "subordinate clauses" (SC) cases [Alex]
- Reword in ioctl_userfaultfd.2 to use bold font for the two modes referenced,
so as to be clear on what is "both" referring to [Alex]
v3:
- Don't use "Currently", instead add "(since x.y)" mark where proper [Alex]
- Always use semantic
On 3/22/21 2:29 PM, Ingo Molnar wrote:
* Arnd Bergmann wrote:
From: Arnd Bergmann
gcc-11 warns about using string operations on pointers that are
defined at compile time as offsets from a NULL pointer. Unfortunately
that also happens on the result of fix_to_virt(), which is a
compile-time
On Sun, 21 Mar 2021 16:38:59 +0100, "Michael Kerrisk (man-pages)"
wrote:
> On 3/9/21 8:53 PM, Stephen Kitt wrote:
> > On Thu, 28 Jan 2021 21:50:23 +0100, "Michael Kerrisk (man-pages)"
> > wrote:
> >> Thanks for your patch revision. I've merged it, and have
> >> done some light editing, but I
On Mon, 22 Mar 2021 22:06:45 +0100 Borislav Petkov wrote:
> On Mon, Mar 22, 2021 at 12:37:02PM -0700, Sean Christopherson wrote:
> > Yes. Note, it's still true if you strike out the "too", KVM support is
> > completely
> > orthogonal to this code. The purpose of this patch is to separate out
On Fri, Mar 19, 2021 at 11:37:20PM +0100, Alejandro Colomar (man-pages) wrote:
> Hi Peter,
Hi, Alex,
> > +generate another write-protect userfault message.
> > +This is only used in conjunction with write-protect mode when both missing
> > and
>
> "when both missing"
>
> both what?
I
On 3/22/21 1:21 PM, Julia Lawall wrote:
> From: kernel test robot
>
> Function "for_each_child_of_node" should have of_node_put() before goto.
>
> Generated by: scripts/coccinelle/iterators/for_each_child.cocci
>
> Fixes: 82c2d81361ec ("coccinelle: iterators: Add for_each_child.cocci script")
On Mon, 22 Mar 2021 22:49:58 +0100
Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> With 'make W=1', gcc warns about casts between incompatible function
> types:
>
> kernel/trace/ftrace.c:128:31: error: cast between incompatible function types
> from 'void (*)(long unsigned int, long unsigned
Transparent huge pages are supported for read-only non-shmem filesystems,
but are only used for vmas with VM_DENYWRITE. This condition ensures that
file THPs are protected from writes while an application is running
(ETXTBSY). Any existing file THPs are then dropped from the page cache
when a
On 2021-03-22, Petr Mladek wrote:
> On Mon 2021-03-22 12:16:15, John Ogness wrote:
>> On 2021-03-21, Sergey Senozhatsky wrote:
>> >> @@ -369,7 +70,10 @@ __printf(1, 0) int vprintk_func(const char *fmt,
>> >> va_list args)
>> >>* Use the main logbuf even in NMI. But avoid calling console
>>
On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
> I agree to the last point and yeah, maybe regressions are the more
> important problem we should work on – at least from the perspective of
> kernel development. But from the users perspective (and
> reporting-issues.rst is
allmodconfig
powerpc allnoconfig
i386 randconfig-a004-20210322
i386 randconfig-a003-20210322
i386 randconfig-a001-20210322
i386 randconfig-a002-20210322
i386 randconfig-a006-20210322
i386
On Mon, Mar 22, 2021 at 01:28:54PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.263 release.
> There are 14 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
On Mon, Mar 22, 2021 at 01:28:50PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.263 release.
> There are 25 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
On Mon, Mar 22, 2021 at 01:28:41PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.227 release.
> There are 43 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
On Mon, Mar 22, 2021 at 01:27:48PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.108 release.
> There are 60 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
On Mon, Mar 22, 2021 at 01:28:14PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.183 release.
> There are 43 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
From: Arnd Bergmann
gcc-10 correctly points out a memcpy beyond the end of the structure
it gets copied into:
fs/omfs/file.c: In function 'omfs_grow_extent':
cc1: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
In file included from fs/omfs/omfs.h:8,
On Mon, Mar 22, 2021 at 04:19:10PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.26 release.
> There are 156 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
From: Arnd Bergmann
gcc -Wextra wants type modifiers in the normal order:
kernel/bpf/bpf_lsm.c:70:1: error: 'static' is not at beginning of declaration
[-Werror=old-style-declaration]
70 | const static struct bpf_func_proto bpf_bprm_opts_set_proto = {
| ^
From: Arnd Bergmann
The correct order is 'static const', not 'const static', as seen from
make W=1:
drivers/net/wireless/intel/iwlwifi/mvm/rfi.c:14:1: error: 'static' is not at
beginning of declaration [-Werror=old-style-declaration]
Fixes: 21254908cbe9 ("iwlwifi: mvm: add RFI-M support")
From: Arnd Bergmann
With extra warnings enabled, gcc complains about a slightly odd
prototype:
drivers/clk/tegra/clk-dfll.c:1380:1: error: 'inline' is not at beginning of
declaration [-Werror=old-style-declaration]
1380 | static void inline dfll_debug_init(struct tegra_dfll *td) { }
Move the
On Mon, Mar 22, 2021 at 01:26:23PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.11.9 release.
> There are 120 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
From: Arnd Bergmann
With 'make W=1', gcc warns about casts between incompatible function
types:
kernel/trace/ftrace.c:128:31: error: cast between incompatible function types
from 'void (*)(long unsigned int, long unsigned int)' to 'void (*)(long
unsigned int, long unsigned int, struct
From: Arnd Bergmann
Building with 'make W=1', gcc points out that casting between
incompatible function types can be dangerous:
arch/x86/math-emu/fpu_trig.c:1638:60: error: cast between incompatible function
types from ‘int (*)(FPU_REG *, u_char)’ {aka ‘int (*)(struct fpu__reg *,
unsigned
On 21-03-13 06:28:17, Adam Ford wrote:
> Most if not all i.MX SoC's call a function which enables all UARTS.
> This is a problem for users who need to re-parent the clock source,
> because any attempt to change the parent results in an busy error
> due to the fact that the clocks have been enabled
From: Arnd Bergmann
The __static_call_return0() function is declared to return a 'long',
while it aliases a couple of functions that all return 'int'. When
building with 'make W=1', gcc warns about this:
kernel/sched/core.c:5420:37: error: cast between incompatible function types
from 'long
Hi,
On Mon, Mar 22, 2021 at 10:25:49AM -0600, Rob Herring wrote:
> On Wed, Mar 17, 2021 at 7:49 AM Sebastian Reichel wrote:
> > Sebastian Reichel (38):
> > ARM: dts: motorola-cpcap-mapphone: Prepare for dtbs_check parsing
> > dt-bindings: power: supply: cpcap-battery: Convert to DT schema
From: "Steven Rostedt (VMware)"
The tab stop for Perl files is by default (at least in emacs) to be 4
spaces, where a tab is used for all 8 spaces. Add a local variable comment
to make vim do the same by default, and this will help keep the file
consistent in the future when others edit it via
Talking with John Hawley about how vim and emacs deal with Perl files
with respect to tabs and spaces, I found that some of my Perl code in
the kernel had inconsistent spacing. The way emacs handles Perl by default
is to use 4 spaces per indent, but make all 8 spaces into a single tab.
Vim does
From: "Steven Rostedt (VMware)"
As Perl code tends to have 4 space indentation, but uses tabs for every 8
spaces, make that consistent in the streamline_config.pl code.
Replace all 8 spaces with a single tab.
Signed-off-by: Steven Rostedt (VMware)
---
scripts/kconfig/streamline_config.pl | 78
On Mon, Mar 22, 2021 at 05:36:44PM -0400, Steven Rostedt wrote:
$@#@#$%%%
Bah! There was another typo in the email list!
Take 3
-- Steve
On Mon, Mar 22, 2021 at 9:29 PM Ingo Molnar wrote:
> * Arnd Bergmann wrote:
> > From: Arnd Bergmann
> This is indeed rather ugly - and the other patch that removes a debug
> check seems counterproductive as well.
>
> Do we know how many genuine bugs -Wstringop-overread-warning has
> caught or
Manish,
On Mon, Mar 22 2021 at 10:15, Manish Varma wrote:
> On Thu, Mar 18, 2021 at 6:04 AM Thomas Gleixner wrote:
>> > +static atomic_t instance_count = ATOMIC_INIT(0);
>>
>> instance_count is misleading as it does not do any accounting of
>> instances as the name suggests.
>>
>
> Not sure if I
Hello,
I have sent you mails, but still have not received a response. Kindly
get back to me for a mutual benefit transaction.
Thank you.
Blake Arnold
On Mon, Mar 22, 2021 at 05:21:56PM -0400, Steven Rostedt wrote:
Bah! John 'Warthog' Hawley email had those single quotes in it that I cut and
pasted into the Cc list, causing the quilt mail parsing to fail, but as LKML
was in the "To" part, it still sent!
Take 2
-- Steve
The following commit has been merged into the x86/microcode branch of tip:
Commit-ID: 7189b3c11903667808029ec9766a6e96de5012a5
Gitweb:
https://git.kernel.org/tip/7189b3c11903667808029ec9766a6e96de5012a5
Author:Otavio Pontes
AuthorDate:Fri, 19 Mar 2021 09:55:15 -07:00
On Wed, Mar 17, 2021 at 3:12 PM Johannes Weiner wrote:
>
> On Tue, Mar 16, 2021 at 11:05:11PM -0700, Arjun Roy wrote:
> > On Tue, Mar 16, 2021 at 3:27 AM Johannes Weiner wrote:
> > >
> > > Hello,
> > >
> > > On Mon, Mar 15, 2021 at 09:16:45PM -0700, Arjun Roy wrote:
> > > > From: Arjun Roy
> >
The req_rate name is a little misleading, so let's rename to pclk_rate
(pixel clock rate).
Signed-off-by: Dario Binacchi
---
(no changes since v2)
Changes in v2:
- The patch has been added in version 2.
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 12 ++--
1 file changed, 6 insertions(+),
The series was born from a patch to fix the LCD pixel clock setting.
Two additional patches have been added to this. One renames a misleading
variable name that was probably the cause of the bug and the other fixes
a warning message.
Changes in v3:
- Replace calculated with requested in the
The warning message did not printed the LCD pixel clock rate but the LCD
clock divisor input rate. As a consequence, the required and real pixel
clock rates are now passed to the tilcdc_pclk_diff().
Signed-off-by: Dario Binacchi
---
Changes in v3:
- Replace calculated with requested in the
The tilcdc_pclk_diff() compares the requested pixel clock rate to the
real one, so passing it clk_rate instead of clk_rate / clkdiv caused
it to fail even if the clk_rate was properly set. Adding the
real_pclk_rate variable makes the code more readable.
Signed-off-by: Dario Binacchi
---
(no
On Mon, 22 Mar 2021 22:18:17 +0100
Arnd Bergmann wrote:
> I think the code works correctly on all architectures we support because
> both 'int' and 'long' are returned in a register with any unused bits cleared.
> It is however undefined behavior in C because 'int' and 'long' are not
>
On Thu, Feb 25, 2021 at 07:35:33PM +, Suzuki K Poulose wrote:
> If the CPU implements Arm v8.4 Trace filter controls (FEAT_TRF),
> move the ETM to trace prohibited region using TRFCR, while disabling.
>
> Cc: Mathieu Poirier
> Cc: Mike Leach
> Cc: Anshuman Khandual
> Signed-off-by: Suzuki
On Fri, Mar 19, 2021 at 4:20 PM Sean Christopherson wrote:
>
> When flushing a range of GFNs across multiple roots, ensure any pending
> flush from a previous root is honored before yielding while walking the
> tables of the current root.
>
> Note, kvm_tdp_mmu_zap_gfn_range() now intentionally
On Fri, Mar 19, 2021 at 4:20 PM Sean Christopherson wrote:
>
> Fix two intertwined bugs in the NX huge page zapping that were introduced
> by the incorporation of the TDP MMU. Because there is a unified list of
> NX huge pages, zapping can encounter both TDP MMU and legacy MMU pages,
> and the
* Randy Dunlap wrote:
> > New version attached. Can I add your Reviewed-by?
>
> Sure.
> Reviewed-by: Randy Dunlap
-v3 attached, the only change is the addition of your Reviewed-by.
This would be for -mm I suppose, if Andrew agrees too?
Thanks,
Ingo
==>
From: Ingo
The TI DP83867 PHY datasheet says:
T1: Post RESET stabilization time == 195us
T3: Hardware configuration pins transition to output drivers == 64us
T4: RESET pulse width == 1us
So with a little overhead set 'reset-assert-us' to 10us (T4) and
'reset-deassert-us' to 280us (T1+T3).
Signed-off-by:
On Fri, Mar 19, 2021 at 11:55:10AM +, Mike Leach wrote:
> HI Suzuki,
>
> On Fri, 19 Mar 2021 at 10:30, Suzuki K Poulose wrote:
> >
> > Hi Mike
> >
> > > On 8 Mar 2021, at 17:26, Mike Leach wrote:
> > >
> > > Hi Suzuki,
> > >
> > > On Thu, 25 Feb 2021 at 19:36, Suzuki K Poulose
> > >
On Wed, Mar 03 2021, edwardh wrote:
> From: Edward Hsieh
>
> For chained bio, trace_block_bio_complete in bio_endio is currently called
> only by the parent bio once upon all chained bio completed.
> However, the sector and size for the parent bio are modified in bio_split.
> Therefore, the size
On Thu, Feb 25, 2021 at 07:35:42PM +, Suzuki K Poulose wrote:
> From: Anshuman Khandual
>
> Trace Buffer Extension (TRBE) implements a trace buffer per CPU which is
> accessible via the system registers. The TRBE supports different addressing
> modes including CPU virtual address and buffer
On Wed, Mar 17, 2021 at 8:21 PM Andrew Morton wrote:
>
> On Mon, 15 Mar 2021 18:30:03 -0700 Arjun Roy wrote:
>
> > From: Arjun Roy
> >
> > TCP zerocopy receive is used by high performance network applications
> > to further scale. For RX zerocopy, the memory containing the network
> > data
On Mon, Mar 22, 2021 at 9:47 PM Peter Zijlstra wrote:
> On Mon, Mar 22, 2021 at 03:32:14PM -0400, Steven Rostedt wrote:
> > On Mon, 22 Mar 2021 18:06:37 +0100
> > Arnd Bergmann wrote:
> >
> > > From: Arnd Bergmann
> > >
> > > The __static_call_return0() function is declared to return a 'long',
On Mon, Mar 22, 2021 at 11:37 AM Muni Sekhar wrote:
>
> What are some good Linux projects in kernel space for final year
> computer.science engineering students?
> Could someone help and share your ideas on this please.
Hedging deployed cryptography.
Hedging can be used to keep the state of a
On Fri, Mar 19, 2021 at 03:01:55PM +0800, Jin Yao wrote:
SNIP
> 102107,,branch-misses,8012781751,100.00,4.15,of all branches
>
> This option can be enabled in perf config by setting the variable
> 'stat.no-cvs-summary'.
>
> # perf config stat.no-cvs-summary=true
>
> # perf config -l
>
301 - 400 of 2211 matches
Mail list logo
