Replace the memory controller's custom hierarchical stats code with
the generic rstat infrastructure provided by the cgroup core.
The current implementation does batched upward propagation from the
write side (i.e. as stats change). The per-cpu batches introduce an
error, which is multiplied by
Rstat currently only supports the default hierarchy in cgroup2. In
order to replace memcg's private stats infrastructure - used in both
cgroup1 and cgroup2 - with rstat, the latter needs to support cgroup1.
The initialization and destruction callbacks for regular cgroups are
already in place.
Current users of the rstat code can source root-level statistics from
the native counters of their respective subsystem, allowing them to
forego aggregation at the root level. This optimization is currently
implemented inside the generic rstat code, which doesn't track the
root cgroup and doesn't
With memcg having switched to rstat, memory.stat output is precise.
Update the cgroup selftest to reflect the expectations and error
tolerances of the new implementation.
Also add newly tracked types of memory to the memory.stat side of the
equation, since they're included in memory.current and
On Tue, Feb 09, 2021 at 10:16:02AM +0100, Peter Zijlstra wrote:
> Where we already decode: mov %rsp, %reg, also decode mov %rsp, (%reg).
>
> Nothing should match for this new stack-op.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> tools/objtool/arch/x86/decode.c | 23
There are no users outside of the memory controller itself. The rest
of the kernel cares either about node or lruvec stats.
Signed-off-by: Johannes Weiner
Reviewed-by: Shakeel Butt
Reviewed-by: Roman Gushchin
Acked-by: Michal Hocko
---
include/linux/memcontrol.h | 44
No need to encapsulate a simple struct member access.
Signed-off-by: Johannes Weiner
Reviewed-by: Shakeel Butt
Reviewed-by: Roman Gushchin
Acked-by: Michal Hocko
---
include/linux/memcontrol.h | 8 +---
mm/memcontrol.c| 21 +++--
2 files changed, 12
The memcg hotunplug callback erroneously flushes counts on the local
CPU, not the counts of the CPU going away; those counts will be lost.
Flush the CPU that is actually going away.
Also simplify the code a bit by using mod_memcg_state() and
count_memcg_events() instead of open-coding the upward
This is version 3 of the memcg rstat patches.
Updates since v2:
- optimize root level in io controller's rstat flush callback (Tejun)
- add comments and changelog notes on root level optimization (Tejun)
- eliminate mem_cgroup_usage() rstat flush for leaf cgroups (Shakeel)
- collected review &
> On 3 Feb 2021, at 00:01, Nick Desaulniers wrote:
>
> I wonder if PAC or BTI also make this slightly more complex? PAC at
> least has implications for unwinders, IIUC.
BTI has effect on the jump target\case because a landing pad is required for
each and every target.
As I see that would
On Tue, Feb 9, 2021 at 5:36 AM Greg KH wrote:
>
> On Wed, Jan 27, 2021 at 04:56:22PM -0600, Mike Ximing Chen wrote:
> > Add basic driver functionality (load, unload, probe, and remove callbacks)
> > for the DLB driver.
> >
> > Add documentation which describes in detail the hardware, the user
> >
- Ursprüngliche Mail -
>> A simple (but ugly!) approach would be redirecting mmap() requests on CUSE
>> devices to /dev/mem.
>> hmm?
>
> what requests are you talking about given that at the moment the CUSE
> client interface (cuse_lowlevel_ops) does not expose mmap?
The mmap() call
On Tue, Feb 09, 2021 at 10:42:31AM +0200, stef...@marvell.com wrote:
> if (priv->global_tx_fc && priv->hw_version != MVPP21) {
> - val = mvpp2_cm3_read(priv, MSS_FC_COM_REG);
> - val |= FLOW_CONTROL_ENABLE_BIT;
> - mvpp2_cm3_write(priv, MSS_FC_COM_REG,
On Tue, 2021-02-09 at 17:13 +0100, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 05:05:14PM +0100, Mike Galbraith wrote:
>
> > ld: init/main.o: in function `trace_initcall_start':
> > /backup/usr/local/src/kernel/linux-tip-rt/./include/trace/events/initcall.h:27:
> > undefined reference to
Create CLL and Mastering display colour volume v4l2 controls for
encoder, add handling of HDR10 PQ SEI packet payloads for v4.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.h | 2 ++
drivers/media/platform/qcom/venus/hfi_cmds.c | 8 +
A simple (but ugly!) approach would be redirecting mmap() requests on CUSE
devices to /dev/mem.
hmm?
what requests are you talking about given that at the moment the CUSE
client interface (cuse_lowlevel_ops) does not expose mmap?
Document Content Light Level and Mastering Display v4l2 colorimetry
controls.
Signed-off-by: Stanimir Varbanov
---
.../media/v4l/ext-ctrls-colorimetry.rst | 71 +++
.../media/v4l/vidioc-g-ext-ctrls.rst | 8 +++
.../media/videodev2.h.rst.exceptions | 2 +
Introduce Content light level and Mastering display colour
volume Colorimetry compound controls with relevant payload
structures and validation.
Signed-off-by: Stanimir Varbanov
---
drivers/media/v4l2-core/v4l2-ctrls.c | 67
include/media/v4l2-ctrls.h | 4
Hi Bartosz, Rafael,
On Tue, Feb 09, 2021 at 04:49:37PM +0100, Bartosz Golaszewski wrote:
> On Mon, Feb 8, 2021 at 5:54 PM Rafael J. Wysocki wrote:
> >
> > On Mon, Feb 8, 2021 at 5:44 PM Bartosz Golaszewski
> > wrote:
> > >
> > > On Fri, Feb 5, 2021 at 2:25 PM Sakari Ailus
> > > wrote:
> > > >
Add a document for ext control colorimetry class.
Signed-off-by: Stanimir Varbanov
---
.../userspace-api/media/v4l/common.rst| 1 +
.../media/v4l/ext-ctrls-colorimetry.rst | 22 +++
.../media/v4l/vidioc-g-ext-ctrls.rst | 4
3 files changed, 27
Add Colorimetry control class for colorimetry controls
Signed-off-by: Stanimir Varbanov
---
drivers/media/v4l2-core/v4l2-ctrls.c | 7 ++-
include/uapi/linux/v4l2-controls.h | 4
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
Hi Gerd,
I tested the patch on drm-misc-next and it fixed the issue.
Thanks,
- Tong
> On Feb 9, 2021, at 7:16 AM, Gerd Hoffmann wrote:
>
> On Mon, Feb 08, 2021 at 12:07:01PM -0500, Tong Zhang wrote:
>> Does this patch fix an issue raised previously? Or should they be used
>> together?
>>
Changes since v4:
* 1/5 - fixed a typo (Hans)
* 2/5 - add some mode info about new colorimetry class (Hans)
* 4/5 - correct cd/m2 -> cd/m\ :sup:`2`
- change to US spelling for color word
- use correct v4l2_ctrl_type in videodev2.h.rst.exceptions
- documented
On 2/8/21 11:35 PM, Dmitry Vyukov wrote:
On Sun, Feb 7, 2021 at 1:20 PM syzbot
wrote:
Hello,
syzbot found the following issue on:
HEAD commit:73d62e81 kmsan: random: prevent boot-time reports in _mix_..
git tree: https://github.com/google/kmsan.git master
console output:
On Tue, Feb 09, 2021 at 04:12:33PM +0100, Thomas Gleixner wrote:
> On Mon, Feb 08 2021 at 14:42, Josh Poimboeuf wrote:
> > On Thu, Feb 04, 2021 at 09:49:08PM +0100, Thomas Gleixner wrote:
> >> #ifdef CONFIG_X86_64
> >> +
> >> +#ifdef CONFIG_UNWINDER_FRAME_POINTER
> >> +# define
On Tue, Feb 9, 2021 at 9:53 PM Petr Mladek wrote:
>
> On Tue 2021-02-09 18:56:13, Yafang Shao wrote:
> > Currently the pGp only shows the names of page flags, rather than
> > the full information including section, node, zone, last cpupid and
> > kasan tag. While it is not easy to parse these
On Sun, Feb 07, 2021 at 04:26:40PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Feb 07, 2021 at 08:54:49PM +0530, karthek wrote:
> > On Sun, Feb 07, 2021 at 04:21:29PM +0100, Greg Kroah-Hartman wrote:
> > > On Sun, Feb 07, 2021 at 08:49:46PM +0530, karthek wrote:
> > > > On Sun, Feb 07, 2021 at
On Tue, Feb 09, 2021 at 05:13:15PM +0100, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 05:05:14PM +0100, Mike Galbraith wrote:
>
> > ld: init/main.o: in function `trace_initcall_start':
> > /backup/usr/local/src/kernel/linux-tip-rt/./include/trace/events/initcall.h:27:
> > undefined reference
On 09.02.21 14:25, Michal Hocko wrote:
On Tue 09-02-21 11:23:35, David Hildenbrand wrote:
[...]
I am constantly trying to fight for making more stuff MOVABLE instead of
going into the other direction (e.g., because it's easier to implement,
which feels like the wrong direction).
Maybe I am the
On Tue, 9 Feb 2021 10:20:30 +0100 Aleksander Morgado wrote:
> This may be a stupid suggestion, but would the integration look less a
> backdoor if it would have been named "mhi_wwan" and it exposed already
> all the AT+DIAG+QMI+MBIM+NMEA possible channels as chardevs, not just
> QMI?
What's DIAG?
On Mon, Feb 08, 2021 at 09:42:05PM +0100, Bean Huo wrote:
> On Mon, 2021-02-08 at 20:56 +0800, Leo Liou wrote:
> > Based on ufshci spec, it defines that "Offset C0h to FFh" belong
> > to vendor specific. If cpu vendor doesn't support these commands, it
> > makes the dme errors:
> >
> > ufs:
On Sun, Feb 07, 2021 at 10:31:38PM +0100, Maciej W. Rozycki wrote:
> On Thu, 21 Jan 2021, Jinyang He wrote:
>
> > mm16_r5_format.rt is 5 bits, so directly judge the value if equal or not.
> > mm_jalr_op requires 7th to 16th bits. These 10 which bits generated by
>
> The minor opcode extension
On Wed, Jan 20, 2021 at 12:51:13AM -0800, Pan Bian wrote:
> The reference count of the old buffer head should be decremented on path
> that fails to get the new buffer head.
>
> Fixes: 6b4657667ba0 ("fs/affs: add rename exchange")
> Signed-off-by: Pan Bian
Thanks, added to affs branch. The fix
Le 09/02/2021 à 02:55, Nicholas Piggin a écrit :
Excerpts from Christophe Leroy's message of February 9, 2021 1:10 am:
When r3 is not modified, reload it from regs->orig_r3 to free
volatile registers. This avoids a stack frame for the likely part
of system_call_exception()
This doesn't on
On Tue, Feb 09, 2021 at 05:05:14PM +0100, Mike Galbraith wrote:
> ld: init/main.o: in function `trace_initcall_start':
> /backup/usr/local/src/kernel/linux-tip-rt/./include/trace/events/initcall.h:27:
> undefined reference to `__SCT__preempt_schedule_notrace'
Ooohh... this is because x86 can't
On Tue, Feb 09, 2021 at 05:03:46PM +0100, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 01:24:30PM +, Mark Rutland wrote:
> > On Tue, Feb 09, 2021 at 09:34:10AM +0100, Peter Zijlstra wrote:
> > >
> > > Subject: lockdep: Noinstr annotate warn_bogus_irq_restore()
> > > From: Peter Zijlstra
>
On Thu, Jan 21, 2021 at 06:43:47PM +0100, Vincent Knecht wrote:
> This adds dts bindings for the mstar msg26xx touchscreen.
>
> Signed-off-by: Vincent Knecht
> ---
> Changed in v3:
> - added `touchscreen-size-x: true` and `touchscreen-size-y: true` properties
> Changed in v2:
> - changed M-Star
Hi Linus,
Can you pull this during the upcoming merge window? It provides a more
modern I/O API for fscache and moves some common pieces out of network
filesystems into a common helper library. This request only includes
modifications for afs and ceph.
Dave Wysochanski has a patch series for
The ipa_fws.elf found in the Lenovo Yoga C630 isn't packed like the one
found in e.g. the MTP, so it doesn't fit in the "standard" ipa_fws
memory region. Further more, authentication of ipa_fws at the usual base
address is rejected by the Peripheral Authentication Service (in
TrustZone), so some
The reserved-memory regions used for carrying firmware to be run on the
various cores and co-processors in a Qualcomm platform differs in size,
placement and presence based on each device's feature set and security
configuration.
Rather than providing some basic set that works on the MTP and then
On 2/5/21 11:28 PM, David Rientjes wrote:
> On Tue, 2 Feb 2021, Charan Teja Kalla wrote:
>
>> >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> >> index 519a60d..531f244 100644
>> >> --- a/mm/page_alloc.c
>> >> +++ b/mm/page_alloc.c
>> >> @@ -4152,6 +4152,8 @@
On Tue, Feb 09, 2021 at 04:16:20PM +0100, Jessica Yu wrote:
> Hmm, these errors don't look like it's related to that particular commit. I
> was
> able to reproduce these weird autoksym errors even without any modules-next
> patches applied, and on a clean v5.11-rc7 tree.
I OTOH can't reproduce
On 09.02.21 15:24, Georgi Djakov wrote:
From: Patrick Daly
Print the name of the CMA region for convenience. This is useful
information to have when cma_alloc() fails.
Signed-off-by: Patrick Daly
Signed-off-by: Georgi Djakov
---
v2:
* Print the "count" variable, as it was originally in
On Tue, 2021-02-09 at 16:13 +0100, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 02:45:37PM +0100, Mike Galbraith wrote:
> >
> > PREEMPT_RT and PREEMPT both needs PREEMPT_DYNAMIC to build, so move
> > selection of PREEMPT_DYNAMIC to the common denominator, PREEMPTION.
>
> I'm confused, why would
- Ursprüngliche Mail -
> for example, many existing video applications use mmap() to map the
> device memory to userspace memory. Adding support for mmap() to CUSE
> would allow these apps to work without any modifications with CUSE-based
> device drivers other than kernel drivers.
So
On Tue, Feb 09, 2021 at 03:32:38PM +0100, Rafael J. Wysocki wrote:
> On Mon, Feb 8, 2021 at 8:48 PM Andy Shevchenko
> wrote:
> > On Mon, Feb 8, 2021 at 9:47 PM Andy Shevchenko
> > wrote:
> > > On Mon, Feb 8, 2021 at 9:30 PM Rafael J. Wysocki
> > > wrote:
> > > > On Friday, February 5, 2021
On Tue, Feb 09, 2021 at 04:24:14PM +0200, Georgi Djakov wrote:
> From: Patrick Daly
>
> Print the name of the CMA region for convenience. This is useful
> information to have when cma_alloc() fails.
>
> Signed-off-by: Patrick Daly
> Signed-off-by: Georgi Djakov
Acked-by: Minchan Kim
On Tue, Feb 09, 2021 at 01:24:30PM +, Mark Rutland wrote:
> On Tue, Feb 09, 2021 at 09:34:10AM +0100, Peter Zijlstra wrote:
> >
> > Subject: lockdep: Noinstr annotate warn_bogus_irq_restore()
> > From: Peter Zijlstra
> > Date: Tue Feb 9 09:30:03 CET 2021
> >
> > vmlinux.o: warning:
Hi Daniel,
On Sun, Feb 7, 2021 at 5:29 PM Daniel Lezcano wrote:
>
> On 07/02/2021 04:31, Guo Ren wrote:
> > Hi Daniel,
> >
> > On Thu, Feb 4, 2021 at 4:48 PM Daniel Lezcano
> > wrote:
> >>
> >> On 04/02/2021 08:46, guo...@kernel.org wrote:
> >>> From: Guo Ren
> >>>
> >>> The timer-mp-csky.c
Looks good to me, thx.
On Tue, Feb 9, 2021 at 6:08 PM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warning:
>
> ./drivers/irqchip/irq-csky-apb-intc.c:139:9-10: WARNING: return of 0/1
> in function 'handle_irq_perbit' with return type bool.
>
> Reported-by: Abaci Robot
> Signed-off-by:
On Tue, 9 Feb 2021 19:02:15 +0800
Jisheng Zhang wrote:
> Add tracepoints to retrieve information about the invoke_fn. This would
> help to measure how many invoke_fn are triggered and how long it takes
> to complete one invoke_fn call.
>
> Signed-off-by: Jisheng Zhang
> ---
>
Adds test_sscanf to test various number conversion cases, as
number conversion was previously broken.
This also tests the simple_strtoxxx() functions exported from
vsprintf.c.
Signed-off-by: Richard Fitzgerald
Acked-by: Andy Shevchenko
---
MAINTAINERS | 1 +
lib/Kconfig.debug | 3 +
Adds a wrapper shell script for the test_scanf module.
Signed-off-by: Richard Fitzgerald
Reviewed-by: Petr Mladek
Acked-by: Andy Shevchenko
---
tools/testing/selftests/lib/Makefile | 2 +-
tools/testing/selftests/lib/config | 1 +
tools/testing/selftests/lib/scanf.sh | 4
3 files
If a signed number field starts with a '-' the field width must be > 1,
or unlimited, to allow at least one digit after the '-'.
This patch adds a check for this. If a signed field starts with '-'
and field_width == 1 the scanf will quit.
It is ok for a signed number field to have a field width
The existing code attempted to handle numbers by doing a strto[u]l(),
ignoring the field width, and then repeatedly dividing to extract the
field out of the full converted value. If the string contains a run of
valid digits longer than will fit in a long or long long, this would
overflow and no
On 09/02/21 16:41, Richard Weinberger wrote:
I wonder about the use case.
for example, many existing video applications use mmap() to map the
device memory to userspace memory. Adding support for mmap() to CUSE
would allow these apps to work without any modifications with CUSE-based
On Tue, Feb 09, 2021 at 07:56:30AM +0100, Greg KH wrote:
> On Mon, Feb 08, 2021 at 10:34:51PM -0800, John Hubbard wrote:
> > On 2/8/21 10:27 PM, John Hubbard wrote:
> > > On 2/8/21 10:13 PM, Greg KH wrote:
> > > > On Mon, Feb 08, 2021 at 05:57:17PM -0800, John Hubbard wrote:
> > > > > On 2/8/21
On Thu, Jan 21, 2021 at 02:18:02PM +0800, Irui Wang wrote:
> Updates binding document since the avc and vp8 hardware encoder in
> MT8173 are now separated. Separate "mediatek,mt8173-vcodec-enc" to
> "mediatek,mt8173-vcodec-vp8-enc" and "mediatek,mt8173-vcodec-avc-enc".
This is not a compatible
On Tue, Feb 09, 2021 at 12:45:11PM +, Robin Murphy wrote:
> It's not a bug, it's a fundamental design failure. dma_get_sgtable() has
> only ever sort-of-worked for DMA buffers that come from CMA or regular page
> allocations. In particular, a "no-map" DMA pool is not backed by kernel
>
On Feb 8, 2021, at 04:33, Borislav Petkov wrote:
> On Wed, Dec 23, 2020 at 07:57:05AM -0800, Chang S. Bae wrote:
>> The struct fpu includes two (possible) xstate buffers -- fpu->state and
>> fpu->state_ptr. Instead of open code for accessing one of them, provide a
>> wrapper that covers both
On Mon, Feb 8, 2021 at 5:54 PM Rafael J. Wysocki wrote:
>
> On Mon, Feb 8, 2021 at 5:44 PM Bartosz Golaszewski
> wrote:
> >
> > On Fri, Feb 5, 2021 at 2:25 PM Sakari Ailus
> > wrote:
> > >
> > > In certain use cases (where the chip is part of a camera module, and the
> > > camera module is
On Feb 8, 2021, at 04:33, Borislav Petkov wrote:
> On Wed, Dec 23, 2020 at 07:57:06AM -0800, Chang S. Bae wrote:
>> copy_xregs_to_kernel() used to save all user states in a kernel buffer.
>> When the dynamic user state is enabled, it becomes conditional which state
>> to be saved.
>>
>>
Hello Chengming,
On Tue, Feb 09, 2021 at 03:10:33PM +0800, Chengming Zhou wrote:
> When the current task in a cgroup is in_memstall, the corresponding groupc
> on that cpu is in PSI_MEM_FULL state, so we can exploit that to remove the
> redundant psi_task_tick from scheduler_tick to save this
The following commit has been merged into the sched/core branch of tip:
Commit-ID: b57f3de85c79f9fbfe2fd84cc6ba548e4e73d02d
Gitweb:
https://git.kernel.org/tip/b57f3de85c79f9fbfe2fd84cc6ba548e4e73d02d
Author:Peter Zijlstra
AuthorDate:Fri, 22 Jan 2021 13:01:58 +01:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 0e79823f55de3cff95894fbb40440b17910e7378
Gitweb:
https://git.kernel.org/tip/0e79823f55de3cff95894fbb40440b17910e7378
Author:Peter Zijlstra (Intel)
AuthorDate:Mon, 18 Jan 2021 15:12:23
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 8659343e7612746d595d55e7cf695c46f2ed571a
Gitweb:
https://git.kernel.org/tip/8659343e7612746d595d55e7cf695c46f2ed571a
Author:Josh Poimboeuf
AuthorDate:Wed, 27 Jan 2021 17:18:37 -06:00
On Tue, 09 Feb 2021, Hans de Goede wrote:
> Hi,
>
> On 2/9/21 3:14 PM, Lee Jones wrote:
> > On Mon, 08 Feb 2021, Hans de Goede wrote:
> >
> >> Hi Mark, Lee,
> >>
> >> On 2/4/21 12:24 PM, Hans de Goede wrote:
> >>> Hi all,
> >>>
> >>> Here is v4 of my series to rework the arizona codec
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 355b3a57ddba71b73a99aa249a99aed6ed904606
Gitweb:
https://git.kernel.org/tip/355b3a57ddba71b73a99aa249a99aed6ed904606
Author:Peter Zijlstra
AuthorDate:Mon, 25 Jan 2021 16:26:50 +01:00
On Tue, 9 Feb 2021, Peter Zijlstra wrote:
> Hi!
>
> Implement objtool support for the x86_64 stack swizzle pattern.
>
> This means we can use the minial stack swizzle:
>
> mov %rsp, (%[tos])
> mov %[tos], %rsp
> ...
> pop %rsp
>
> from inline asm, with arbitrary stack setup. The ORC
On Tue, Feb 09, 2021 at 04:07:11PM +0100, Sven Schnelle wrote:
> commit c6bc9bd06dff49fa4c("rbtree, uprobes: Use rbtree helpers") from
> next-20210208 accidentally removed the refcount increase. Add it again.
>
Thanks, and sorry about that!
Extend kvm_s390_shadow_fault to return the pointer to the valid leaf
DAT table entry, or to the invalid entry.
Also return some flags in the lower bits of the address:
DAT_PROT: indicates that DAT protection applies because of the
protection bit in the segment (or, if EDAT, region)
Correctly handle the MVPG instruction when issued by a VSIE guest.
Fixes: a3508fbe9dc6d ("KVM: s390: vsie: initial support for nested
virtualization")
Cc: sta...@vger.kernel.org
Signed-off-by: Claudio Imbrenda
---
arch/s390/kvm/vsie.c | 93 +---
1 file
The current handling of the MVPG instruction when executed in a nested
guest is wrong, and can lead to the nested guest hanging.
This patchset fixes the behaviour to be more architecturally correct,
and fixes the hangs observed.
v2->v3
* improved some comments
* improved some variable and
> a bit OT probably: is there any chance for you to also implement mmap()
> for CUSE? That would be much appreciated.
What exactly do you have in mind? I wonder about the use case.
mmap() between a FUSE server and a client is more or less shared memory in
userspace.
Thanks,
//richard
On Tue, Feb 09, 2021 at 05:32:20PM +0800, Qing Zhang wrote:
> Add DTB boot support, only support LS2K1000 processor for now,
> determine whether to use the built-in DTB or the DTB from the
> firmware by checking the range of CKSEG0 and XKPHYS.
>
> Signed-off-by: Jiaxun Yang
> Signed-off-by: Qing
On Feb 9, 2021, at 04:49, Borislav Petkov wrote:
> On Mon, Feb 08, 2021 at 06:53:23PM +, Bae, Chang Seok wrote:
> Yours does. So drop it from this one and from all the other patches as
> it is causing more confusion than it is trying to dispel.
Okay.
>> I think they are in a different
Hi Yongqiang Niu,
Thank you for your patch.
Missatge de Yongqiang Niu del dia dt., 5
de gen. 2021 a les 4:07:
>
> the mmsys will more and more complicated after support
> more and more SoCs, add an independent folder will be
> more clear
>
> Signed-off-by: Yongqiang Niu
> ---
>
On 04/02/2021 12:27, Leo Yan wrote:
> On Mon, Feb 01, 2021 at 07:40:45PM +0200, James Clark wrote:
>>
>> On 31/01/2021 14:01, Leo Yan wrote:
>>> Option 1: by merging patches 07/08 and 08/08, we can firstly support PID
>>> tracing for root namespace, and later we can extend to support PID
>>>
Fix checkpatch.pl CHECK:
CHECK: Please don't use multiple blank lines
Signed-off-by: Aakash Hemadri
---
This is my first patch.
Done as a part of the linux-kernel-mentees program and as the 10th task
on eudyptula to fix style checks.
drivers/staging/rtl8712/rtl871x_debug.h | 2 --
1 file
On Mon, Feb 8, 2021 at 19:35:16, Bjorn Helgaas
wrote:
> [+cc Krzysztof]
>
> From reading the subject, I thought you were adding a function to
> check the return values, i.e., a "checker." But you're really adding
> "checks" :)
That's true, I will rework the subject.
>
> On Wed, Feb 03,
Only export MTE symbols when KASAN-KUnit tests are enabled.
Signed-off-by: Andrey Konovalov
---
Andrew, please squash this into:
"arm64: kasan: export MTE symbols for KASAN tests"
---
arch/arm64/kernel/mte.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/kernel/mte.c
On Tue, Feb 02, 2021 at 04:12:31PM +0800, Hsin-Yi Wang wrote:
> From: Yongqiang Niu
>
> This patch add component POSTMASK.
>
> Signed-off-by: Yongqiang Niu
> Signed-off-by: Hsin-Yi Wang
> Reviewed-by: CK Hu
> ---
[ ... ]
>
> +void mtk_postmask_config(struct device *dev, unsigned int w,
Hello,
On Tue, Feb 09, 2021 at 02:17:19PM +0100, Odin Ugedal wrote:
> A am not that familiar how cross subsystem patches like these are handled, but
> I am still adding the Tejun Heo (cgroup maintainer) as a CC. Should maybe cc
> to
> cgroup@ as well?
Yeah, that'd be great. Given that it's
On Mon, Feb 8, 2021 at 22:53:54, Krzysztof Wilczyński
wrote:
> [+cc Bjorn]
>
> Hi Gustavo,
>
> [...]
> > Thanks for your review. I will wait for a couple of days, before sending
> > a new version of this patch series based on your feedback.
>
> Thank you!
>
> There might be one more
On Fri, 22 Jan 2021, Matti Vaittinen wrote:
> BD9573 and BD9576 support set of "protection" interrupts for "fatal"
> issues. Those lead to SOC reset as PMIC shuts the power outputs. Thus
> there is no relevant IRQ handling for them.
>
> Few "detection" interrupts were added to the BD9576 with
On Tue, Feb 9, 2021 at 4:10 PM Luca Risolia
wrote:
>
> Hi guys,
>
> a bit OT probably: is there any chance for you to also implement mmap()
> for CUSE? That would be much appreciated.
That's an old one.
No, I don't have plans, but patches are welcome, of course.
Thanks,
Miklos
On Sat, Feb 06, 2021 at 07:50:10PM +0100, Johan Jonker wrote:
> In the past Rockchip dwc3 usb nodes were manually checked.
> With the conversion of snps,dwc3.yaml as common document
> we now can convert rockchip,dwc3.txt to yaml as well.
> Remove node wrapper.
>
> Added properties for rk3399 are:
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 0fcc7c20d2e2a65fb5b80d42841084e8509d085d
Gitweb:
https://git.kernel.org/tip/0fcc7c20d2e2a65fb5b80d42841084e8509d085d
Author:Mikael Beckius
AuthorDate:Thu, 28 Jan 2021 15:02:08 +01:00
; arch/arm/mach-at91/pm.c:{ .compatible = "atmel,sama5d2-pmc",
> .data = _infos[1] },
> drivers/clk/at91/pmc.c: { .compatible = "atmel,sama5d2-pmc" },
> drivers/clk/at91/sama5d2.c:CLK_OF_DECLARE_DRIVER(sama5d2_pmc,
> "atmel,sama5d2-pmc", sama5d2_pmc_setup);
>
From: Vladimir Oltean
The chip can configure unicast flooding, broadcast flooding and learning.
Learning is per port, while flooding is per {ingress, egress} port pair
and we need to configure the same value for all possible ingress ports
towards the requested one.
While multicast flooding is
From: Vladimir Oltean
In preparation of offloading the bridge port flags which have
independent settings for unknown multicast and for broadcast, we should
also start reserving one destination Port Group ID for the flooding of
broadcast packets, to allow configuring it individually.
From: Vladimir Oltean
We should not be unconditionally enabling address learning, since doing
that is actively detrimential when a port is standalone and not offloading
a bridge. Namely, if a port in the switch is standalone and others are
offloading the bridge, then we could enter a situation
From: Vladimir Oltean
Now that br_switchdev_set_port_flag is never called from under br->lock,
it runs in sleepable context.
All switchdev drivers handle SWITCHDEV_PORT_ATTR_SET as both blocking
and atomic, so no changes are needed on that front.
Signed-off-by: Vladimir Oltean
---
Changes in
From: Vladimir Oltean
The bridge offloads the port flags through a single bit mask using
switchdev, which among others, contains learning and flooding settings.
The commit 57652796aa97 ("net: dsa: add support for bridge flags")
missed one crucial aspect of the
From: Vladimir Oltean
With the bridge driver doing that for us now, we can simplify our
mid-layer logic a little bit, which would have otherwise needed some
tuning for the disabling of address learning that is necessary in
standalone mode.
Signed-off-by: Vladimir Oltean
---
Changes in v2:
From: Vladimir Oltean
There does not appear to be any strong reason why
br_switchdev_set_port_flag issues a separate notification for checking
the supported brport flags rather than just attempting to apply them and
propagating the error if that fails.
However, there is a reason why this
From: Vladimir Oltean
It must first be admitted that switchdev device drivers have a life
beyond the bridge, and when they aren't offloading the bridge driver
they are operating with forwarding disabled between ports, emulating as
closely as possible N standalone network interfaces.
Now it must
From: Vladimir Oltean
Currently br_switchdev_set_port_flag has two options for error handling
and neither is good:
- The driver returns -EOPNOTSUPP in PRE_BRIDGE_FLAGS if it doesn't
support offloading that flag, and this gets silently ignored and
converted to an errno of 0. Nobody does this.
From: Vladimir Oltean
The br_switchdev_set_port_flag function uses the atomic notifier call
chain because br_setport runs in an atomic section (under br->lock).
This is because port flag changes need to be synchronized with the data
path. But actually the switchdev notifier doesn't need that,
From: Vladimir Oltean
The initial goal of this series was to have better support for
standalone ports mode and multiple bridges on the DSA drivers like
ocelot/felix and sja1105. Proper support for standalone mode requires
disabling address learning, which in turn requires interaction with the
801 - 900 of 1488 matches
Mail list logo
