Re: [PATCH 03/25] um/xor: don't override XOR_SELECT_TEMPLATE
Richard Weinberger <[email protected]>
| Newsgroups | org.kernel.vger.sparclinux,dev.linux.lists.loongarch,org.infradead.lists.linux-riscv,org.infradead.lists.linux-um,org.kernel.vger.linux-alpha,org.kernel.vger.linux-arch,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-crypto,org.kernel.vger.linux-kernel,org.kernel.vger.linux-raid,org.kernel.vger.linux-s390,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
----- Ursprüngliche Mail ----- > Von: "hch" <[email protected]> > XOR_SELECT_TEMPLATE is only ever called with a NULL argument, so all the > ifdef'ery doesn't do anything. With our without this, the time travel > mode should work fine on CPUs that support AVX2, as the AVX2 > implementation is forced in this case, and won't work otherwise. IIRC Johannes added XOR_SELECT_TEMPLATE() here to skip the template selection logic because it didn't work with time travel mode. Johannes, can you please test whether this change does not break time travel mode? Thanks, //richard