On 2020-06-02T15:01:14+02:00 SeongJae Park wrote:
> From: SeongJae Park
>
> At the beginning of the monitoring, DAMON constructs the initial regions
> by evenly splitting the memory mapped address space of the process into
> the user-specified minimal number of regions. In this initial state,
Define precisely the size of the user accessible virtual space size
for sv32/39/48 mmu types and explain why the whole virtual address
space is split into 2 equal chunks between kernel and user space.
Signed-off-by: Alexandre Ghiti
Reviewed-by: Anup Patel
Reviewed-by: Palmer Dabbelt
---
Now that the mmu type is determined at runtime using SATP
characteristic, use the global variable pgtable_l4_enabled to output
mmu type of the processor through /proc/cpuinfo instead of relying on
device tree infos.
Signed-off-by: Alexandre Ghiti
Reviewed-by: Anup Patel
Reviewed-by: Palmer
This is made possible by using the mmu-type property of the cpu node of
the device tree.
By default, the kernel will boot with 4-level page table if the hw supports
it but it can be interesting for the user to select 3-level page table as
it is less memory consuming and faster since it requires
By adding a new 4th level of page table, give the possibility to 64bit
kernel to address 2^48 bytes of virtual address: in practice, that roughly
offers ~160TB of virtual address space to userspace and allows up to 64TB
of physical memory.
If the underlying hardware does not support sv48, we will
The Jitter RNG is unconditionally allocated as a seed source follwoing
the patch 97f2650e5040. Thus, the instance must always be deallocated.
Reported-by: syzbot+2e635807decef724a...@syzkaller.appspotmail.com
Fixes: 97f2650e5040 ("crypto: drbg - always seeded with SP800-90B ...")
Signed-off-by:
This is a preparatory patch for sv48 support that will introduce
dynamic PAGE_OFFSET.
Dynamic PAGE_OFFSET implies that all zones (vmalloc, vmemmap, fixaddr...)
whose addresses depend on PAGE_OFFSET become dynamic and can't be used
to statically initialize the array used by ptdump to identify the
Either the user specifies maximum physical memory size of 2GB or the
user lives with the system constraint which is 1/4th of maximum
addressable memory in Sv39 MMU mode (i.e. 128GB) for now.
Signed-off-by: Alexandre Ghiti
Reviewed-by: Anup Patel
---
arch/riscv/Kconfig | 20 ++--
Em Wed, 3 Jun 2020 12:46:46 +1000
Hi Stephen,
Stephen Rothwell escreveu:
> Hi all,
>
> After merging the v4l-dvb-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/media/atomisp/pci/atomisp_compat_css20.c: In function
> 'atomisp_css_isr_thread':
With 4-level page table folding at runtime, we don't know at compile time
the size of the virtual address space so we must set VA_BITS dynamically
so that sparsemem reserves the right amount of memory for struct pages.
Signed-off-by: Alexandre Ghiti
---
arch/riscv/Kconfig | 10
There is no need to compare at compile time MAX_EARLY_MAPPING_SIZE value
with PGDIR_SIZE since MAX_EARLY_MAPPING_SIZE is set to 128MB which is less
than PGDIR_SIZE that is equal to 1GB: that allows to simplify early_pmd
definition.
Signed-off-by: Alexandre Ghiti
Reviewed-by: Anup Patel
A recent commit added new variables only used if CONFIG_NETDEVICES is
set. A simple fix is to only declare these variables if the same
condition is valid.
Other solutions could be to move the code related to SO_BINDTODEVICE
option from _bpf_setsockopt() function to a dedicated one or only
declare
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
Convert vhost net to use the new format-agnostic API.
In particular, don't poke at vq internals such as the
heads array.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/net.c | 153 +++-
1 file
This patchset implements sv48 support at runtime. The kernel will try to
boot with 4-level page table and will fallback to 3-level if the HW does not
support it.
On Wed 2020-06-03 12:52:14, Sumit Garg wrote:
> While rounding up CPUs via NMIs, its possible that a rounded up CPU
> maybe holding a console port lock leading to kgdb master CPU stuck in
> a deadlock during invocation of console write operations. A similar
> deadlock could also be possible while
On Wed 2020-06-03 12:52:13, Sumit Garg wrote:
> Check if a console is enabled prior to invoking corresponding write
> handler.
>
> Suggested-by: Sergey Senozhatsky
> Signed-off-by: Sumit Garg
> Reviewed-by: Daniel Thompson
> Reviewed-by: Douglas Anderson
Reviewed-by: Petr Mladek
Best
From: Al Viro On Behalf Of Al Viro
> Sent: 02 June 2020 22:58
> On Tue, Jun 02, 2020 at 08:41:38PM +, David Laight wrote:
>
> > In which case you need a 'user_access_begin' that takes the mm
> > as an additional parameter.
>
> What does any of that have to do with mm? Details,
Hi, Christoph Hellwig, folks,
i just writing a driver for stm32f4's dma2d controller(/dev/video0
v4l2-m2m device), got following mmap -6 error
(No such device or address) at user space.
working environment is:
hardware: stm32f469-disco board, ARM Cortex-M4 up to 180MHz with FPU,
ArmV7M, no
On Tue, 2 Jun 2020 at 20:14, James Bottomley wrote:
>
> On Tue, 2020-06-02 at 19:48 +0530, Sumit Garg wrote:
> > Add support for TEE based trusted keys where TEE provides the
> > functionality to seal and unseal trusted keys using hardware unique
> > key. Also, this is an alternative in case
On Wed 2020-06-03 12:52:12, Sumit Garg wrote:
> Re-factor kdb_printf() message write code in order to avoid duplication
> of code and thereby increase readability.
>
> Signed-off-by: Sumit Garg
> Reviewed-by: Douglas Anderson
Revieved-by: Petr Mladek
Best Regards,
Petr
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
mm/gup.c
between commit:
17839856fd58 ("gup: document and work around "COW can break either way"
issue")
from Linus' tree and (at least) commits:
d7f76db8e4ad ("mm/gup: move __get_user_pages_fast() down a few
Relocating kernel at runtime is done very early in the boot process, so
it is not convenient to check for relocations there and react in case a
relocation was not expected.
There exists a script in scripts/ that extracts the relocations from
vmlinux that is then used at postlink to check the
Since commit 8ec59c0f5f49 ("sched/topology: Remove unused 'sd'
parameter from arch_scale_cpu_capacity()") it is no longer needed.
Signed-off-by: Dietmar Eggemann
---
kernel/sched/fair.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c
Relocating kernel at runtime is done very early in the boot process, so
it is not convenient to check for relocations there and react in case a
relocation was not expected.
Powerpc architecture has a script that allows to check at compile time
for such unexpected relocations: extract the common
The idle task and stop task sched_classes return 0 in this function.
The single call site in sched_rr_get_interval() calls
p->sched_class->get_rr_interval() only conditional in case it is
defined. Otherwise time_slice=0 will be used.
The deadline sched class does not define it. Commit
Remove redundant functions, parameters and macros from the task
scheduler code.
Dietmar Eggemann (4):
sched/pelt: Remove redundant cap_scale() definition
sched/core: Remove redundant 'preempt' param from
sched_class->yield_to_task()
sched/idle,stop: Remove .get_rr_interval from
Besides in PELT cap_scale() is used in the Deadline scheduler class for
scale-invariant bandwidth enforcement.
Remove the cap_scale() definition in kernel/sched/pelt.c and keep the
one in kernel/sched/sched.h.
Signed-off-by: Dietmar Eggemann
---
kernel/sched/pelt.c | 2 --
1 file changed, 2
Commit 6d1cafd8b56e ("sched: Resched proper CPU on yield_to()") moved
the code to resched the CPU from yield_to_task_fair() to yield_to()
making the preempt parameter in sched_class->yield_to_task()
unnecessary. Remove it. No other sched_class implements yield_to_task().
Signed-off-by: Dietmar
This config allows to compile the kernel as PIE and to relocate it at
any virtual address at runtime: this paves the way to KASLR and to 4-level
page table folding at runtime. Runtime relocation is possible since
relocation metadata are embedded into the kernel.
Note that relocating at runtime
This is a preparatory patch for relocatable kernel.
The kernel used to be linked at PAGE_OFFSET address and used to be loaded
physically at the beginning of the main memory. Therefore, we could use
the linear mapping for the kernel mapping.
But the relocated kernel base address will be different
On Wed, 2020-06-03 at 08:40 +0100, Marc Zyngier wrote:
> On 2020-06-03 08:29, Neal Liu wrote:
> > On Tue, 2020-06-02 at 21:02 +0800, Marc Zyngier wrote:
> >> On 2020-06-02 13:14, Ard Biesheuvel wrote:
> >> > On Tue, 2 Jun 2020 at 10:15, Neal Liu wrote:
> >> >>
> >> >> These patch series introduce
This patchset originally implemented relocatable kernel support but now
also moves the kernel mapping into the vmalloc zone.
The first patch explains why we need to move the
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
Add a new API that doesn't assume used ring, heads, etc.
For now, we keep the old APIs around to make it easier
to convert drivers.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/vhost.c | 52 ++-
On Wed, Jun 3, 2020 at 3:51 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the overlayfs tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "security_file_ioctl" [fs/overlayfs/overlay.ko] undefined!
>
> Caused by commit
>
> b5940870e166 ("ovl:
On Tue, 2 Jun 2020 at 22:48, Paul E. McKenney wrote:
>
> On Tue, Jun 02, 2020 at 04:36:33PM +0200, Marco Elver wrote:
> > Instead of __no_kcsan_or_inline, prefer '__no_kcsan inline' in test --
> > this is in case we decide to remove __no_kcsan_or_inline.
> >
> > Suggested-by: Peter Zijlstra
> >
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
drivers/gpu/drm/i915/gem/i915_gem_userptr.c
between commit:
17839856fd58 ("gup: document and work around "COW can break either way"
issue")
from Linus' tree and commit:
bca3ecd3b92c ("drm/i915: convert
On 02-06-20, 11:34, Xiongfeng Wang wrote:
> Hi Viresh,
>
> Sorry to disturb you about another problem as follows.
>
> CPPC use the increment of Desired Performance counter and Reference
> Performance
> counter to get the CPU frequency and show it in sysfs through
> 'cpuinfo_cur_freq'. But ACPI
On Wed, 3 Jun 2020 at 09:34, Benjamin GAIGNARD wrote:
>
>
>
> On 6/2/20 3:35 PM, Valentin Schneider wrote:
> > On 02/06/20 12:37, Benjamin GAIGNARD wrote:
> >> On 6/2/20 11:31 AM, Valentin Schneider wrote:
> @@ -99,6 +100,8 @@ enum state {
>
> #define OVERRUN_ERROR_THRESHOLD 3
>
Commit 130f4caf145c ("libata: Ensure ata_port probe has completed before
detach") may cause system freeze during suspend.
Using async_synchronize_full() in PM callbacks is wrong, since async
callbacks that are already scheduled may wait for not-yet-scheduled
callbacks, causes a circular
On 6/3/2020 9:10 AM, Sean Christopherson wrote:
On Fri, May 29, 2020 at 04:55:43PM +0800, Xiaoyao Li wrote:
Split the part of updating KVM states from kvm_update_cpuid(), and put
it into a new kvm_update_state_based_on_cpuid(). So it's clear that
kvm_update_cpuid() is to update guest CPUID
On 02/06/2020 11:24, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.6.16 release.
> There are 174 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.
>
> Responses
On Tue, Jun 02, 2020 at 05:36:11PM +0100, Jon Hunter wrote:
>
> On 02/06/2020 11:23, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.183 release.
> > There are 76 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Jun 02, 2020 at 12:13:56PM -0700, Guenter Roeck wrote:
> On Tue, Jun 02, 2020 at 12:24:19PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.6.16 release.
> > There are 174 patches in this series, all will be posted as a response
> > to this one.
On Wed, Jun 03, 2020 at 11:42:48AM +0530, Naresh Kamboju wrote:
> On Tue, 2 Jun 2020 at 23:44, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.9.226 release.
> > There are 55 patches in this series, all will be posted as a response
> > to this one. If
On Wed, Jun 3, 2020 at 9:18 AM Thomas Zimmermann wrote:
>
> Hi
>
> Am 02.06.20 um 23:56 schrieb Linus Torvalds:
> > On Tue, Jun 2, 2020 at 2:21 PM Linus Torvalds
> > wrote:
> >>
> >> I'm still working through the rest of the merge, so far that was the
> >> only one that made me go "Whaa?".
> >
>
Hi all,
After merging the ftrace tree, today's linux-next build (htmldocs)
failed like this:
Sphinx parallel build error:
docutils.utils.SystemMessage:
/home/sfr/next/next/Documentation/trace/histogram-design.rst:219: (SEVERE/4)
Unexpected section title.
.
.
Caused by commit
16b585fe7192
On 2020-06-03 08:29, Neal Liu wrote:
On Tue, 2020-06-02 at 21:02 +0800, Marc Zyngier wrote:
On 2020-06-02 13:14, Ard Biesheuvel wrote:
> On Tue, 2 Jun 2020 at 10:15, Neal Liu wrote:
>>
>> These patch series introduce a security random number generator
>> which provides a generic interface to
在 2020/6/1 上午2:35, Lukas Bulwahn 写道:
> Documentation generation warns:
>
> Documentation/translations/zh_CN/filesystems/debugfs.rst:5:
> WARNING: undefined label: debugfs_index
It's due to debugfs.txt changed to debugfs.rst.
>
> Use doc reference for files rather than introducing a
On 2020-06-02 18:37, Robin Murphy wrote:
On 2020-05-26 08:19, gup...@codeaurora.org wrote:
On 2020-05-22 14:54, Robin Murphy wrote:
On 2020-05-22 07:25, gup...@codeaurora.org wrote:
On 2020-05-22 01:46, Robin Murphy wrote:
On 2020-05-21 12:30, Prakash Gupta wrote:
Sorry for delayed
Hi Adrian,
On Wed, Jun 3, 2020 at 9:20 AM John Paul Adrian Glaubitz
wrote:
> On 5/31/20 12:47 PM, John Paul Adrian Glaubitz wrote:
> > Changes since v1:
> > - Replace single mov instruction for exception handling
> >in case of invalid load
>
> Yutaka Niibe has had a look at my patch and he
Hi Geert,
Geert Uytterhoeven 於 2020/6/3 下午 03:13 寫道:
Hi Ji-Ze,
If devres_head is not empty, you have a serious problem on your system,
as those resources may be in an unknown state (e.g. freed but still in
use). While I had missed the probe_count imbalance when implementing
the original
On 6/2/20 3:35 PM, Valentin Schneider wrote:
> On 02/06/20 12:37, Benjamin GAIGNARD wrote:
>> On 6/2/20 11:31 AM, Valentin Schneider wrote:
@@ -99,6 +100,8 @@ enum state {
#define OVERRUN_ERROR_THRESHOLD 3
+#define DCMI_MIN_FREQ 65 /* in KHz */
+
>>> This
On 6/3/20 9:27 AM, John Paul Adrian Glaubitz wrote:
> On 6/2/20 3:33 AM, Rich Felker wrote:
>> Hmm, it looks like Andrew Morton just pulled most of these into -mm,
>> apparently independently of me getting them in my for-next a few hours
>> ago, since his versions lack my signed-off-by. That's ok
On 02/06/2020 11:23, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.126 release.
> There are 92 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.
>
> Responses
On 02/06/2020 11:24, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.44 release.
> There are 139 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.
>
> Responses
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
Return code of fetch_buf is confusing, so callers resort to
tricks to get to sane values. Let's switch to something standard:
0 empty, >0 non-empty, <0 error.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/vhost.c | 24
On Tue, 2020-06-02 at 21:02 +0800, Marc Zyngier wrote:
> On 2020-06-02 13:14, Ard Biesheuvel wrote:
> > On Tue, 2 Jun 2020 at 10:15, Neal Liu wrote:
> >>
> >> These patch series introduce a security random number generator
> >> which provides a generic interface to get hardware rnd from Secure
>
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
With this patch applied, new and old code perform identically.
Lots of extra optimizations are now possible, e.g.
we can fetch multiple heads with copy_from/to_user now.
We can get rid of maintaining the log array. Etc etc.
Signed-off-by:
Hi Rich!
On 6/2/20 3:33 AM, Rich Felker wrote:
> Hmm, it looks like Andrew Morton just pulled most of these into -mm,
> apparently independently of me getting them in my for-next a few hours
> ago, since his versions lack my signed-off-by. That's ok though, as
> long as they go up. Some details
On Tue Jun 02 20, Joerg Roedel wrote:
Hi,
two small patches to move the Intel and AMD IOMMU drivers into their own
subdirectory under drivers/iommu/ to make the file structure a bit less
cluttered.
Regards,
Joerg
Joerg Roedel (2):
iommu/amd: Move AMD IOMMU driver into subdirectory
Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for
subscribing to the service. It has been a long time we use both kbuild test
robot and kernel test robot to send out report. From now on, we want to
combine two mails to kernel test robot, which is a single voice for the
Re-factor kdb_printf() message write code in order to avoid duplication
of code and thereby increase readability.
Signed-off-by: Sumit Garg
Reviewed-by: Douglas Anderson
---
kernel/debug/kdb/kdb_io.c | 57 +++
1 file changed, 28 insertions(+), 29
In kgdb context, calling console handlers aren't safe due to locks used
in those handlers which could in turn lead to a deadlock. Although, using
oops_in_progress increases the chance to bypass locks in most console
handlers but it might not be sufficient enough in case a console uses
more locks
While rounding up CPUs via NMIs, its possible that a rounded up CPU
maybe holding a console port lock leading to kgdb master CPU stuck in
a deadlock during invocation of console write operations. A similar
deadlock could also be possible while using synchronous breakpoints.
So in order to avoid
On 2 June 2020 11:03:03 PM IST, Amit Singh Tomar wrote:
>At the moment, Driver uses bit fields to describe registers of the DMA
>descriptor structure that makes it less portable and maintainable, and
>Andre suugested(and even sketched important bits for it) to make use of
>array to describe
Check if a console is enabled prior to invoking corresponding write
handler.
Suggested-by: Sergey Senozhatsky
Signed-off-by: Sumit Garg
Reviewed-by: Daniel Thompson
Reviewed-by: Douglas Anderson
---
kernel/debug/kdb/kdb_io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git
This patch-set is aimed to improve console handling especially when kdb
operates in NMI context.
Brief description of enhancements:
- Add status check for console prior to invoking corresponding handler.
- Fixup to avoid possible deadlock in NMI context due to usage of locks
in the console
Hi!
On 5/31/20 12:47 PM, John Paul Adrian Glaubitz wrote:
> Changes since v1:
> - Replace single mov instruction for exception handling
>in case of invalid load
Yutaka Niibe has had a look at my patch and he says, we might have to add
an entry for the fault handling of the upper word.
Hi
Am 02.06.20 um 23:56 schrieb Linus Torvalds:
> On Tue, Jun 2, 2020 at 2:21 PM Linus Torvalds
> wrote:
>>
>> I'm still working through the rest of the merge, so far that was the
>> only one that made me go "Whaa?".
>
> Hmm. I'm also ending up effectively reverting the drm commit
>
On Fri, May 29, 2020 at 5:38 AM Zhe Li wrote:
>
> Recently I find a bug that I get nothing with shell
> command "ls". The test steps are listed below.
> 1. cd $JFFS2_MOUNT_DIR
> 2. touch file
> 3. ls
>
> Finally I find that when command "ls" going into
> function jffs2_readdir(), it get non-zero
On Tue, Jun 02, 2020 at 04:35:33PM -0400, Kyungtae Kim wrote:
> We report a bug (in linux-5.6.11) found by FuzzUSB (a modified version
> of syzkaller)
>
> This bug happened when accessing a deallocated instance in printer_read().
>
> printer_read() tries to access lock_printer_io of the
Signed-off-by: kbuild test robot
---
contiguous.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c
index 4b10d0ca0456d..2094c8e0590ac 100644
--- a/kernel/dma/contiguous.c
+++ b/kernel/dma/contiguous.c
@@ -37,7 +37,7 @@
On Tue, Jun 02, 2020 at 04:36:22PM -0400, Kyungtae Kim wrote:
> We report a bug (in linux-5.6.11) found by FuzzUSB (a modified version
> of syzkaller)
>
> The buf of an usbtest_dev instance (dev->buf) allocated in
> usbtest_probe() leaked.
>
> The usbtest_dev instance holding the buf is attached
From: SeongJae Park
This commit documents DAMON-based operation schemes in the DAMON
document.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/guide.rst | 35 +
Documentation/admin-guide/mm/damon/usage.rst | 127 +--
2 files changed, 152 insertions(+),
From: SeongJae Park
This commit implements 'schemes' subcommand of the damon userspace tool.
It can be used to describe and apply the data access monitoring-based
operation schemes in more human friendly fashion.
Signed-off-by: SeongJae Park
---
tools/damon/_convert_damos.py | 128
From: SeongJae Park
This commit adds simple selftets for 'schemes' debugfs file of DAMON.
Signed-off-by: SeongJae Park
---
.../testing/selftests/damon/debugfs_attrs.sh | 29 +++
1 file changed, 29 insertions(+)
diff --git a/tools/testing/selftests/damon/debugfs_attrs.sh
From: SeongJae Park
To tune the DAMON-based operation schemes, knowing how many and how
large regions are affected by each of the schemes will be helful. Those
stats could be used for not only the tuning, but also monitoring of the
working set size and the number of regions, if the scheme does
On 2020/6/2 下午9:05, Michael S. Tsirkin wrote:
As testing shows no performance change, switch to that now.
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Link: https://lore.kernel.org/r/20200401183118.8334-3-epere...@redhat.com
Signed-off-by: Michael S. Tsirkin
---
From: SeongJae Park
In many cases, users might use DAMON for simple data access aware
memory management optimizations such as applying an operation scheme to
a memory region of a specific size having a specific access frequency
for a specific time. For example, "page out a memory region larger
From: SeongJae Park
This commit implements a debugfs interface for the data access
monitoring oriented memory management schemes. It is supposed to be
used by administrators and/or privileged user space programs. Users can
read and update the rules using ``/damon/schemes`` file. The
format
From: SeongJae Park
DAMON can be used as a primitive for data access pattern aware memory
management optimizations. However, users who want such optimizations
should run DAMON, read the monitoring results, analyze it, plan a new
memory management scheme, and apply the new scheme by themselves.
On 2020/6/2 下午9:05, Michael S. Tsirkin wrote:
The idea is to support multiple ring formats by converting
to a format-independent array of descriptors.
This costs extra cycles, but we gain in ability
to fetch a batch of descriptors in one go, which
is good for code cache locality.
When used,
Hi Ji-Ze,
On Wed, Jun 3, 2020 at 8:45 AM Ji-Ze Hong (Peter Hong) wrote:
> In previous patch, using return -EBUSY in really_probe() instead WARN_ON()
> only. The following is the partial code.
>
> ...
> atomic_inc(_count);
> pr_debug("bus: '%s': %s: probing driver %s with
Once PR_SPEC_FORCE_DISABLE is set, users cannot set PR_SPEC_ENABLE.
This commit checks whether PR_SPEC_FORCE_DISABLE was previously set.
Signed-off-by: Kenta Tada
---
arch/x86/kernel/cpu/bugs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/kernel/cpu/bugs.c
From: SeongJae Park
This commit exports 'do_madvise()' to external GPL modules, so that
other modules including DAMON could use the function.
Signed-off-by: SeongJae Park
---
mm/madvise.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/madvise.c b/mm/madvise.c
index
From: SeongJae Park
DAMON[1] can be used as a primitive for data access awared memory management
optimizations. For that, users who want such optimizations should run DAMON,
read the monitoring results, analyze it, plan a new memory management scheme,
and apply the new scheme by themselves.
[resend; because of missing cc]
Remove Andreas Werner as Maintainer of the F21 BMC driver, as he is no
longer with the company and add Andreas Geissler as additional
Maintainer for all MEN Hardware.
Acked-by: Johannes Thumshirn
Acked-by: Andreas Werner
Signed-off-by: AGeissler
---
Oh, thanks for notification!
2020년 6월 3일 (수) 오후 3:59, Chao Yu 님이 작성:
>
> On 2020/6/1 11:03, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > Found a new segemnt allocation without f2fs_lock_op() in
> > expand_inode_data(). So, when we do fallocate() for a pinned file
> > and trigger checkpoint
On Thu, Apr 23, 2020 at 4:58 AM Zhe Li wrote:
>
> Mounting jffs2 on nand flash will get message "failed: I/O error"
> with the steps listed below.
> 1.erase nand flash
> 2.mount jffs2 on it (this mounting operation will be successful)
> 3.do chown or chmod to the mount point directory
> 4.umount
There are some parameters that are different between
isp2400 and isp2401. None of those are actually used.
So, get rid of them.
Signed-off-by: Mauro Carvalho Chehab
---
.../hrt/isp2400_mamoiada_params.h | 20 +--
.../atomisp/pci/isp2401_mamoiada_params.h | 20
There are lots of mess with IRQ ifdef settings. As the
*_global.h will already detect the type of IRQ system at
compile time, we can get rid of them, replacing by just
one ifdef for ISP2401.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/isp_global.h | 10 ++
If the sensor doesn't implement support for g_frame_interval,
it won't return the expected fps rate.
Instead of keeping DFS on its minimal value (which will likely
not work), set it to the max.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 8
- Get rid of typedefs;
- Get rid of a duplicated enum type with different names for
ISP2400 and ISP2401;
- adjust indentation on the touched code.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/host/irq.c| 29 +--
The logic which sets the hpll_freq for BYT sets hpll_freq
to 1600MHz, but ignores it, and sets it again after reading
from-device-specific EFI vars (this time, using a default
of 2000MHz).
Remove the first set, as this will be overriden anyway.
While here, do minor adjustments on comments and on
There are several parts of the driver that could produce
a "dfs failed!" message. Change the texts, in order to help
identifying from where they're coming.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 4 ++--
Instead of hardcoding the intel family values there, use
the already defined ones from asm/intel-family.h.
Signed-off-by: Mauro Carvalho Chehab
---
.../media/atomisp/include/linux/atomisp_platform.h | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
The contents of hive_isp_css_2401_irq_types_hrt.h and
hive_isp_css_common/irq_global.h are identical, except for
one unused enum:
On isp2401, this IRQ line has this name:
hrt_isp_css_irq_is2401 = HIVE_GP_DEV_IRQ_ISP_PMEM_ERROR_BIT_ID,
While the same bit is named as:
As both isp2400 and isp2401 files are identical, remove one
of them and remove the test for ISP variant.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/isp_global.h | 6 +-
.../atomisp/pci/isp2401_mamoiada_params.h | 211 --
Instead of having a static var to detect it, let's use the
already-existing arch-specific bytes, as this is how other
parts of the code also checks when it needs to do something
different, depending on an specific chipset version.
Signed-off-by: Mauro Carvalho Chehab
---
1001 - 1100 of 1155 matches
Mail list logo
