[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v2 0/8] pdx: introduce a new compression algorithm
On 01.07.2025 22:46, Stefano Stabellini wrote: > On Tue, 1 Jul 2025, Jan Beulich wrote: >> Sadly from this you omitted the output from the setup of the offsets >> arrays. Considering also your later reply, I'd be curious to know what >> mfn_to_pdx(0x50000000) is. > > Full logs here, and debug patch in attachment. Interesting. Up to ... > (XEN) Checking for initrd in /chosen > (XEN) RAM: 0000000000000000 - 000000007fffffff > (XEN) RAM: 0000000800000000 - 000000087fffffff > (XEN) RAM: 0000050000000000 - 000005007fffffff > (XEN) RAM: 0000060000000000 - 000006007fffffff > (XEN) RAM: 0000070000000000 - 000007007fffffff > (XEN) > (XEN) MODULE[0]: 0000000022000000 - 0000000022172fff Xen > (XEN) MODULE[1]: 0000000022200000 - 000000002220efff Device Tree > (XEN) MODULE[2]: 0000000020400000 - 0000000021e2ffff Kernel > (XEN) RESVD[0]: 0000000000000000 - 0000000000ffffff > (XEN) RESVD[1]: 0000000001000000 - 00000000015fffff > (XEN) RESVD[2]: 0000000001600000 - 00000000017fffff > (XEN) RESVD[3]: 0000000001800000 - 00000000097fffff > (XEN) RESVD[4]: 0000000009800000 - 000000000bffffff > (XEN) RESVD[5]: 0000000011126000 - 000000001114dfff > (XEN) RESVD[6]: 000000001114e000 - 000000001214efff > (XEN) RESVD[7]: 0000000017275000 - 000000001729cfff > (XEN) RESVD[8]: 000000001729d000 - 000000001829dfff > (XEN) RESVD[9]: 000000001a7df000 - 000000001a806fff > (XEN) RESVD[10]: 000000001a807000 - 000000001b807fff > (XEN) RESVD[11]: 000000001d908000 - 000000001d92ffff > (XEN) RESVD[12]: 000000001d930000 - 000000001e930fff > (XEN) RESVD[13]: 000000001829e000 - 000000001869dfff > (XEN) RESVD[14]: 000000001869e000 - 00000000186ddfff > (XEN) RESVD[15]: 0000000800000000 - 000000083fffffff > (XEN) > (XEN) > (XEN) Command line: console=dtuart dom0_mem=2048M console_timestamps=boot > debug bootscrub=0 vwfi=native sched=null > (XEN) [00000006bfc302ec] parameter "debug" unknown! > (XEN) [00000006bfcc0476] DEBUG init_pdx 294 start=0 end=80000000 > (XEN) [00000006bfcd2400] DEBUG init_pdx 294 start=800000000 end=880000000 > (XEN) [00000006bfce29ec] DEBUG init_pdx 294 start=50000000000 end=50080000000 > (XEN) [00000006bfcf1768] DEBUG init_pdx 294 start=60000000000 end=60080000000 > (XEN) [00000006bfd015a4] DEBUG init_pdx 294 start=70000000000 end=70080000000 > (XEN) [00000006bfd1444f] DEBUG setup_mm 252 > (XEN) [00000006bfd3dc6f] DEBUG setup_mm 273 start=0 size=80000000 > ram_end=80000000 directmap_base_pdx=0 > (XEN) [00000006bfd5616e] DEBUG setup_directmap_mappings 229 base_mfn=0 > nr_mfns=80000 directmap_base_pdx=0 mfn_to_pdx=0 > (XEN) [00000006bfd7d38a] DEBUG setup_directmap_mappings 237 base_mfn=0 > nr_mfns=80000 directmap_base_pdx=0 > (XEN) [00000006bfd92728] DEBUG setup_mm 273 start=800000000 size=80000000 > ram_end=880000000 directmap_base_pdx=0 > (XEN) [00000006bfdaba3b] DEBUG setup_directmap_mappings 229 base_mfn=800000 > nr_mfns=80000 directmap_base_pdx=0 mfn_to_pdx=800000 > (XEN) [00000006bfdcd79c] DEBUG setup_directmap_mappings 237 base_mfn=800000 > nr_mfns=80000 directmap_base_pdx=0 > (XEN) [00000006bfde4d82] DEBUG setup_mm 273 start=50000000000 size=80000000 > ram_end=50080000000 directmap_base_pdx=0 > (XEN) [00000006bfdfaef0] DEBUG setup_directmap_mappings 229 base_mfn=50000000 > nr_mfns=80000 directmap_base_pdx=0 mfn_to_pdx=50000000 > (XEN) [00000006bfe35249] Assertion '(mfn_to_pdx(maddr_to_mfn(ma)) - > directmap_base_pdx) < (DIRECTMAP_SIZE >> PAGE_SHIFT)' failed at > ./arch/arm/include/asm/mmu/mm.h:72 ... here there's no sign of PDX compression actually being set up; all that's there are the init_pdx() messages. Do you perhaps have an ordering problem on Arm? The register values ... > (XEN) [00000006bfe68507] ----[ Xen-4.21-unstable arm64 debug=y Not tainted > ]---- > (XEN) [00000006bfe766bf] CPU: 0 > (XEN) [00000006bfe832e0] PC: 00000a00002da70c setup_mm+0x284/0x308 > (XEN) [00000006bfea5b1a] LR: 00000a00002da6b0 > (XEN) [00000006bfeb1032] SP: 00000a0000327e00 > (XEN) [00000006bfebf403] CPSR: 00000000200003c9 MODE:64-bit EL2h > (Hypervisor, handler) > (XEN) [00000006bfed4634] X0: 0000000000000017 X1: 0000000000000000 X2: > 0000000050000000 > (XEN) [00000006bfee4d11] X3: 000000004fffffff X4: 0000000000000020 X5: > 0000000000000000 > (XEN) [00000006bfef48cf] X6: 0000000000000000 X7: 0000000000000000 X8: > ffffffffffffffff > (XEN) [00000006bff047ac] X9: fefefefefefeff09 X10: 0000000000000080 X11: > 0101010101010101 > (XEN) [00000006bff153b4] X12: 0000000000000008 X13: 0000000000000009 X14: > 0000000000000030 > (XEN) [00000006bff2620d] X15: 00000a0000a00000 X16: 00000a0000291478 X17: > 0000000000000000 > (XEN) [00000006bff35c41] X18: 000000007be9bbe0 X19: 00000a0000292c40 X20: > 00000a00002ade68 > (XEN) [00000006bff465a5] X21: 0000050080000000 X22: 0000000000000000 X23: > 0000000180000000 > (XEN) [00000006bff57a51] X24: 0000000000000002 X25: 00000a0000292c50 X26: > 0000000050000000 > (XEN) [00000006bff67d91] X27: 0000000000080000 X28: 0000050000000000 FP: > 00000a0000327e00 ... also suggest (x2, x3, and x26 in particular) that offsets are still all zero, i.e. PDX == MFN. And aiui DIRECTMAP_SIZE is 5Tb. Jan
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |