On 9/22/20 8:53 AM, James Bottomley wrote:
> I recently ran into this as an error from 0day. On x86 it's pretty
> much impossible to build a configuration where CONFIG_ASN1 isn't set,
> so you rarely notice a problem using the ASN.1 compiler because
> something else has selected it. However,
On Fri, Jul 24, 2020 at 12:07:55PM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> Current pcie_do_recovery() implementation has following two issues:
>
I'm having trouble parsing this out, probably just lack of my
understanding...
> 1. Fatal
Quoting Stephen Boyd (2020-09-16 16:12:01)
> The clk_rcg2_dp_determine_rate() function is used for the DP pixel clk.
> This function should return the rate that can be achieved by the pixel
> clk in 'struct clk_rate_request::rate' and match the logic similar to
> what is seen in
Quoting Jason Yan (2020-09-10 18:37:22)
> This addresses the following gcc warning with "make W=1":
>
> drivers/clk/qcom/gcc-msm8939.c:610:32: warning:
> ‘gcc_xo_gpll6_gpll0a_map’ defined but not used
> [-Wunused-const-variable=]
> static const struct parent_map gcc_xo_gpll6_gpll0a_map[] = {
>
Quoting Jonathan Marek (2020-09-03 20:09:52)
> diff --git a/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
> b/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
> index d04f5bd28dde..66a6066ae353 100644
> --- a/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
> +++
The swap area descriptor only gets struct swap_cluster_info *cluster_info
allocated if the swapfile is backed by non-rotational storage.
When the swap area is laid on top of ordinary disk spindles, lock_cluster()
will naturally return NULL.
CONFIG_THP_SWAP exposes cluster_info infrastructure to a
On Tue, Sep 22, 2020 at 08:23:18PM +0200, Oleg Nesterov wrote:
> On 09/22, Peter Xu wrote:
> >
> > On Tue, Sep 22, 2020 at 06:53:55PM +0200, Oleg Nesterov wrote:
> > > On 09/22, Peter Xu wrote:
> > > >
> > > > On Tue, Sep 22, 2020 at 05:48:46PM +0200, Oleg Nesterov wrote:
> > > > > > However since
On 9/22/20 9:00 AM, Joe Perches wrote:
> On Tue, 2020-09-22 at 07:37 -0700, Randy Dunlap wrote:
>> On 9/22/20 4:18 AM, Wang Qing wrote:
>>> Increase direcly,ununsed,manger spelling error check
>>>
>>> Signed-off-by: Wang Qing
>>> ---
>>> scripts/spelling.txt | 3 +++
>>> 1 file changed, 3
Quoting Jonathan Marek (2020-09-03 20:09:51)
> Add device tree bindings for video clock controller for SM8150 SoCs.
>
> Signed-off-by: Jonathan Marek
> ---
This one should be fine after sorting the lists in the first patch.
Quoting Jonathan Marek (2020-09-03 20:09:50)
> diff --git a/Documentation/devicetree/bindings/clock/qcom,sdm845-videocc.yaml
> b/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
> similarity index 76%
> rename from Documentation/devicetree/bindings/clock/qcom,sdm845-videocc.yaml
> rename
Constify a couple of static struct clk_ops that are not modified. Their
only usage is inside the macros and their address is passed to
clk_register_composite() which takes pointers to const struct clk_ops.
This allows the compiler to put them in read-only memory.
Signed-off-by: Rikard Falkeborn
Alrighty, I'll take everyone else's silence as tacit approval of
Ville's opinions. (I didn't receive any email bounces this time, so I
think my issue was transient.) I will start on inverting the quirk and
making the most-significant-alignment matter for these registers by
default.
Who can help
Quoting Jonathan Marek (2020-09-03 20:09:54)
> Add support for the video clock controller found on SM8250 based devices.
>
> Derived from the downstream driver.
>
> Signed-off-by: Jonathan Marek
> ---
> drivers/clk/qcom/Kconfig | 9 +
> drivers/clk/qcom/Makefile | 1 +
>
Hi Thomas,
On Tue, Sep 22, 2020 at 12:58 AM Thomas Gleixner wrote:
>
> Sami reported that run_on_irqstack_cond() requires the caller to cast
> functions to mismatching types, which trips indirect call Control-Flow
> Integrity (CFI) in Clang.
>
> Instead of disabling CFI on that function, provide
On 2020-09-22 3:51 a.m., Robin Murphy wrote:
> On 2020-09-18 21:47, Logan Gunthorpe wrote:
>> Hi Lu,
>>
>> On 2020-09-11 9:21 p.m., Lu Baolu wrote:
>>> Tom Murphy has almost done all the work. His latest patch series was
>>> posted here.
>>>
>>>
On 09/22, Peter Xu wrote:
>
> Or I can also do it in inverted order if you think better:
>
> if (unlikely(copy_ret == COPY_MM_BREAK_COW)) {
> WARN_ON_ONCE(!data.cow_new_page);
> ...
> }
Peter, let me say this again. I don't understand this code
On Tue, Sep 22, 2020 at 01:29:40PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> If kdump is enabled, the handling of shooting down CPUs does not use the
> RESET_VECTOR irq before trying to use NMIs to shoot down the CPUs.
>
> For normal errors that is fine. MCEs, however, are
On Tue, Sep 22, 2020 at 09:51:36AM +1000, Herbert Xu wrote:
> On Mon, Sep 21, 2020 at 04:26:39PM -0700, Paul E. McKenney wrote:
> >
> > > But this reasoning could apply to any data structure that contains
> > > a spin lock, in particular ones that are dereferenced through RCU.
> >
> > I lost you
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 900ffe39fec908e0aa26a30612e43ebc7140db79
Gitweb:
https://git.kernel.org/tip/900ffe39fec908e0aa26a30612e43ebc7140db79
Author:Kees Cook
AuthorDate:Sat, 19 Sep 2020 01:09:36 -07:00
On Tue, Sep 22, 2020 at 09:52:24AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Sep 20, 2020 at 10:30:00PM -0700, James Browning wrote:
> > Removed repeated words "the" and "in"
> >
> > Signed-off-by: James Browning
> > ---
> > drivers/staging/comedi/comedi.h | 4 ++--
> > 1 file changed, 2
Quoting Srinivas Kandagatla (2020-09-17 06:28:49)
> GFM Muxes in AUDIO_CC control clocks to LPASS WSA and RX Codec Macros.
> This patch adds support to these muxes.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> drivers/clk/qcom/Kconfig| 7 +
> drivers/clk/qcom/Makefile
Add of_match_table to this driver, so devices can be probed based on
device tree contents.
Signed-off-by: Michael Auchter
---
Changes since v1:
- Drop of_match_ptr() use
drivers/iio/dac/ad5696-i2c.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
The AD5338R is a 10-bit DAC with 2 outputs and an internal 2.5V
reference (enabled by default). The register configuration is nearly
identical to the AD5696R DAC that's already supported by this driver,
with the channel selection bits being the only thing different.
Signed-off-by: Michael Auchter
Add a binding for AD5686
Signed-off-by: Michael Auchter
---
Changes since v1:
- Keep supported device sorted
- fix adc -> dac type in schema path
.../bindings/iio/dac/adi,ad5686.yaml | 61 +++
1 file changed, 61 insertions(+)
create mode 100644
Hi,
-Original Message-
From: Michal Simek
Sent: Tuesday, September 22, 2020 3:00 PM
To: Zulkifli, Muhammad Husaini ; Michal
Simek ; Hunter, Adrian ;
ulf.hans...@linaro.org; linux-...@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; Arnd
Bergmann
Sheesh, I cannot stop forgetting these...
Fixes: f2a76a2955c0 (clk: qcom: Add Global Clock controller (GCC)
driver for SDM660)
Konrad
> > -#define this_cpu_ptr_nvhe(sym) this_cpu_ptr(_nvhe_sym(sym))
> > -#define per_cpu_ptr_nvhe(sym, cpu) per_cpu_ptr(_nvhe_sym(sym), cpu)
> > +/* Array of percpu base addresses. Length of the array is nr_cpu_ids. */
> > +extern unsigned long *kvm_arm_hyp_percpu_base;
> > +
> > +/*
> >
On Tue, Sep 22, 2020 at 06:52:17PM +0200, Oleg Nesterov wrote:
> On 09/22, Peter Xu wrote:
> >
> > On Tue, Sep 22, 2020 at 02:40:14PM +0200, Oleg Nesterov wrote:
> > > On 09/22, Oleg Nesterov wrote:
> > > >
> > > > On 09/21, Peter Xu wrote:
> > > > >
> > > > > @@ -859,6 +989,25 @@ static int
Can you send your patch To: somebody?
Quoting Konrad Dybcio (2020-09-22 05:09:09)
> This was likely overlooked while porting the driver upstream.
>
> Reported-by: Pavel Dubrova
> Signed-off-by: Konrad Dybcio
Any Fixes tag?
On Tue, Sep 22, 2020 at 09:28:44AM -0600, Rob Herring wrote:
> On Fri, Sep 18, 2020 at 8:33 AM Jiri Olsa wrote:
> >
> > On Fri, Sep 11, 2020 at 03:51:13PM -0600, Rob Herring wrote:
> > > In order to support usersapce access, an event must be mmapped. While
> > > there's already mmap support for
On Tue 22-09-20 11:10:17, Shakeel Butt wrote:
> On Tue, Sep 22, 2020 at 9:55 AM Michal Hocko wrote:
[...]
> > So far I have learned that you are primarily working around an
> > implementation detail in the zswap which is doing the swapout path
> > directly in the pageout path.
>
> Wait how did
On Mon, Sep 21, 2020 at 04:52:43PM -0700, Eric Biggers wrote:
> On Mon, Sep 21, 2020 at 04:26:39PM -0700, Paul E. McKenney wrote:
> > On Tue, Sep 22, 2020 at 08:11:04AM +1000, Herbert Xu wrote:
> > > On Mon, Sep 21, 2020 at 08:27:14AM -0700, Paul E. McKenney wrote:
> > > > On Mon, Sep 21, 2020 at
From: Corey Minyard
If kdump is enabled, the handling of shooting down CPUs does not use the
RESET_VECTOR irq before trying to use NMIs to shoot down the CPUs.
For normal errors that is fine. MCEs, however, are already running in
an NMI, so sending them an NMI won't do anything. The MCE code
On 09/22, Peter Xu wrote:
>
> On Tue, Sep 22, 2020 at 06:53:55PM +0200, Oleg Nesterov wrote:
> > On 09/22, Peter Xu wrote:
> > >
> > > On Tue, Sep 22, 2020 at 05:48:46PM +0200, Oleg Nesterov wrote:
> > > > > However since I didn't change this logic in this patch, it probably
> > > > > means this
On Tue, 22 Sep 2020 20:52:06 +0300
Ville Syrjälä wrote:
> Mea culpa. My doc test build was foiled by the sphinx 2 vs. 3
> regression and I was too lazy to start downgrading things.
> Any ETA for getting that fixed btw?
There's a fix of sorts in docs-next (and thus linux-next) now, has been
I saw this booting yesterday's 5.9.0-rc6+. I have one small patch applied,
quite unlikely
to cause any problems I think. Platform is apu2, fedora-27 linux, with serial
console attached.
[0.624831] =
[0.624831] [ BUG: Invalid wait context ]
[0.624831]
On Tue, Sep 22, 2020 at 11:02:03AM -0700, John Hubbard wrote:
> On 9/22/20 8:17 AM, Peter Xu wrote:
> > On Mon, Sep 21, 2020 at 04:53:38PM -0700, John Hubbard wrote:
> > > On 9/21/20 2:17 PM, Peter Xu wrote:
> > > > (Commit message collected from Jason Gunthorpe)
> > > >
> > > > Reduce the chance
On Tue, Sep 22, 2020 at 06:53:55PM +0200, Oleg Nesterov wrote:
> On 09/22, Peter Xu wrote:
> >
> > On Tue, Sep 22, 2020 at 05:48:46PM +0200, Oleg Nesterov wrote:
> > > > However since I didn't change this logic in this patch, it probably
> > > > means this
> > > > bug is also in the original code
Thank you Keith, Christoph,
So I don't need to send v3 patch?
-Original Message-
From: Christoph Hellwig [mailto:h...@lst.de]
Sent: Tuesday, September 22, 2020 10:59 PM
To: Keith Busch
Cc: tianxianting (RD) ; ax...@fb.com; h...@lst.de;
s...@grimberg.me; linux-n...@lists.infradead.org;
On Tue, Sep 22, 2020 at 9:55 AM Michal Hocko wrote:
>
> On Tue 22-09-20 08:54:25, Shakeel Butt wrote:
> > On Tue, Sep 22, 2020 at 4:49 AM Michal Hocko wrote:
> > >
> > > On Mon 21-09-20 10:50:14, Shakeel Butt wrote:
> [...]
> > > > Let me add one more point. Even if the high limit reclaim is
On Fri, Sep 18, 2020 at 10:16 PM Kevin Hilman wrote:
>
> I haven't had the time or the expertise to adequately review and
> maintain these drivers for awhile, so make it official.
Well, fair enough, so applied as 5.10 material.
But this means that I'm going to stop picking up AVS drivers
On Fri, Sep 18, 2020 at 01:00:44PM +0100, Will Deacon wrote:
> On Wed, Sep 16, 2020 at 06:34:37PM +0100, David Brazdil wrote:
> > In preparation for unmapping hyp pages from host stage-2, allocate/free hyp
> > stack using new helpers which automatically mark the pages reserved.
>
> Given that
> > u64 *ptr;
> >
> > - ptr = per_cpu_ptr(_ssbd_callback_required, cpu);
> > + ptr = per_cpu_ptr_nvhe(arm64_ssbd_callback_required, cpu);
> > err = create_hyp_mappings(ptr, ptr + 1, PAGE_HYP);
> > if (err)
> > return
Em Tue, Sep 22, 2020 at 02:56:30PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Sep 22, 2020 at 09:50:04AM +0800, Jin Yao escreveu:
> > Some metrics (such as DRAM_BW_Use) consists of uncore events and
> > duration_time. For uncore events, counter->core.system_wide is
> > true. But for
On Tue, Sep 22, 2020 at 09:24:38AM -0700, Sean Christopherson wrote:
> The "else if" is correct. Version Array (VA) pages have 512 slots that hold
> metadata for evicted EPC pages, i.e. swapping a page out of the EPC requires
> a VA slot. For simplicity (LOL),
I'll say.
> the approach we are
One last change I realized we should do is print the name of the AUX adapter
in question. I don't mind just adding that myself before I push it though so
you don't need to send a respin.
Going to go push this to drm-misc-next, thanks!
On Tue, 2020-09-22 at 14:53 +0800, Koba Ko wrote:
> As per
On 9/22/20 8:17 AM, Peter Xu wrote:
On Mon, Sep 21, 2020 at 04:53:38PM -0700, John Hubbard wrote:
On 9/21/20 2:17 PM, Peter Xu wrote:
(Commit message collected from Jason Gunthorpe)
Reduce the chance of false positive from page_maybe_dma_pinned() by keeping
Not yet, it doesn't. :) More:
Hi Peng,
On Tue, Sep 15, 2020 at 11:55 PM wrote:
>
> From: Peng Fan
>
> V2:
> Update to use pmc0/pmc1 following hardware naming
>
> This patchset is to add HSRUN mode support.
> Patch 1,2 is to add binding doc and dts node
> Patch 3 is to support HSRUN mode
> Patch 4 is to use wait mode when
Em Tue, Sep 22, 2020 at 09:50:04AM +0800, Jin Yao escreveu:
> Some metrics (such as DRAM_BW_Use) consists of uncore events and
> duration_time. For uncore events, counter->core.system_wide is
> true. But for duration_time, counter->core.system_wide is false
> so target.system_wide is set to false.
On 2020-09-22 19:03, Andrew Morton wrote:
On Tue, 22 Sep 2020 15:56:36 +0200 Oscar Salvador
wrote:
This patchset is the latest version of soft offline rework patchset
targetted for v5.9.
Thanks.
Where do we now stand with the followon patches:
On Tue, Sep 22, 2020 at 01:10:46PM -0300, Jason Gunthorpe wrote:
> On Tue, Sep 22, 2020 at 11:17:36AM -0400, Peter Xu wrote:
>
> > > But it's admittedly a cosmetic point, combined with my perennial fear that
> > > I'm missing something when I look at a READ_ONCE()/WRITE_ONCE() pair. :)
> >
> >
From: Mauro Carvalho Chehab
The name of the argument is different, causing those warnings:
./drivers/gpu/drm/drm_edid.c:3754: warning: Function parameter or
member 'video_code' not described in 'drm_display_mode_from_cea_vic'
./drivers/gpu/drm/drm_edid.c:3754: warning: Excess
From: Mauro Carvalho Chehab
As warned by kernel-doc:
./drivers/gpu/drm/drm_dp_helper.c:385: warning: Function parameter or
member 'type' not described in 'drm_dp_downstream_is_type'
./drivers/gpu/drm/drm_dp_helper.c:886: warning: Function parameter or
member 'dev' not
> > +#define HYP_SECTION_NAME(NAME) .hyp##NAME
> > +
> > +/* Defines an ELF hyp section from input section @NAME and its
> > subsections. */
> > +#define HYP_SECTION(NAME) \
> > + HYP_SECTION_NAME(NAME) : { *(NAME NAME##.[0-9a-zA-Z_]*) }
>
> I still don't get why we can't just use NAME ##
On Tue, Sep 22, 2020 at 9:27 AM Ian Bearman wrote:
>
> Hi, Nick. Thanks for reaching out again. I'm excited to see other groups
> taking an interest in LTO and PGO for Linux. CFI for the kernel sounds like a
> huge deal, nice!
Yes, CFI is quite nice. There are some hardware extensions in the
On Tue, Sep 22, 2020 at 01:39:41PM -0400, Lyude Paul wrote:
> For patches 2 and 3:
>
> Reviewed-by: Lyude Paul
>
> I'll go ahead and push these to drm-intel-next-queued (since drm-misc-next
> doesn't have these patches in yet, and the commits these fix were originally
> merged through
On Tue, Sep 22, 2020 at 4:22 AM Mauro Carvalho Chehab
wrote:
>
> kernel-doc expects the function prototype to be just after
> the kernel-doc markup, as otherwise it will get it all wrong:
>
> ./net/core/dev.c:10036: warning: Excess function parameter 'dev'
> description in
On Tue, 22 Sep 2020 18:21:52 +0200
Greg Kroah-Hartman wrote:
> On Tue, Sep 22, 2020 at 03:23:44PM +0200, Torsten Duwe wrote:
> > On Mon, Sep 21, 2020 at 10:40:37AM +0200, Stephan Mueller wrote:
> > > Am Montag, 21. September 2020, 09:58:16 CEST schrieb Nicolai
> > > Stange:
> > >
> > > > -
PowerPC allmodconfig often fails to build as follows:
LD .tmp_vmlinux.kallsyms1
KSYM.tmp_vmlinux.kallsyms1.o
LD .tmp_vmlinux.kallsyms2
KSYM.tmp_vmlinux.kallsyms2.o
LD .tmp_vmlinux.kallsyms3
KSYM.tmp_vmlinux.kallsyms3.o
LD vmlinux
On Tue, Sep 22, 2020 at 4:22 AM Mauro Carvalho Chehab
wrote:
>
> kernel-doc expects the function prototype to be just after
> the kernel-doc markup, as otherwise it will get it all wrong:
>
> ./net/core/dev.c:10036: warning: Excess function parameter 'dev'
> description in
On Tue, Sep 22, 2020 at 03:42:21PM +0100, Mark Brown wrote:
On Tue, Sep 22, 2020 at 10:25:15AM -0400, Sasha Levin wrote:
On Mon, Sep 21, 2020 at 04:07:01PM +0100, Mark Brown wrote:
> This is pretty much a cosmetic change - previously we were silently not
> reading the register, this just
For patches 2 and 3:
Reviewed-by: Lyude Paul
I'll go ahead and push these to drm-intel-next-queued (since drm-misc-next
doesn't have these patches in yet, and the commits these fix were originally
merged through drm-intel-next-queued anyway). thanks!
On Tue, 2020-09-22 at 13:22 +0200, Mauro
On Fri, Sep 18, 2020 at 4:34 AM Nadeem Athani wrote:
>
> Cadence controller will not initiate autonomous speed change if
> strapped as Gen2. The Retrain bit is set as a quirk to trigger
> this speed change.
>
> Signed-off-by: Nadeem Athani
> ---
>
On Fri, Sep 18, 2020 at 12:32:48AM +0200, Marek Behún wrote:
> Hi,
>
> this series is also available at [1].
>
> This is v2, you can read cover letter of v1 at [2] (togehter with
> explanation of why I did this).
...
> leds: ns2: use devres LED registering function
> leds: ns2: alloc
On 9/22/20 1:12 AM, Dan Carpenter wrote:
The error handling code does this:
err_free:
kfree(devmem);
^
err_release:
release_mem_region(devmem->pagemap.range.start,
range_len(>pagemap.range));
The problem is that when
On Mon, Sep 21, 2020 at 1:50 AM Neil Armstrong wrote:
>
> When establish link timeouts, probe fails but the error is unrelated since
> the PCIe controller has been probed succesfully.
>
> Align with most of the other dw-pcie drivers and ignore return of
> dw_pcie_wait_for_link() in the host_init
the struct name was modified long ago, but the comment still
use struct handle_s.
Signed-off-by: Hui Su
---
include/linux/jbd2.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/jbd2.h b/include/linux/jbd2.h
index 08f904943ab2..a1ef05412acf 100644
---
On Tue, Sep 22, 2020 at 12:46:05PM -0400, Mikulas Patocka wrote:
> I agree that the b+tree were a good choice for XFS.
>
> In RAM-based maps, red-black trees or avl trees are used often. In
> disk-based maps, btrees or b+trees are used. That's because in RAM, you
> are optimizing for the number
On Tue, 2020-09-22 at 18:05 +0100, Matthew Wilcox wrote:
> On Tue, Sep 22, 2020 at 12:23:45PM -0400, Qian Cai wrote:
> > On Fri, 2020-09-11 at 00:47 +0100, Matthew Wilcox (Oracle) wrote:
> > > Size the uptodate array dynamically to support larger pages in the
> > > page cache. With a 64kB page,
Hi Archie,
On Tue, Sep 22, 2020 at 12:37 AM Archie Pusaka wrote:
>
> Hi Luiz,
>
> On Tue, 22 Sep 2020 at 01:13, Luiz Augusto von Dentz
> wrote:
> >
> > Hi Archie,
> >
> > On Mon, Sep 21, 2020 at 1:31 AM Archie Pusaka wrote:
> > >
> > > From: Archie Pusaka
> > >
> > > According to the spec Ver
On 9/22/2020 9:32 AM, Jan Kiszka wrote:
>
> On 22.09.20 16:28, George Prekas wrote:
>> If the next pointer is NULL, list_for_each gets stuck in an infinite
>> loop.
>>
>> Signed-off-by: George Prekas
>> ---
>> scripts/gdb/linux/lists.py | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff
On 22.09.20 16:37, Vlastimil Babka wrote:
> As per the discussions [1] [2] this is an attempt to implement David's
> suggestion that page isolation should disable pcplists to avoid races with
> page
> freeing in progress. This is done without extra checks in fast paths, as
> explained in Patch 9.
On Mon, Sep 21, 2020 at 7:40 AM Daniel Bristot de Oliveira
wrote:
>
> The RT_RUNTIME_SHARE sched feature enables the sharing of rt_runtime
> between CPUs, allowing a CPU to run a real-time task up to 100% of the
> time while leaving more space for non-real-time tasks to run on the CPU
> that lend
On Tue, 22 Sep 2020 18:37:25 +0530 George Cherian wrote:
> This series add support for VLAN based flow distribution for octeontx2
> netdev driver. This adds support for configuring the same via ethtool.
>
> Following tests have been done.
> - Multi VLAN flow with same SD
> - Multi
On Mon, 21 Sep 2020 22:01:46 -0400 Rik van Riel wrote:
> Both with frontswap/zswap, and with some extremely fast IO devices,
> swap IO will be done before the "asynchronous" swap_readpage() call
> has returned.
>
> In that case, doing swap readahead only wastes memory, increases
> latency, and
Hi Thomas,
Le mar. 22 sept. 2020 à 18:02, Thomas Bogendoerfer
a écrit :
On Thu, Sep 17, 2020 at 03:35:28PM +0200, Paul Cercueil wrote:
There is nothing that prevents us from using lower maximum values.
It's something that we actually want, when using bigger page sizes
on
devices with
On 22/09/2020 19:20, Greg KH wrote:
On Tue, Sep 22, 2020 at 05:13:02PM +0300, Paraschiv, Andra-Irina wrote:
On 21/09/2020 15:34, Paraschiv, Andra-Irina wrote:
On 14/09/2020 20:23, Paraschiv, Andra-Irina wrote:
On 14/09/2020 18:59, Greg KH wrote:
On Fri, Sep 11, 2020 at 05:11:37PM +0300,
Hi Linus,
A few fixes - most of them regression fixes from this cycle, but also a
few stable heading fixes, and a build fix for the included demo tool
since some systems now actually have gettid() available.
Please pull.
The following changes since commit
On Tue, Sep 22, 2020 at 12:23:45PM -0400, Qian Cai wrote:
> On Fri, 2020-09-11 at 00:47 +0100, Matthew Wilcox (Oracle) wrote:
> > Size the uptodate array dynamically to support larger pages in the
> > page cache. With a 64kB page, we're only saving 8 bytes per page today,
> > but with a 2MB
On Tue, Sep 22, 2020 at 11:53 AM wrote:
>
>
> On 9/22/20 6:58 AM, Philipp Rudo wrote:
> >
> > AFAIK pstore requires UEFI to work. So what's the point to enable it on
> > non-UEFI
> > systems?
>
>
> I don't think UEFI is required, ERST can specify its own backend. And that,
> in fact, can be
Add a documentation for the Rockchip Camera Interface controller
binding.
This controller can be found on platforms such as the PX30 or the
RK3288, the PX30 being the only platform supported so far.
Signed-off-by: Maxime Chevallier
---
V3 :
- renamed the controller
Hi Archie,
On Tue, Sep 22, 2020 at 12:48 AM Archie Pusaka wrote:
>
> Hi Luiz,
>
> On Tue, 22 Sep 2020 at 01:15, Luiz Augusto von Dentz
> wrote:
> >
> > Hi Archie,
> >
> >
> > On Mon, Sep 21, 2020 at 12:56 AM Archie Pusaka wrote:
> > >
> > > From: Archie Pusaka
> > >
> > > When receiving
Introduce a driver for the camera interface on some Rockchip platforms.
This controller supports CSI2 and BT656 interfaces, but for
now only the BT656 interface could be tested, hence it's the only one
that's supported in the first version of this driver.
This controller can be fond on PX30,
On Wed, 16 Sep 2020 16:28:06 +0200
Heiko Carstens wrote:
> On Sat, Sep 12, 2020 at 09:54:12PM -0400, Qian Cai wrote:
> > Occasionally, running this LTP test will trigger an error below on
> > s390:
> >
The PX30 has a camera interface, supporting CSI2 and BT656
modes. Add a DT description for this interface.
Signed-off-by: Maxime Chevallier
---
V3: Renamed the driver
arch/arm64/boot/dts/rockchip/px30.dtsi | 12
1 file changed, 12 insertions(+)
diff --git
Hi everyone,
This is the third iteration of the series introducing a driver for the
PX30 camera interface.
This was previously known as the "cif" driver in other iterations, but
was renamed to "vip" following Ezequiel's advices to match the datasheet
name.
This is based on a BSP driver, and I'm
On Tue, 22 Sep 2020 15:56:36 +0200 Oscar Salvador wrote:
> This patchset is the latest version of soft offline rework patchset
> targetted for v5.9.
Thanks.
Where do we now stand with the followon patches:
mmhwpoison-take-free-pages-off-the-buddy-freelists.patch
On Tue 22-09-20 09:51:30, Shakeel Butt wrote:
> On Tue, Sep 22, 2020 at 9:34 AM Michal Hocko wrote:
> >
> > On Tue 22-09-20 09:29:48, Shakeel Butt wrote:
[...]
> > > Anyways, what do you think of the in-kernel PSI based
> > > oom-kill trigger. I think Johannes had a prototype as well.
> >
> > We
On 9/22/20 12:40 PM, Alex Williamson wrote:
On Mon, 21 Sep 2020 08:43:29 -0400
Matthew Rosato wrote:
On 9/10/20 10:59 AM, Matthew Rosato wrote:
While it is true that devices with is_virtfn=1 will have a Memory Space
Enable bit that is hard-wired to 0, this is not the only case where we
see
On Tue 22-09-20 08:54:25, Shakeel Butt wrote:
> On Tue, Sep 22, 2020 at 4:49 AM Michal Hocko wrote:
> >
> > On Mon 21-09-20 10:50:14, Shakeel Butt wrote:
[...]
> > > Let me add one more point. Even if the high limit reclaim is swift, it
> > > can still take 100s of usecs. Most of our jobs are
On 09/22, Peter Xu wrote:
>
> On Tue, Sep 22, 2020 at 05:48:46PM +0200, Oleg Nesterov wrote:
> > > However since I didn't change this logic in this patch, it probably means
> > > this
> > > bug is also in the original code before this series... I'm thinking
> > > maybe I
> > > should prepare a
On 09/22, Peter Xu wrote:
>
> On Tue, Sep 22, 2020 at 02:40:14PM +0200, Oleg Nesterov wrote:
> > On 09/22, Oleg Nesterov wrote:
> > >
> > > On 09/21, Peter Xu wrote:
> > > >
> > > > @@ -859,6 +989,25 @@ static int copy_pte_range(struct mm_struct
> > > > *dst_mm, struct mm_struct *src_mm,
> > > >
On Tue, Sep 22, 2020 at 07:30:32PM +0300, Gal Pressman wrote:
> On 22/09/2020 19:14, Jason Gunthorpe wrote:
> > On Tue, Sep 22, 2020 at 03:46:29PM +0300, Gal Pressman wrote:
> >
> >> I agree, that makes sense.
> >> But assuming Oded actually goes and implements all the needed verbs to get
> >> a
On Tue, Sep 22, 2020 at 9:34 AM Michal Hocko wrote:
>
> On Tue 22-09-20 09:29:48, Shakeel Butt wrote:
> > On Tue, Sep 22, 2020 at 8:16 AM Michal Hocko wrote:
> > >
> > > On Tue 22-09-20 06:37:02, Shakeel Butt wrote:
> [...]
> > > > I talked about this problem with Johannes at LPC 2019 and I
On Tue, 22 Sep 2020 12:09:19 +0800
Yafang Shao wrote:
> > > Are there any methods to avoid un-inlining these wrappers ?
> > >
> > > For example,
> > > // include/linux/mmap_lock.h
> > >
> > > void mmap_lock_start_trace_wrapper();
> > > void mmap_lock_acquire_trace_wrapper();
> > >
> > > static
Em Tue, Sep 22, 2020 at 08:07:32PM +0800, Leo Yan escreveu:
> Hi Arnaldo,
>
> On Mon, Sep 14, 2020 at 07:53:05PM +0800, Leo Yan wrote:
> > This patch set is to refactor TSC implementation and move TSC code from
> > x86 folder to util/tsc.c, this allows all archs to reuse the code. And
> > alse
This patch is created and tested on top of mainline linux
commit 856deb866d16 ("Linux 5.9-rc5")
Reference log of "make dt_binding_check" is available here[1].
Just in case required the log of dt_binding_check without this patch
is available here[2]
[1] https://paste.ubuntu.com/p/d2bXwvpFz9/
Convert the device tree bindings for the SiFive's FU540-C000 SoC's L2 Cache
controller to YAML format.
Signed-off-by: Sagar Kadam
---
.../devicetree/bindings/riscv/sifive-l2-cache.txt | 51
.../devicetree/bindings/riscv/sifive-l2-cache.yaml | 90 ++
2 files
Hi
Thanks for reviewing NVFS.
On Tue, 22 Sep 2020, Dave Chinner wrote:
> Hi Mikulas,
>
> I'll say up front that I think you're barking up the wrong tree
> trying to knock down XFS and ext4 to justify NVFS. NVFS will stand
> or fall on it's own merits, not on how you think it's better than
>
From: Eric Biggers
There's no need for mnt_want_write_file() to increment mnt_writers when
the file is already open for writing, provided that
mnt_drop_write_file() is changed to conditionally decrement it.
We seem to have ended up in the current situation because
mnt_want_write_file() used to
501 - 600 of 1340 matches
Mail list logo
