Date: Mon, 18 Sep 2023 17:13:20 -0400 From: Michael Butler <imb@protected-networks.net> To: Mike Karels <mike@karels.net> Cc: freebsd-current@freebsd.org Subject: Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Message-ID: <31fa46dc-3de3-0bc6-f675-92d2be35eccd@protected-networks.net> In-Reply-To: <77F5DC92-726E-4F26-ACEA-0AF92E0AF5D2@karels.net> References: <YhE1rWoA%2BhMfebq/@kib.kiev.ua> <59cbcfe2-cd53-69d8-65d6-7a79e656f494@FreeBSD.org> <YhVnsB5ZwLYmpAFP@kib.kiev.ua> <1f968af1-1c57-9a09-7e01-145a5262e27f@FreeBSD.org> <YhVyFIFA5XnbGHej@kib.kiev.ua> <20230806181238.858f58e25dfd0f99269cfe53@dec.sakura.ne.jp> <ZM9t--jEqyc4_Z4t@kib.kiev.ua> <20230808063735.e8e1d3ede370a18f200a6f48@dec.sakura.ne.jp> <ZNI3VoFklDaSED59@kib.kiev.ua> <20230808224612.c3889d6e20b6fc980f5278cc@dec.sakura.ne.jp> <ZNJK-PPUhm00ndXs@kib.kiev.ua> <20230808235635.744e0e1c6a72face7fdf6a9b@dec.sakura.ne.jp> <4f0fbb44-eebe-aa8f-f958-dcd678936fe1@protected-networks.net> <946c1f29-dd2a-776d-e88d-7523c103b221@protected-networks.net> <77F5DC92-726E-4F26-ACEA-0AF92E0AF5D2@karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/18/23 14:27, Mike Karels wrote: [ .. snip .. ] >>> avail memory = 16363008000 (15604 MB) >>> CPU microcode: updated from 0xc to 0x10 >> >> With the most recent microcode update, this device reports .. >> >> CPU microcode: updated from 0xc to 0x11 >> >> .. and is now stable with vm.pmap.pcid_enabled=0, vm.pmap.pcid_invlpg_workaround=1, and CPUTYPE?=alderlake set in /etc/make.conf over multiple full system builds. >> >> I have not tested with vm.pmap.pcid_invlpg_workaround=0. <sigh> .. sorry that was a typo .. I'm actually using .. vm.pmap.pcid_invlpg_workaround: 1 vm.pmap.invpcid_works: 1 vm.pmap.pcid_enabled: 1 > I believe that vm.pmap.pcid_invlpg_workaround does not matter if > vm.pmap.pcid_enabled=0. Enabling the workaround or disabling pcid should > be basically the same for this CPU, so I don't understand why that isn't > true. It might be interesting to test with pcid enabled with the new > microcode, although I don't see why that would affect the results (pcid > should still not be used on any CPU). > > The CPUTYPE for the compiler should not affect the pcid vm issues, just > change the optimization by the compiler. Agreed. However, I was previously using CPUTYPE?=tremont so I just wanted to note that two things had changed in my testing, microcode and CPUTYPE, not just one, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31fa46dc-3de3-0bc6-f675-92d2be35eccd>