On Fri, Sep 20, 2024 at 6:02 AM Kris Van Hees wrote:
>
> On Thu, Sep 19, 2024 at 11:28:44PM +0900, Masahiro Yamada wrote:
> > Hi Kris,
> >
> >
> >
> > On Tue, Sep 10, 2024 at 4:43 AM Kris Van Hees
> > wrote:
> > >
> > > On Sun, Sep 08, 2024 at 11:50:51AM +0900, Masahiro Yamada wrote:
> > > > On
On Fri, Sep 20, 2024 at 3:08 AM Sam James wrote:
>
> Masahiro Yamada writes:
>
> > On Fri, Sep 20, 2024 at 2:07 AM Daniel Gomez wrote:
> >>
> >> On Fri, Sep 06, 2024 at 10:45:03AM -0400, Kris Van Hees wrote:
> >> > Create file module.builtin.ranges that can be used to find where
> >> > built-in
On Thu, Sep 19, 2024 at 11:28:44PM +0900, Masahiro Yamada wrote:
> Hi Kris,
>
>
>
> On Tue, Sep 10, 2024 at 4:43 AM Kris Van Hees
> wrote:
> >
> > On Sun, Sep 08, 2024 at 11:50:51AM +0900, Masahiro Yamada wrote:
> > > On Fri, Sep 6, 2024 at 11:45???PM Kris Van Hees
> > > wrote:
> > > >
> > >
On Thu, Sep 19, 2024 at 07:08:42PM +0100, Sam James wrote:
> Masahiro Yamada writes:
>
> > On Fri, Sep 20, 2024 at 2:07 AM Daniel Gomez wrote:
> >>
> >> On Fri, Sep 06, 2024 at 10:45:03AM -0400, Kris Van Hees wrote:
> >> > Create file module.builtin.ranges that can be used to find where
> >> > b
Masahiro Yamada writes:
> On Fri, Sep 20, 2024 at 2:07 AM Daniel Gomez wrote:
>>
>> On Fri, Sep 06, 2024 at 10:45:03AM -0400, Kris Van Hees wrote:
>> > Create file module.builtin.ranges that can be used to find where
>> > built-in modules are located by their addresses. This will be useful for
>
On Fri, Sep 20, 2024 at 2:07 AM Daniel Gomez wrote:
>
> On Fri, Sep 06, 2024 at 10:45:03AM -0400, Kris Van Hees wrote:
> > Create file module.builtin.ranges that can be used to find where
> > built-in modules are located by their addresses. This will be useful for
> > tracing tools to find what fu
On Fri, Sep 06, 2024 at 10:45:03AM -0400, Kris Van Hees wrote:
> Create file module.builtin.ranges that can be used to find where
> built-in modules are located by their addresses. This will be useful for
> tracing tools to find what functions are for various built-in modules.
>
> The offset range
On Mon, 2024-09-16 at 08:01 +0700, Bagas Sanjaya wrote:
> On Sat, Sep 14, 2024 at 01:07:20PM -0400, Jeff Layton wrote:
> > +Multigrain timestamps aim to remedy this by selectively using fine-grained
> > +timestamps when a file has had its timestamps queried recently, and the
> > current
> > +coars
On Mon, 2024-09-16 at 12:12 +0200, Thomas Gleixner wrote:
> On Sat, Sep 14 2024 at 13:07, Jeff Layton wrote:
> > For multigrain timestamps, we must keep track of the latest timestamp
>
> What is a multgrain timestamp? Can you please describe the concept
> behind it? I'm not going to chase random d
Hi Kris,
On Tue, Sep 10, 2024 at 4:43 AM Kris Van Hees wrote:
>
> On Sun, Sep 08, 2024 at 11:50:51AM +0900, Masahiro Yamada wrote:
> > On Fri, Sep 6, 2024 at 11:45???PM Kris Van Hees
> > wrote:
> > >
> > > Create file module.builtin.ranges that can be used to find where
> > > built-in modules
On 09/19, Liao Chang wrote:
>
> --- a/arch/arm64/kernel/probes/uprobes.c
> +++ b/arch/arm64/kernel/probes/uprobes.c
> @@ -17,12 +17,16 @@ void arch_uprobe_copy_ixol(struct page *page, unsigned
> long vaddr,
> void *xol_page_kaddr = kmap_atomic(page);
> void *dst = xol_page_kaddr + (vad
> Sorry, I know nothing about the ThreadSanitizer and related annotation,
> could you provide some information about it, thanks.
Documentation/dev-tools/kcsan.rst
> > Would be good to have some commentary why doing so
> > many write operations with merely a rcu_read_lock as protection is safe.
>
在 2024/9/18 20:25, Andi Kleen 写道:
> Liao Chang writes:
>> +
>> +/*
>> + * xol_recycle_insn_slot - recycle a slot from the garbage collection list.
>> + */
>> +static int xol_recycle_insn_slot(struct xol_area *area)
>> +{
>> +struct uprobe_task *utask;
>> +int slot = UINSNS_PER_PAGE;
>>
The profiling of single-thread selftests bench reveals a bottlenect in
caches_clean_inval_pou() on ARM64. On my local testing machine, this
function takes approximately 34% of CPU cycles for trig-uprobe-nop and
trig-uprobe-push.
This patch add a check to avoid unnecessary cache flush when writing
* Mike Rapoport [240909 02:49]:
> From: "Mike Rapoport (Microsoft)"
>
> Using large pages to map text areas reduces iTLB pressure and improves
> performance.
>
> Extend execmem_alloc() with an ability to use huge pages with ROX
> permissions as a cache for smaller allocations.
>
> To populate
15 matches
Mail list logo
