[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <0866384c-990f-40b2-8815-2525f9323453@app.fastmail.com>
Date: Sun, 22 Dec 2024 22:19:39 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "kernel test robot" <oliver.sang@...el.com>,
"Arnd Bergmann" <arnd@...nel.org>
Cc: oe-lkp@...ts.linux.dev, "kernel test robot" <lkp@...el.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org,
"Thomas Gleixner" <tglx@...utronix.de>, "Ingo Molnar" <mingo@...hat.com>,
"Borislav Petkov" <bp@...en8.de>,
"Dave Hansen" <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Andy Shevchenko" <andy@...nel.org>, "Matthew Wilcox" <willy@...radead.org>
Subject: Re: [PATCH v2 07/11] x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
On Fri, Dec 20, 2024, at 03:52, kernel test robot wrote:
>
> config: i386-randconfig-001-20241213
> compiler: gcc-12
> test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
I haven't been able to figure this out, apparently something goes
wrong on a KVM guest that has more than 32-bit of addressing (RAM+MMIO)
when it uses a 32-bit phys_addr_t.
I changed the patch now to only drop SWIOTLB, not PHYS_ADDR_T_64BIT.
Arnd
Powered by blists - more mailing lists