CR3 of Kernel thread

Dear members,

As you know, at least I think that the Linux kernel is single thread entity and cr3 for whole of the kernel must be the same, but when I tried to read the cr3's value using a kernel module, each time, I have obtained different one for it. I'm wondering if someone could help me to unravel this problem.

Thanks in advance

With all due respect ... "Google it," and instantly read the last umpty-leven times this very same question has been answered.

Changing the CR3 value is expensive, and from the point of view of running kernel-code, completely unnecessary. Changing this register causes the CPU to flush a lot of caches that it'd rather not flush if it doesn't have to, and there's no reason to do it (and every reason not to ...) until a different user-land process is actually selected. The system might ping-pong between user mode and kernel mode dozens of times before deciding to switch to a different virtual-memory context.