On Tue, Feb 20, 2024 at 12:46 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Feb 20, 2024 at 12:23:01PM -0800, Suren Baghdasaryan wrote: > > On Tue, Feb 20, 2024 at 12:20 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On Tue, Feb 20, 2024 at 11:03:50AM -0800, Suren Baghdasaryan wrote: > > > > From: Wang Kefeng <wangkefeng.wang@xxxxxxxxxx> > > > > > > > > Attempt VMA lock-based page fault handling first, and fall back to the > > > > existing mmap_lock-based handling if that fails, the ebizzy benchmark > > > > shows 25% improvement on qemu with 2 cpus. > > > > > > > > Signed-off-by: Kefeng Wang <wangkefeng.wang@xxxxxxxxxx> > > > > Signed-off-by: Russell King (Oracle) <rmk+kernel@xxxxxxxxxxxxxxx> > > > > Signed-off-by: Suren Baghdasaryan <surenb@xxxxxxxxxx> > > > > --- > > > > arch/arm/Kconfig | 1 + > > > > arch/arm/mm/fault.c | 30 ++++++++++++++++++++++++++++++ > > > > 2 files changed, 31 insertions(+) > > > > > > No git id? > > > > > > What kernel branch(s) does this go to? > > > > > > confused, > > > > Sorry, I used the command from your earlier email about the merge conflict: > > git send-email --to '<stable@xxxxxxxxxxxxxxx>' --in-reply-to > > '2024021921-bleak-sputter-5ecf@gregkh' --subject-prefix 'PATCH 6.7.y' > > HEAD^.. > > but it didn't send both patches, so I formatted the patches I wanted > > to send and sent it with the same command replacing "HEAD^.." with > > "*.patch". What should I have done instead? > > You forgot the "git cherry-pick -x " portion of the instructions :( Ah, I see. Will do next time. > > > And the subject prefix didn't work here, right? Yes, looks like it. It worked the first time though :/ > > thanks, > > greg k-h
