On Mon, Sep 18, 2023 at 01:27:55PM -0500, Mike Karels wrote:
> On 18 Sep 2023, at 10:38, Michael Butler wrote:
>
> > On 8/8/23 13:50, Michael Butler wrote:
> >> On 8/8/23 10:56, Tomoaki AOKI wrote:
> >>> On Tue, 8 Aug 2023 17:02:32 +0300
> >>> Konstantin Belousov wrote:
> >>
> >> [ .. snip ..
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,
On 18 Sep 2023, at 10:38, Michael Butler wrote:
> On 8/8/23 13:50, Michael Butler wrote:
>> On 8/8/23 10:56, Tomoaki AOKI wrote:
>>> On Tue, 8 Aug 2023 17:02:32 +0300
>>> Konstantin Belousov wrote:
>>
>> [ .. snip .. ]
>>
The workaround is switched on automatically, when kernel detects
On 8/8/23 13:50, Michael Butler wrote:
On 8/8/23 10:56, Tomoaki AOKI wrote:
On Tue, 8 Aug 2023 17:02:32 +0300
Konstantin Belousov wrote:
[ .. snip .. ]
The workaround is switched on automatically, when kernel detects
'small cores'
reported by CPUID.
If I read the code correctly,
On Tue, Aug 8, 2023 at 10:50 AM Michael Butler
wrote:
> On 8/8/23 10:56, Tomoaki AOKI wrote:
> > On Tue, 8 Aug 2023 17:02:32 +0300
> > Konstantin Belousov wrote:
>
> [ .. snip .. ]
>
> >> The workaround is switched on automatically, when kernel detects 'small
> cores'
> >> reported by CPUID.
On 8/8/23 10:56, Tomoaki AOKI wrote:
On Tue, 8 Aug 2023 17:02:32 +0300
Konstantin Belousov wrote:
[ .. snip .. ]
The workaround is switched on automatically, when kernel detects 'small cores'
reported by CPUID.
If I read the code correctly, vm.pmap.pcid_invlpg_workaround
(precicely, the
On Tue, 8 Aug 2023 17:02:32 +0300
Konstantin Belousov wrote:
> On Tue, Aug 08, 2023 at 10:46:12PM +0900, Tomoaki AOKI wrote:
> > On Tue, 8 Aug 2023 15:38:46 +0300
> > Konstantin Belousov wrote:
> >
> > > On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> > > > On Sun, 6 Aug 2023
On Tue, Aug 08, 2023 at 10:46:12PM +0900, Tomoaki AOKI wrote:
> On Tue, 8 Aug 2023 15:38:46 +0300
> Konstantin Belousov wrote:
>
> > On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> > > On Sun, 6 Aug 2023 12:55:07 +0300
> > > Konstantin Belousov wrote:
> > >
> > > > On Sun, Aug
On Tue, 8 Aug 2023 15:38:46 +0300
Konstantin Belousov wrote:
> On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> > On Sun, 6 Aug 2023 12:55:07 +0300
> > Konstantin Belousov wrote:
> >
> > > On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> > > > On Wed, 23 Feb 2022
On Tue, Aug 08, 2023 at 06:37:35AM +0900, Tomoaki AOKI wrote:
> On Sun, 6 Aug 2023 12:55:07 +0300
> Konstantin Belousov wrote:
>
> > On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> > > On Wed, 23 Feb 2022 01:30:28 +0200
> > > Konstantin Belousov wrote:
> > >
> > > > On Tue, Feb
On Sun, 6 Aug 2023 12:55:07 +0300
Konstantin Belousov wrote:
> On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> > On Wed, 23 Feb 2022 01:30:28 +0200
> > Konstantin Belousov wrote:
> >
> > > On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> > > > On 22.02.2022
On Sun, Aug 06, 2023 at 06:12:38PM +0900, Tomoaki AOKI wrote:
> On Wed, 23 Feb 2022 01:30:28 +0200
> Konstantin Belousov wrote:
>
> > On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> > > On 22.02.2022 17:46, Konstantin Belousov wrote:
> > > > Ok, the next step is to get the CPU
On Wed, 23 Feb 2022 01:30:28 +0200
Konstantin Belousov wrote:
> On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> > On 22.02.2022 17:46, Konstantin Belousov wrote:
> > > Ok, the next step is to get the CPU feature reports from P- vs. E- cores.
> > > Patch below should work, with
Motin
Cc: Mike Karels; Tomoaki AOKI; Chen, Alvin W; freebsd-current@freebsd.org
Subject: Re: [Intel AlderLake] Read files to FAT32 or UFS partition cause
data corrupt due to P-Core
[EXTERNAL EMAIL]
On Wed, Feb 23, 2022 at 12:25:24PM -0500, Alexander Motin wrote:
> On 22.02.2022 19
On Wed, Feb 23, 2022 at 12:25:24PM -0500, Alexander Motin wrote:
> On 22.02.2022 19:00, Konstantin Belousov wrote:
> > On Tue, Feb 22, 2022 at 06:53:09PM -0500, Alexander Motin wrote:
> > > On 22.02.2022 18:41, Konstantin Belousov wrote:
> > > > On Tue, Feb 22, 2022 at 06:38:24PM -0500, Alexander
On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote:
> On 22.02.2022 17:46, Konstantin Belousov wrote:
> > Ok, the next step is to get the CPU feature reports from P- vs. E- cores.
> > Patch below should work, with verbose boot.
>
> Not much difference on that level:
>
> --- zzzp
On 22.02.2022 17:46, Konstantin Belousov wrote:
Ok, the next step is to get the CPU feature reports from P- vs. E- cores.
Patch below should work, with verbose boot.
Not much difference on that level:
--- zzzp2022-02-22 18:18:24.531704000 -0500
+++ zzze2022-02-22
On Sat, Feb 19, 2022 at 07:26:24PM -0500, Alexander Motin wrote:
> On 19.02.2022 13:23, Konstantin Belousov wrote:
> > On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
> > > On 19.02.2022 12:02, Mike Karels wrote:
> > > > On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> > > > > Just
On 19.02.2022 13:23, Konstantin Belousov wrote:
On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
On 19.02.2022 12:02, Mike Karels wrote:
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
Just a thought, but can it be the reason with timing (e.g., rendezvous
within (i)threads,
On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
> On 19.02.2022 12:02, Mike Karels wrote:
> > On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> > > Just a thought, but can it be the reason with timing (e.g., rendezvous
> > > within (i)threads, hardware controlls without using
On 19.02.2022 12:02, Mike Karels wrote:
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
Just a thought, but can it be the reason with timing (e.g., rendezvous
within (i)threads, hardware controlls without using hardware timer)
problem?
On FreeBSD, IIUC, multi processor (multi core)
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> Just a thought, but can it be the reason with timing (e.g., rendezvous
> within (i)threads, hardware controlls without using hardware timer)
> problem?
>
> On FreeBSD, IIUC, multi processor (multi core) implementation assumes
> SMP (differs only
Just a thought, but can it be the reason with timing (e.g., rendezvous
within (i)threads, hardware controlls without using hardware timer)
problem?
On FreeBSD, IIUC, multi processor (multi core) implementation assumes
SMP (differs only clock speed) and end up with difference of
performance at
This looks pretty weird to me, but I don't think it is specific to the
FAT32. Just today I've first noticed that booting TrueNAS 12.0-U8
(http://download.freenas.org/12.0/STABLE/U8/x64/TrueNAS-12.0-U8.iso)
(based on FreeBSD 12.2 with many backports) from NVMe SSD (I don't
insist on NVMe so
24 matches
Mail list logo