From owner-freebsd-current@freebsd.org Wed Dec 11 11:12:21 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 36C961D41F1 for ; Wed, 11 Dec 2019 11:12:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47XvQs0mBmz40P4; Wed, 11 Dec 2019 11:12:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id BD5F226017B; Wed, 11 Dec 2019 12:03:59 +0100 (CET) Subject: Re: any scheduler/ipi/wakeup bug fixed in the last year? To: Andriy Gapon , FreeBSD Current References: <7196727c-77bd-8c96-5194-3dcc7277d4bd@FreeBSD.org> From: Hans Petter Selasky Message-ID: Date: Wed, 11 Dec 2019 12:02:34 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <7196727c-77bd-8c96-5194-3dcc7277d4bd@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47XvQs0mBmz40P4 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2019 11:12:21 -0000 > I wonder if there have been any bug fixes in that area over the past year or so. > Any help and pointers are welcome. Hi, A long time ago I fixed an issue for ARM: http://svnweb.freebsd.org/changeset/base/265913 I've always wondered why x86 does some fixed amount of idle spins before going to sleep. --HPS