On 2020-12-15 11:47, Tomasz Figa wrote:
On Tue, Dec 15, 2020 at 8:16 PM Stanimir Varbanov
wrote:
Hi,
Cc: Robin
On 12/14/20 2:57 PM, Alexandre Courbot wrote:
This driver uses the SG vb2 ops, but effectively only ever accesses the
first entry of the SG table, indicating that it expects a
On Tue 08-12-20 12:18:42, Muchun Song wrote:
> The unit of NR_ANON_THPS is HPAGE_PMD_NR. Convert the NR_ANON_THPS
> account to pages.
This changelog could benefit from some improvements. First of all you
should be clear about the motivation. I believe the previous feedback
was also to explicitly
On Tue, Dec 15, 2020 at 05:45:59PM +0530, Vidya Sagar wrote:
> Thanks Mian for bringing it to our notice.
> Have you tried removing the dw_pcie_setup_rc(pp); call from pcie-tegra194.c
> file on top of linux-next? and does that solve the issue?
>
> diff --git
ux-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers?h=next-20201215=d3795d6321ecaa55d94dc24c3b1e3cce608aabd6
Coming to there from my for-next branch - it's also already been sent in
a pull request to Linus so will hopefully be hitting his tree soonish.
s
On 12/14/2020 20:40, Mark Pearson wrote:
Thanks Hans
On 14/12/2020 13:31, Mark Pearson wrote:
*From:* Hans de Goede
*Sent:* December 14, 2020 13:24
*To:* Mario Limonciello ; Jeff Kirsher
; Tony Nguyen ;
The time to finish a xhci_handshake() is platform specific
and sometimes during suspend resume test the followng
errors were encountered:
[53455.418330] ACPI: Waking up from system sleep state S4
[66838.490856] xhci_hcd :00:14.0: xHCI dying, ignoring interrupt.
Shouldn't IRQs be
On Thu, Dec 03, 2020 at 08:32:52PM +0800, Tiezhu Yang wrote:
> In the current code, we can not build under !CONFIG_NUMA and !CONFIG_SMP
> on the Loongson64 platform, it seems bad for the users who just want to
> use pure single core (not nosmp) to debug, so do the following things to
> give them a
commit/drivers?h=next-20201215=d3795d6321ecaa55d94dc24c3b1e3cce608aabd6
Regards,
Fabio Estevam
The pf8x00 driver supports three devices, the DT compatible strings
and I2C IDs should enumerate these specifically rather than using a
wildcard so that we don't collide with anything incompatible in the
same ID range in the future and so that we can handle any software
visible differences between
Hi Yanan,
On 2020-12-14 07:20, wangyanan (Y) wrote:
diff --git a/arch/arm64/kvm/hyp/pgtable.c
b/arch/arm64/kvm/hyp/pgtable.c
index a74a62283012..e3c6133567c4 100644
--- a/arch/arm64/kvm/hyp/pgtable.c
+++ b/arch/arm64/kvm/hyp/pgtable.c
@@ -45,6 +45,10 @@
#define KVM_PTE_LEAF_ATTR_HI_S2_XN
Le mar. 15 déc. 2020 à 14:06, Mark Brown a écrit :
>
> On Mon, Dec 14, 2020 at 11:58:49PM +0100, Adrien Grassein wrote:
>
> > this set of patch intends to add the support of the pf8x00 PMIC
> > regulators. This family of PMIC contains 12 regulators (7 bucks
> > converters, 4 LDO, 1 RTC supply).
On 2020/12/15 2:58, Eric Farman wrote:
>
>
> On 12/10/20 8:56 AM, xuxiaoyang (C) wrote:
>>
>>
>> On 2020/12/9 22:42, Eric Farman wrote:
>>>
>>>
>>> On 12/9/20 6:54 AM, Cornelia Huck wrote:
On Tue, 8 Dec 2020 21:55:53 +0800
"xuxiaoyang (C)" wrote:
> On 2020/11/21 15:58,
My employment with TI is coming to an end, add the copyright and author comments
as they due and change the maintainer mail address.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Peter Ujfalusi
---
Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml | 4 +++-
Hi,
My TI address is going to bounce after Friday (18.12.2020), switch my address to
my private one for now.
Regards,
Peter
---
Peter Ujfalusi (2):
MAINTAINERS: Add entry for Texas Instruments DMA drivers
dt-bindings: dma: ti: Update maintainer and author information
My employment with TI is coming to an end, it is my intention to look after
the DMA drivers I have worked with over the years.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Peter Ujfalusi
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS
On Tue, Dec 15, 2020 at 1:40 AM Bjorn Helgaas wrote:
>
> On Mon, Dec 14, 2020 at 11:56:31PM +0100, Ian Kumlien wrote:
> > On Mon, Dec 14, 2020 at 8:19 PM Bjorn Helgaas wrote:
>
> > > If you're interested, you could probably unload the Realtek drivers,
> > > remove the devices, and set the
On Mon, 2020-12-14 at 22:08 +0200, Grygorii Strashko wrote:
>
> On 14/12/2020 10:48, Qii Wang wrote:
> > On Thu, 2020-12-10 at 15:03 +0200, Grygorii Strashko wrote:
> >>
> >> On 10/12/2020 03:56, Qii Wang wrote:
> >>> On Mon, 2020-12-07 at 18:35 +0200, Grygorii Strashko wrote:
>
> >
>
My employment with TI is coming to an end, add the copyright and author comments
as they due and change the maintainer mail address.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Peter Ujfalusi
---
.../devicetree/bindings/sound/ti,j721e-cpb-audio.yaml | 4 +++-
On Mon, Dec 14, 2020 at 10:12 PM Jeffrin Jose T
wrote:
>
> hello,
>
> i have worked on to fix depreciated api issue from
> tools/testing/selftests/intel_pstate/aerf.c
>
> i met with the following error related...
>
> --x--x->
> $pwd
>
15.12.2020, 15:40, "Johannes Weiner" :
> On Mon, Dec 14, 2020 at 02:37:16PM -0800, Yang Shi wrote:
>> The shrink_slab_memcg() races with mem_cgroup_css_online(). A visibility of
>> CSS_ONLINE flag
>> in shrink_slab_memcg()->mem_cgroup_online() does not guarantee that we will
>> see
>>
Hi,
On 15/12/2020 15.05, Peter Ujfalusi wrote:
> Hi,
>
> My TI address is going to bounce after Friday (18.12.2020), switch my email
> address to my private one for now.
Obviously I forgot to 'TO' the private myself...
Doing that now.
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (2):
>
My employment with TI is coming to an end, it is my intention to look after
the drivers I have worked with over the years.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Peter Ujfalusi
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS
On Mon, Dec 14, 2020 at 11:58:49PM +0100, Adrien Grassein wrote:
> this set of patch intends to add the support of the pf8x00 PMIC
> regulators. This family of PMIC contains 12 regulators (7 bucks
> converters, 4 LDO, 1 RTC supply). All these 12 regulators are
> configurable via an OTP memory and
Hi,
My TI address is going to bounce after Friday (18.12.2020), switch my email
address to my private one for now.
Regards,
Peter
---
Peter Ujfalusi (2):
MAINTAINERS: Update email address for TI ASoC and twl4030 codec
drivers
ASoC: dt-bindings: ti,j721e: Update maintainer and author
Hi Charles,
I love your patch! Yet something to improve:
[auto build test ERROR on linux/master]
[also build test ERROR on linus/master v5.10]
[cannot apply to hwmon/hwmon-next next-20201215]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
From: Colin Ian King
There is a spelling mistake in the Kconfig, fix it.
Signed-off-by: Colin Ian King
---
drivers/mailbox/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
index f4abe3529acd..68de2c6af727 100644
---
On Tue, 2020-12-15 at 16:33 +0800, Fox Chen wrote:
> On Mon, Dec 14, 2020 at 9:30 PM Ian Kent wrote:
> > On Mon, 2020-12-14 at 14:14 +0800, Fox Chen wrote:
> > > On Sun, Dec 13, 2020 at 11:46 AM Ian Kent
> > > wrote:
> > > > On Fri, 2020-12-11 at 10:17 +0800, Ian Kent wrote:
> > > > > On Fri,
On Tue, Dec 15, 2020 at 5:39 PM Vincent Guittot
wrote:
>
> On Mon, 14 Dec 2020 at 19:46, Dietmar Eggemann
> wrote:
> >
> > On 11/12/2020 13:03, Ryan Y wrote:
> > > Hi Dietmar,
> > >
> > > Yes! That's exactly what I meant.
> > >
> > >> The issue is that sugov_update_[shared\|single] ->
Hi "József,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tty/tty-testing]
[also build test WARNING on usb/usb-testing robh/for-next linus/master v5.10]
[cannot apply to next-20201215]
[If your patch is applied to the wrong git tree, kindly drop us a
When a filesystem is mounted with a blank name like so:
# mount '' bad -t tmpfs
its name entry in /proc/mounts is blank causing the line to start
with a space.
/mnt/bad tmpfs rw,seclabel,relatime,inode64 0 0
Further, the name could start with a hash, causing the entry to look
like this
From: Colin Ian King
There is a spelling mistake in the Kconfig help text. Fix it.
Signed-off-by: Colin Ian King
---
drivers/hid/usbhid/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/usbhid/Kconfig b/drivers/hid/usbhid/Kconfig
index
Hi,
On 12/14/20 8:29 PM, Mario Limonciello wrote:
> commit e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME
> systems")
> disabled s0ix flows for systems that have various incarnations of the
> i219-LM ethernet controller. This changed caused power consumption
> regressions
> on
Hi,
On 12/14/20 8:29 PM, Mario Limonciello wrote:
> Per guidance from Intel ethernet architecture team, it may take
> up to 1 second for unconfiguring ULP mode.
>
> However in practice this seems to be taking up to 2 seconds on
> some Lenovo machines. Detect scenarios that take more than 1
On Tue, Dec 15, 2020 at 2:22 AM Matthew Garrett wrote:
>
> On Sun, Nov 29, 2020 at 9:36 PM Kai-Heng Feng
> wrote:
> >
> > We are seeing thermal shutdown on Intel based mobile workstations, the
> > shutdown happens during the first trip handle in
> > thermal_zone_device_register():
> > kernel:
Hi,
On 12/14/20 8:29 PM, Mario Limonciello wrote:
> This flag can be used by an end user to disable S0ix flows on a
> buggy system or by an OEM for development purposes.
>
> If you need this flag to be persisted across reboots, it's suggested
> to use a udev rule to call adjust it until the
Hi,
On 12/14/20 8:29 PM, Mario Limonciello wrote:
> commit e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME
> systems")
> disabled s0ix flows for systems that have various incarnations of the
> i219-LM ethernet controller. This was done because of some regressions
> caused by an
Hi Linus,
Included in this pull request are just 3 patches. Other integrity
changes are being upstreamed via EFI (defines a common EFI secure and
trusted boot IMA policy) and BPF LSM (exporting the IMA file cache hash
info based on inode).
The 3 patches included in this pull request:
- bug fix:
My employment with TI is coming to an end and I will not have access to
the board where this bridge is connected to.
It is better to remove a soon bouncing email address.
Signed-off-by: Peter Ujfalusi
---
.../devicetree/bindings/display/bridge/toshiba,tc358768.yaml | 3 ---
1 file changed, 3
Hi Bao Hua,
Sorry I almost missed this message, :(
On 2020/12/14 7:29, Song Bao Hua (Barry Song) wrote:
>
> Hi Aubrey,
>
> The patch looks great. But I didn't find any hackbench improvement
> on kunpeng 920 which has 24 cores for each llc span. Llc span is also
> one numa node. The topology is
On Mon, Dec 14, 2020 at 02:37:16PM -0800, Yang Shi wrote:
> The shrink_slab_memcg() races with mem_cgroup_css_online(). A visibility of
> CSS_ONLINE flag
> in shrink_slab_memcg()->mem_cgroup_online() does not guarantee that we will
> see
> memcg->nodeinfo[nid]->shrinker_maps != NULL. This may
On Fri, Dec 11, 2020 at 12:18:50PM +0530, Viresh Kumar wrote:
> On 10-12-20, 11:17, Viresh Kumar wrote:
> > The previous call to update_freq_counters_refs() has already updated the
> > per-cpu variables, don't overwrite them with the same value again.
> >
> > Fixes: 4b9cf23c179a ("arm64: wrap and
On 2020-12-15 11:14, Valentin Schneider wrote:
On 15/12/20 10:19, Marc Zyngier wrote:
Hi Gunter,
On 2020-12-15 00:21, Guenter Roeck wrote:
On Mon, Nov 09, 2020 at 09:41:19AM +, Valentin Schneider wrote:
As done for the Arm GIC irqchips, move IPIs to
handle_percpu_devid_irq() as
When memory-failure occurs, we call this function which is implemented
by each kind of devices. For the fsdax case, pmem device driver
implements it. Pmem device driver will find out the block device where
the error page locates in, and try to get the filesystem on this block
device. And
This patchset is a try to resolve the problem of tracking shared page
for fsdax.
Change from v2:
- Adjust the order of patches
- Divide the infrastructure and the drivers that use it
- Rebased to v5.10
Change from v1:
- Introduce ->block_lost() for block device
- Support mapped device
Memory failure occurs in fsdax mode will finally be handled in
filesystem. We introduce this interface to find out files or metadata
affected by the corrupted range, and try to recover the corrupted data
if possiable.
Signed-off-by: Shiyang Ruan
---
include/linux/fs.h | 2 ++
1 file changed, 2
Hi,
Ouuu it was fixed recently in net-next.
Sorry, I missed that.
Thanks for submitting policy clarification I am going to adapt to it.
Thanks
On Tue, Dec 15, 2020 at 7:18 AM Leon Romanovsky wrote:
>
> On Mon, Dec 14, 2020 at 09:37:34PM -0800, Joe Perches wrote:
> > On Tue, 2020-12-15 at 07:18
Hi,
On 12/14/20 8:36 PM, Limonciello, Mario wrote:
>> Hi All,
>>
>> Sasha (and the other intel-wired-lan folks), thank you for investigating this
>> further and for coming up with a better solution.
>>
>> Mario, thank you for implementing the new scheme.
>>
>
> Sure.
>
>> I've tested this patch
The ptr_ret script script addresses a number of situations where we end up
testing an error pointer, and if it's an error returning it, or return 0
otherwise to transform it into a PTR_ERR_OR_ZERO call.
So it will convert a block like this:
if (IS_ERR(err))
return PTR_ERR(err);
return 0;
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-5.11-rc1-tag
xen: branch for v5.11-rc1
It contains fixes for security issues just having been disclosed:
- a 5 patch series for fixing of XSA-349 (DoS via resource depletion in
On Tue, Dec 15, 2020 at 09:52:36AM +0100, Julia Lawall wrote:
>
>
> On Tue, 15 Dec 2020, Maxime Ripard wrote:
>
> > Hi,
> >
> > On Tue, Jan 07, 2020 at 11:29:54AM +0100, Wolfram Sang wrote:
> > > On Tue, Jan 07, 2020 at 11:06:56AM +0100, Julia Lawall wrote:
> > > >
> > > >
> > > > On Tue, 7 Jan
A later commit will need to lookup a subset of these opcodes. To
avoid duplicating code, pull out a table.
The shift opcodes won't be needed by that later commit, but they're
already duplicated, so fold them into the table anyway.
Signed-off-by: Brendan Jackman
Acked-by: John Fastabend
---
On Sat 12-12-20 17:29:57, Matthew Wilcox wrote:
> On Fri, Dec 04, 2020 at 10:48:53AM -0500, Josef Bacik wrote:
> > We on the program committee hope everybody has been able to stay safe and
> > healthy during this challenging time, and look forward to being able to see
> > all of you in person
The JIT case for encoding atomic ops is about to get more
complicated. In order to make the review & resulting code easier,
let's factor out some shared helpers.
Signed-off-by: Brendan Jackman
Acked-by: John Fastabend
---
arch/x86/net/bpf_jit_comp.c | 39 ++---
A subsequent patch will add additional atomic operations. These new
operations will use the same opcode field as the existing XADD, with
the immediate discriminating different operations.
In preparation, rename the instruction mode BPF_ATOMIC and start
calling the zero immediate BPF_ADD.
This is
I can't find a reason why this code is in resolve_pseudo_ldimm64;
since I'll be modifying it in a subsequent commit, tidy it up.
Signed-off-by: Brendan Jackman
Acked-by: Yonghong Song
Acked-by: John Fastabend
---
kernel/bpf/verifier.c | 13 ++---
1 file changed, 6 insertions(+), 7
The BPF_FETCH field can be set in bpf_insn.imm, for BPF_ATOMIC
instructions, in order to have the previous value of the
atomically-modified memory location loaded into the src register
after an atomic op is carried out.
Suggested-by: Yonghong Song
Signed-off-by: Brendan Jackman
Acked-by: John
On Mon, Dec 14, 2020 at 11:28 PM Guillaume Tucker
wrote:
> Please see the bisection report below about the pinctrl driver
> failing to probe on the arm64 mt8173-elm-hana platform.
That's an excellent, helpful report which helps a lot!
Thank you for doing this!
> This is the error message:
>
>
The prog_test that's added depends on Clang/LLVM features added by
Yonghong in commit 286daafd6512 (was https://reviews.llvm.org/D72184).
Note the use of a define called ENABLE_ATOMICS_TESTS: this is used
to:
- Avoid breaking the build for people on old versions of Clang
- Avoid needing
This adds instructions for
atomic[64]_[fetch_]and
atomic[64]_[fetch_]or
atomic[64]_[fetch_]xor
All these operations are isomorphic enough to implement with the same
verifier, interpreter, and x86 JIT code, hence being a single commit.
The main interesting thing here is that x86 doesn't directly
Since the atomic operations that are added in subsequent commits are
all isomorphic with BPF_ADD, pull out a macro to avoid the
interpreter becoming dominated by lines of atomic-related code.
Note that this sacrificies interpreter performance (combining
STX_ATOMIC_W and STX_ATOMIC_DW into single
Document new atomic instructions.
Signed-off-by: Brendan Jackman
---
Documentation/networking/filter.rst | 26 ++
1 file changed, 26 insertions(+)
diff --git a/Documentation/networking/filter.rst
b/Documentation/networking/filter.rst
index 1583d59d806d..26d508a5e038
This adds two atomic opcodes, both of which include the BPF_FETCH
flag. XCHG without the BPF_FETCH flag would naturally encode
atomic_set. This is not supported because it would be of limited
value to userspace (it doesn't imply any barriers). CMPXCHG without
BPF_FETCH woulud be an atomic
Status of the patches
=
Thanks for the reviews!
There's one review comment from John which I haven't resolved [3].
He pointed out that we could make the verifier a bit smarter about
propagating register bounds. I don't have a clear picture of how
useful it would be but IIUC
drm_irq_uninstall should be called before pci_disable_msi, if use
devm_drm_irq_install to register the interrupt, the system will
call pci_disable_msi first and then call drm_irq_uninstall, which
will result in the following callstack.
This reverts commit e4401247070a37c2fce62b2773a4eb7757983938.
This provides a convenient perf ringbuf -> libbpf ringbuf migration
path for users of external polling systems. It is analogous to
perf_buffer__epoll_fd.
Signed-off-by: Brendan Jackman
---
Difference from v1: Added entry to libbpf.map.
tools/lib/bpf/libbpf.h | 1 +
tools/lib/bpf/libbpf.map |
The case for JITing atomics is about to get more complicated. Let's
factor out some common code to make the review and result more
readable.
NB the atomics code doesn't yet use the new helper - a subsequent
patch will add its use as a side-effect of other changes.
Acked-by: John Fastabend
This function is used to handle errors which may cause data lost in
filesystem. Such as memory failure in fsdax mode.
In XFS, it requires "rmapbt" feature in order to query for files or
metadata which associated to the corrupted data. Then we could call fs
recover functions to try to repair the
Thanks Mian for bringing it to our notice.
Have you tried removing the dw_pcie_setup_rc(pp); call from
pcie-tegra194.c file on top of linux-next? and does that solve the issue?
diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c
b/drivers/pci/controller/dwc/pcie-tegra194.c
index
The current memory_failure_dev_pagemap() can only handle single-mapped
dax page for fsdax mode. The dax page could be mapped by multiple files
and offsets if we let reflink feature & fsdax mode work together. So,
we refactor current implementation to support handle memory failure on
each file
Pmem device could be a target of mapped device. In order to obtain
superblock on the mapped device, we introduce this to translate offset
from target device to md device.
Currently, we implement it on linear target, which is easy to do the
translation. Other targets will be supported in the
With the support of ->rmap(), it is possible to obtain the superblock on
a mapped device.
If a pmem device is used as one target of mapped device, we cannot
obtain its superblock directly. With the help of SYSFS, the mapped
device can be found on the target devices. So, we iterate the
Call the ->memory_failure() which is implemented by pmem driver, in
order to finally notify filesystem to handle the corrupted data. The
old collecting and killing processes are moved into
mf_dax_mapping_kill_procs(), which will be called by filesystem.
Signed-off-by: Shiyang Ruan
---
In fsdax mode, the memory failure happens on block device. So, it is
needed to introduce an interface for block devices. Each kind of block
device can handle the memory failure in ther own ways.
Signed-off-by: Shiyang Ruan
---
include/linux/blkdev.h | 2 ++
1 file changed, 2 insertions(+)
Obtain the superblock of a pmem disk, and call filesystem's
->corrupted_range() to handle the corrupted data.
Signed-off-by: Shiyang Ruan
---
block/genhd.c | 12
drivers/nvdimm/pmem.c | 24
include/linux/genhd.h | 1 +
3 files changed, 37
On 2020/12/15 15:59, Peter Zijlstra wrote:
> On Tue, Dec 15, 2020 at 11:36:35AM +0800, Li, Aubrey wrote:
>> On 2020/12/15 0:48, Peter Zijlstra wrote:
>>> We compute the average cost of the total scan, but then use it as a
>>> per-cpu scan cost when computing the scan proportion. Fix this by
>>>
Hi Geert,
On Tue, Dec 15, 2020 at 12:44:17PM +0100, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> On Tue, Dec 15, 2020 at 12:14 PM Jacopo Mondi wrote:
> > On Mon, Nov 30, 2020 at 03:00:48PM -0700, Rob Herring wrote:
> > > On Mon, Nov 16, 2020 at 02:52:59PM +0100, Jacopo Mondi wrote:
> > > >
On Mon, Dec 14, 2020 at 10:24:22AM -0500, Steven Rostedt wrote:
> On Mon, 14 Dec 2020 10:22:17 +0800
> Ming Lei wrote:
>
> > trace_note_tsk() is called by __blk_add_trace(), which is covered by RCU
> > read lock.
> > So in case of PREEMPT_RT, warning of 'BUG: sleeping function called from
> >
The idle_exittime field of tick_sched is used to record the time when
the idle state was left. but currently the idle_exittime is updated in
the function tick_nohz_restart_sched_tick(), which is not always in idle
state when nohz_full is configured.
tick_irq_exit
tick_nohz_irq_exit
On Tue, Dec 15, 2020 at 11:14:20AM +, Pavel Begunkov wrote:
> On 15/12/2020 01:41, Ming Lei wrote:
> > On Tue, Dec 15, 2020 at 12:20:19AM +, Pavel Begunkov wrote:
> >> Instead of creating a full copy of iter->bvec into bio in direct I/O,
> >> the patchset makes use of the one provided. It
在 2020/12/15 20:01, Daniel Vetter 写道:
On Tue, Dec 15, 2020 at 12:59:53PM +0100, Daniel Vetter wrote:
On Tue, Dec 15, 2020 at 11:01:39AM +0800, Tian Tao wrote:
drm_irq_uninstall should be called before pci_disable_msi, if use
devm_drm_irq_install to register the interrupt, the system will
--
Good Day,
I know that this mail might be a surprise to you, but i plead that you
take a little time to read this it, if it is something you can
handle, then you reply me.
I work with one of the leading banks in my country, and i have worked
with this bank for more than 11yrs, There is an
From: SeongJae Park
This commit adds kunit based unit tests for the core and the virtual
address spaces monitoring primitives of DAMON.
Signed-off-by: SeongJae Park
Reviewed-by: Brendan Higgins
---
mm/damon/Kconfig | 36 +
mm/damon/core-test.h | 253
From: SeongJae Park
This commit adds a simple user space tests for DAMON. The tests are
using kselftest framework.
Signed-off-by: SeongJae Park
---
tools/testing/selftests/damon/Makefile| 7 +
.../selftests/damon/_chk_dependency.sh| 28 +++
From: SeongJae Park
This commit updates MAINTAINERS file for DAMON related files.
Signed-off-by: SeongJae Park
---
MAINTAINERS | 12
1 file changed, 12 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 281de213ef47..88b2125b0f07 100644
--- a/MAINTAINERS
+++
On Tue, Dec 15, 2020 at 12:59:53PM +0100, Daniel Vetter wrote:
> On Tue, Dec 15, 2020 at 11:01:39AM +0800, Tian Tao wrote:
> > drm_irq_uninstall should be called before pci_disable_msi, if use
> > devm_drm_irq_install to register the interrupt, the system will
> > call pci_disable_msi first and
From: SeongJae Park
This commit adds documents for DAMON under
`Documentation/admin-guide/mm/damon/` and `Documentation/vm/damon/`.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/guide.rst | 157 ++
Documentation/admin-guide/mm/damon/index.rst | 15 +
Hi Jane
On 2020/12/15 上午4:58, Jane Chu wrote:
Hi, Shiyang,
On 11/22/2020 4:41 PM, Shiyang Ruan wrote:
This patchset is a try to resolve the problem of tracking shared page
for fsdax.
Change from v1:
- Intorduce ->block_lost() for block device
- Support mapped device
- Add 'not
From: SeongJae Park
'damon-dbgfs' provides simple user space interface for DAMON, but using
the interface for complex usages could require annoying repetitive
works. Writing a user space data access monitoring applications on top
of the debugfs interface and using the application would be
From: SeongJae Park
In some use cases, users would want to run multiple monitoring context.
For example, if a user wants a high precision monitoring and dedicating
multiple CPUs for the job is ok, because DAMON creates one monitoring
thread per one context, the user can split the monitoring
From: SeongJae Park
The user space users can control DAMON and get the monitoring results
via the 'damon_aggregated' tracepoint event. However, dealing with the
tracepoint might be complex for some simple use cases. This commit
therefore implements 'recording' feature in 'damon-dbgfs'. The
From: SeongJae Park
For CPU usage accounting, knowing pid of the monitoring thread could be
helpful. For example, users could use cpuaccount cgroups with the pid.
This commit therefore exports the pid of currently running monitoring
thread to the user space via 'kdamond_pid' file in the
Hi,
On Tuesday 15 Dec 2020 at 11:04:16 (+0530), Viresh Kumar wrote:
> The AMU counters won't get used today if the cpufreq driver is built as
> a module as the amu core requires everything to be ready by late init.
>
> Fix that properly by registering for cpufreq policy notifier. Note that
> the
On Tue, Dec 15, 2020 at 11:01:39AM +0800, Tian Tao wrote:
> drm_irq_uninstall should be called before pci_disable_msi, if use
> devm_drm_irq_install to register the interrupt, the system will
> call pci_disable_msi first and then call drm_irq_uninstall, which
> will result in the following
From: SeongJae Park
DAMON is designed to be used by kernel space code such as the memory
management subsystems, and therefore it provides only kernel space API.
That said, letting the user space control DAMON could provide some
benefits to them. For example, it will allow user space to analyze
From: SeongJae Park
This commit adds a tracepoint for DAMON. It traces the monitoring
results of each region for each aggregation interval. Using this, DAMON
can easily integrated with tracepoints supporting tools such as perf.
Signed-off-by: SeongJae Park
Reviewed-by: Leonard Foerster
From: SeongJae Park
This commit introduces a reference implementation of the address space
specific low level primitives for the virtual address space, so that
users of DAMON can easily monitor the data accesses on virtual address
spaces of specific processes by simply configuring the
From: SeongJae Park
PG_idle and PG_young allow the two PTE Accessed bit users, Idle Page
Tracking and the reclaim logic concurrently work while don't interfere
each other. That is, when they need to clear the Accessed bit, they set
PG_young to represent the previous state of the bit,
From: SeongJae Park
Even somehow the initial monitoring target regions are well constructed
to fulfill the assumption (pages in same region have similar access
frequencies), the data access pattern can be dynamically changed. This
will result in low monitoring quality. To keep the assumption
On Tue, Dec 15, 2020 at 07:48:52PM +0800, Tian Tao wrote:
> Add new api devm_drm_msi_install() to register interrupts,
> no need to call pci_disable_msi() when the drm module is removed.
>
> Signed-off-by: Tian Tao
> ---
> drivers/gpu/drm/drm_irq.c | 33 +
>
From: SeongJae Park
To avoid the unbounded increase of the overhead, DAMON groups adjacent
pages that assumed to have the same access frequencies into a region.
As long as the assumption (pages in a region have the same access
frequencies) is kept, only one page in the region is required to be
901 - 1000 of 1218 matches
Mail list logo
