Yes Adam, my commit should have mentioned that! Maybe even referenced "https://docs.pmem.io/getting-started-guide/creating-development- environments/linux-environments/linux-memmap" or some other doc about it.
Thanks for pointing that out! I'll rephrase that, so others willing to do autopkgtest may consider testing with memmap as well. If the "-e" option works, I think most of the scripts being included shall work. I might have to "skip" some tests whenever memcg is being used if they're not good. Since these tests are likely not being ran in bileto, for every new merge/fix, as neither kvm nvdimm emulation nor kernel cmdlines can be provided in that environment, I'll keep things as is for now, if everyone agrees (after changing the commit log). I haven't tested all scripts I'm including with "memmap=" cmdline because I was also worried about supporting QEMU nvdimm support, so I was killing 2 birds w/ a single stone in this effort. So, for now, the regressions test would be done manually anyway. For a next step, when merging this back to Debian (so I can put the package back to syncpackage), I, perhaps, could spend more time into this and split those tests that would work with memmap= , those that would work with both, memmap= and qemu emulation, and those only working with HW. Sounds good for you ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853506 Title: [MIR] ndctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
