Date: Mon, 14 Nov 2022 06:50:20 +0000 From: "Chen, Alvin W" <Weike.Chen@Dell.com> To: Mike Karels <mike@karels.net> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: RE: Status of Intel Hybrid CPU support (Alder Lake/Raptor Lake) support Message-ID: <PH0PR19MB4938527239BDA1AA6FFE5C129E059@PH0PR19MB4938.namprd19.prod.outlook.com> In-Reply-To: <CB6714BB-F070-436A-9324-1053648A7DE6@karels.net> References: <PH0PR19MB49386F16177AC787CFFAD05C9E339@PH0PR19MB4938.namprd19.prod.outlook.com> <CB6714BB-F070-436A-9324-1053648A7DE6@karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Internal Use - Confidential > -----Original Message----- > From: Mike Karels <mike@karels.net> > Sent: 2022年10月27日 23:17 > To: Chen, Alvin W > Cc: freebsd-current > Subject: Re: Status of Intel Hybrid CPU support (Alder Lake/Raptor Lake) > support > > > [EXTERNAL EMAIL] > > On 26 Oct 2022, at 22:29, Chen, Alvin W wrote: > > > Any body know the status to support P Core and E Core? > > Now WA is: disable PCID. > > Disabling vm.pmap.pcid_enabled is the best workaround for now. > There has been some progress in investigations in the background, but I don’t > think there is a permanent solution yet. > > btw, I haven’t heard reports about Raptor Lake yet. Do you know if it has the > same problems as Alder Lake on hybrids? I would guess it does. > I get one RPL-S DVT, and it hasn't mode name yet as it is the engineering CPU intel provided for validation. Based on my testing, the issue is still there: "Boot to shell by USB disk installer, and mount a FAT32 partition (on SSD), and copy a 300MB file to the FAT32, compare the sha256 checksums for the source file and the dst file, the checksum are different."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PH0PR19MB4938527239BDA1AA6FFE5C129E059>