[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJuCfpGM7rX6EBLSpjY-go1N-mbc_ObgjeggTLgE4rOR4mXDDA@mail.gmail.com>
Date: Sun, 24 Nov 2024 11:56:56 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: akpm@...ux-foundation.org, Peter Zijlstra <peterz@...radead.org>
Cc: Andrii Nakryiko <andrii@...nel.org>, linux-trace-kernel@...r.kernel.org,
linux-mm@...ck.org, mingo@...nel.org, torvalds@...ux-foundation.org,
oleg@...hat.com, rostedt@...dmis.org, mhiramat@...nel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org, jolsa@...nel.org,
paulmck@...nel.org, willy@...radead.org, mjguzik@...il.com,
brauner@...nel.org, jannh@...gle.com, mhocko@...nel.org, vbabka@...e.cz,
shakeel.butt@...ux.dev, hannes@...xchg.org, lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com, david@...hat.com, arnd@...db.de,
viro@...iv.linux.org.uk, hca@...ux.ibm.com
Subject: Re: [PATCH v5 tip/perf/core 0/2] uprobes: speculative lockless
VMA-to-uprobe lookup
On Sat, Nov 23, 2024 at 12:35 PM Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Fri, Nov 22, 2024 at 09:48:11AM -0800, Suren Baghdasaryan wrote:
> > On Fri, Nov 22, 2024 at 7:04 AM Suren Baghdasaryan <surenb@...gle.com> wrote:
> > >
> > > On Fri, Nov 22, 2024 at 3:07 AM Peter Zijlstra <peterz@...radead.org> wrote:
> > > >
> > > > On Thu, Nov 21, 2024 at 07:59:20PM -0800, Andrii Nakryiko wrote:
> > > >
> > > > > Andrii Nakryiko (2):
> > > > > uprobes: simplify find_active_uprobe_rcu() VMA checks
> > > > > uprobes: add speculative lockless VMA-to-inode-to-uprobe resolution
> > > >
> > > > Thanks, assuming Suren is okay with me carrying his patches through tip,
> > > > I'll make this land in tip/perf/core after -rc1.
> > >
> > > No objections from me. Thanks!
> >
> > I just fixed a build issue in one of my patches for an odd config, so
> > please use the latest version of the patchset from here:
> > https://lore.kernel.org/all/20241122174416.1367052-1-surenb@google.com/
>
> updated, thanks!
Hi Andrew,
I just noticed that patches from an old version of my patchset are
present in mm-unstable, more specifically these two:
fb23aacd2a14 "mm: convert mm_lock_seq to a proper seqcount"
549aeb99ccf1 "mm: introduce mmap_lock_speculation_{begin|end}"
Peter will be merging the latest version into tip/perf/core, so this
will cause a conflict at some point.
It should be easy to update them in mm-unstable to the latest version
[1]. I was able to revert the old ones and apply the new ones without
any merge conflict. If possible, please update them instead of
dropping them from mm-unstable. Some patches I'm preparing to post
have dependencies on this patchset.
Thanks,
Suren.
[1] https://lore.kernel.org/all/20241122174416.1367052-1-surenb@google.com/
Powered by blists - more mailing lists