On 11/28/19 7:52 AM, Konstantin Belousov wrote:
On Thu, Nov 28, 2019 at 09:17:15AM +, Andrew Turner wrote:
On 28 Nov 2019, at 08:48, Michal Meloun wrote:
On 27.11.2019 21:33, Alan Cox wrote:
Author: alc
Date: Wed Nov 27 20:33:49 2019
New Revision: 355145
URL:
On Thu, Nov 28, 2019 at 09:17:15AM +, Andrew Turner wrote:
>
>
> > On 28 Nov 2019, at 08:48, Michal Meloun wrote:
> >
> >
> >
> > On 27.11.2019 21:33, Alan Cox wrote:
> >> Author: alc
> >> Date: Wed Nov 27 20:33:49 2019
> >> New Revision: 355145
> >> URL:
> On 28 Nov 2019, at 08:48, Michal Meloun wrote:
>
>
>
> On 27.11.2019 21:33, Alan Cox wrote:
>> Author: alc
>> Date: Wed Nov 27 20:33:49 2019
>> New Revision: 355145
>> URL: https://svnweb.freebsd.org/changeset/base/355145
>>
>> Log:
>> There is no reason why we need to pin the
On 27.11.2019 21:33, Alan Cox wrote:
> Author: alc
> Date: Wed Nov 27 20:33:49 2019
> New Revision: 355145
> URL: https://svnweb.freebsd.org/changeset/base/355145
>
> Log:
> There is no reason why we need to pin the underlying thread to its current
> processor in
Author: alc
Date: Wed Nov 27 20:33:49 2019
New Revision: 355145
URL: https://svnweb.freebsd.org/changeset/base/355145
Log:
There is no reason why we need to pin the underlying thread to its current
processor in pmap_invalidate_{all,page,range}(). These functions are using
an instruction