Re: mmotm 2018-12-21-15-28 uploaded
On Mon 07-01-19 14:46:43, Anshuman Khandual wrote: > > > On 01/07/2019 02:13 PM, Michal Hocko wrote: > > Hi, > > > > On Mon 07-01-19 13:02:31, Anshuman Khandual wrote: > >> On 12/22/2018 04:58 AM, a...@linux-foundation.org wrote: > > [...] > >>> A git tree which contains the memory management portion of this tree is > >>> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi > >> > >> Hello Michal, > >> > >> I dont see the newer tags on this tree. Tried fetching all the tags from > >> the tree > >> but only see these right now for 2018. This release should have an > >> equivalent tag > >> (mmotm-2018-12-21-15-28) right ? > > > > I have stopped tracking mmotm trees in this tree quite some time ago. I > > would much rather turn mmotm into a proper git tree which I was > > discussing with Andrew but we didn't land in anything so far. I hope to > > use LSFMM this year to resurrect the idea. > > > > Even this tree http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/ does not > clone. So > right now the only way to construct the latest mmotm tree is through applying > all > the patches mentioned here at http://www.ozlabs.org/~akpm/mmotm/ on > linux-next ? linux-next should contain all of them already. -- Michal Hocko SUSE Labs
Re: mmotm 2018-12-21-15-28 uploaded
On 01/07/2019 02:13 PM, Michal Hocko wrote: > Hi, > > On Mon 07-01-19 13:02:31, Anshuman Khandual wrote: >> On 12/22/2018 04:58 AM, a...@linux-foundation.org wrote: > [...] >>> A git tree which contains the memory management portion of this tree is >>> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi >> >> Hello Michal, >> >> I dont see the newer tags on this tree. Tried fetching all the tags from the >> tree >> but only see these right now for 2018. This release should have an >> equivalent tag >> (mmotm-2018-12-21-15-28) right ? > > I have stopped tracking mmotm trees in this tree quite some time ago. I > would much rather turn mmotm into a proper git tree which I was > discussing with Andrew but we didn't land in anything so far. I hope to > use LSFMM this year to resurrect the idea. > Even this tree http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/ does not clone. So right now the only way to construct the latest mmotm tree is through applying all the patches mentioned here at http://www.ozlabs.org/~akpm/mmotm/ on linux-next ?
Re: mmotm 2018-12-21-15-28 uploaded
Hi, On Mon 07-01-19 13:02:31, Anshuman Khandual wrote: > On 12/22/2018 04:58 AM, a...@linux-foundation.org wrote: [...] > > A git tree which contains the memory management portion of this tree is > > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi > > Hello Michal, > > I dont see the newer tags on this tree. Tried fetching all the tags from the > tree > but only see these right now for 2018. This release should have an equivalent > tag > (mmotm-2018-12-21-15-28) right ? I have stopped tracking mmotm trees in this tree quite some time ago. I would much rather turn mmotm into a proper git tree which I was discussing with Andrew but we didn't land in anything so far. I hope to use LSFMM this year to resurrect the idea. -- Michal Hocko SUSE Labs
Re: mmotm 2018-12-21-15-28 uploaded
On 12/22/2018 04:58 AM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2018-12-21-15-28 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully > more than once a week. > > You will need quilt to apply these patches to the latest Linus release (4.x > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series > > The file broken-out.tar.gz contains two datestamp files: .DATE and > .DATE--mm-dd-hh-mm-ss. Both contain the string -mm-dd-hh-mm-ss, > followed by the base kernel version against which this patch series is to > be applied. > > This tree is partially included in linux-next. To see which patches are > included in linux-next, consult the `series' file. Only the patches > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in > linux-next. > > A git tree which contains the memory management portion of this tree is > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi Hello Michal, I dont see the newer tags on this tree. Tried fetching all the tags from the tree but only see these right now for 2018. This release should have an equivalent tag (mmotm-2018-12-21-15-28) right ? mmotm-2018-01-04-16-19 mmotm-2018-01-12-16-53 mmotm-2018-01-18-16-31 mmotm-2018-01-25-16-20 mmotm-2018-01-31-16-51 mmotm-2018-02-06-16-41 mmotm-2018-02-21-14-48 mmotm-2018-03-13-15-15 mmotm-2018-03-14-16-24 mmotm-2018-03-22-16-18 mmotm-2018-03-28-16-05 mmotm-2018-04-05-16-59 mmotm-2018-04-10-17-02 mmotm-2018-04-13-17-28 mmotm-2018-05-03-15-54 mmotm-2018-05-10-16-34 mmotm-2018-05-18-16-44 mmotm-2018-05-25-14-52 - Anshuman
mmotm 2018-12-21-15-28 uploaded
The mm-of-the-moment snapshot 2018-12-21-15-28 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You will need quilt to apply these patches to the latest Linus release (4.x or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in http://ozlabs.org/~akpm/mmotm/series The file broken-out.tar.gz contains two datestamp files: .DATE and .DATE--mm-dd-hh-mm-ss. Both contain the string -mm-dd-hh-mm-ss, followed by the base kernel version against which this patch series is to be applied. This tree is partially included in linux-next. To see which patches are included in linux-next, consult the `series' file. Only the patches within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in linux-next. A git tree which contains the memory management portion of this tree is maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git by Michal Hocko. It contains the patches which are between the "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series file, http://www.ozlabs.org/~akpm/mmotm/series. A full copy of the full kernel tree with the linux-next and mmotm patches already applied is available through git within an hour of the mmotm release. Individual mmotm releases are tagged. The master branch always points to the latest release, so it's constantly rebasing. http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/ To develop on top of mmotm git: $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git $ git remote update mmotm $ git checkout -b topic mmotm/master $ git send-email mmotm/master.. [...] To rebase a branch with older patches to a new mmotm release: $ git remote update mmotm $ git rebase --onto mmotm/master topic The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second) contains daily snapshots of the -mm tree. It is updated more frequently than mmotm, and is untested. A git copy of this tree is available at http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/ and use of this tree is similar to http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above. This mmotm tree contains the following patches against 4.20-rc7: (patches marked "*" will be included in linux-next) origin.patch * mm-memory_hotplug-initialize-struct-pages-for-the-full-memory-section.patch * mm-thp-fix-flags-for-pmd-migration-when-split.patch * forkmemcg-fix-crash-in-free_thread_stack-on-memcg-charge-fail.patch * mm-page_alloc-fix-has_unmovable_pages-for-hugepages.patch * checkpatch-dont-interpret-stack-dumps-as-commit-ids.patch * mm-thp-always-specify-disabled-vmas-as-nh-in-smaps.patch * mm-memcg-fix-reclaim-deadlock-with-writeback.patch * arm-arch-arm-include-asm-pageh-needs-personalityh.patch * kasan-mm-change-hooks-signatures.patch * kasan-slub-handle-pointer-tags-in-early_kmem_cache_node_alloc.patch * kasan-move-common-generic-and-tag-based-code-to-commonc.patch * kasan-rename-source-files-to-reflect-the-new-naming-scheme.patch * kasan-add-config_kasan_generic-and-config_kasan_sw_tags.patch * kasan-arm64-adjust-shadow-size-for-tag-based-mode.patch * kasan-rename-kasan_zero_page-to-kasan_early_shadow_page.patch * kasan-initialize-shadow-to-0xff-for-tag-based-mode.patch * arm64-move-untagged_addr-macro-from-uaccessh-to-memoryh.patch * kasan-add-tag-related-helper-functions.patch * kasan-arm64-untag-address-in-_virt_addr_is_linear.patch * kasan-preassign-tags-to-objects-with-ctors-or-slab_typesafe_by_rcu.patch * kasan-arm64-fix-up-fault-handling-logic.patch * kasan-arm64-enable-top-byte-ignore-for-the-kernel.patch * kasan-mm-perform-untagged-pointers-comparison-in-krealloc.patch * kasan-split-out-generic_reportc-from-reportc.patch * kasan-add-bug-reporting-routines-for-tag-based-mode.patch * mm-move-obj_to_index-to-include-linux-slab_defh.patch * kasan-add-hooks-implementation-for-tag-based-mode.patch * kasan-arm64-add-brk-handler-for-inline-instrumentation.patch * kasan-mm-arm64-tag-non-slab-memory-allocated-via-pagealloc.patch * kasan-add-__must_check-annotations-to-kasan-hooks.patch * kasan-arm64-select-have_arch_kasan_sw_tags.patch * kasan-update-documentation.patch * kasan-add-spdx-license-identifier-mark-to-source-files.patch * bloat-o-meter-ignore-__addressable_-symbols.patch * scripts-decodecode-set-arch-when-running-natively-on-arm-arm64.patch * scripts-decode_stacktrace-only-strip-base-path-when-a-prefix-of-the-path.patch * checkstackpl-dynamic-stack-growth-for-aarch64.patch * scripts-add-spdxcheckpy-self-test.patch * scripts-tags-add-more-declarations.patch * arch-sh-mach-kfr2r09-fix-struct-mtd_oob_ops-build-warning.patch * sh-kfr2r09-drop-pointless-static-qualifier-in-kfr2r09_usb0_gadget_setup.patch * sh-boards-convert-to-spdx-identifiers.patch *