X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org B48DB385E027
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=maxrnd.com
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=mark AT maxrnd DOT com
Subject:	Re: Why is taskset still not in util-linux?
To:	cygwin AT cygwin DOT com
References:	<1348011a-261a-2a87-d361-4e51fa8dc19f AT cs DOT umass DOT edu>
	<85ae12aa-6cc3-5d4c-5df2-25bf811ec6a9 AT maxrnd DOT com>
	<72fea68a-b3d7-e87c-726f-8a5a2587a992 AT maxrnd DOT com>
	<01e3d337-e5fe-f393-7634-3f1881bca315 AT cs DOT umass DOT edu>
	<dca24f26-9da9-591c-19c1-8020e5de3a4e AT maxrnd DOT com>
	<79d7afa5-a07b-04df-c259-b76c61390f8c AT maxrnd DOT com>
	<92157259-166d-a85d-2db7-a8e30c75ec09 AT cs DOT umass DOT edu>
	<99d74893-f9f8-4d8d-a400-dfe247660bf0 AT maxrnd DOT com>
	<ad8159c0-db0d-2501-fe22-c295833725bc AT SystematicSw DOT ab DOT ca>
	<20200323093158 DOT GA3261 AT calimero DOT vinschen DOT de>
From:	Mark Geisert <mark AT maxrnd DOT com>
Message-ID:	<ee3b6112-dc3e-6245-0abe-8b5410515547@maxrnd.com>
Date:	Mon, 23 Mar 2020 02:42:15 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
	Firefox/52.0 SeaMonkey/2.49.4
MIME-Version:	1.0
In-Reply-To:	<20200323093158.GA3261@calimero.vinschen.de>
X-Spam-Status:	No, score=-13.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	Cygwin mailing list <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<http://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 02N9gxq6025806

Corinna Vinschen wrote:
> On Mar 21 10:41, Brian Inglis wrote:
>> On 2020-03-21 02:18, Mark Geisert wrote:
>>> Eliot Moss wrote:
>>>> On 3/20/2020 1:54 AM, Mark Geisert wrote:
>>>>> I've reproduced your snags. It/they are due to my having forgotten
>>>>> another tiny update that should have been part of the
>>>>> 2.33.1-cygwin-cpuset.patch file.  If you
>>>>> 'echo "#define SYS_sched_getaffinity 42" > /usr/local/include/sys/syscall.h'
>>>>> and then back out your other fix attempts, the build using cygport should
>>>>> work.
>>>> Once I did that properly, it built without commenting out that test. Yay!
>>
>>> I ended up installing Process Lasso to follow processes among the cpus and to
>>> test the Cygwin affinity mask implementation.  It has a free trial period.  And
>>> I wrote a simple test program that just advances from one cpu to the next
>>> repeatedly, cpu-bound between steps, so PL can display the changing cpu.
>>
>> Anyone know if this feature support or what feature support will get top P/last
>> used CPU and/or procps-ng P/sgi_p currently executing CPU and PSR/currently
>> assigned CPU showing actual CPUs rather than 0/zero?
>>
>> Anyone know if or where or how this info is available on Windows or a link to
>> it? I've looked at Google and SO results and nothing useful is apparent.
> 
> Can't we just fake the calls?

Brian is asking for a way to watch processes globally, as they are scheduled 
back and forth on the available cpus.  I was a bit sloppy in my wording above; 
what Process Lasso displays is the changing process affinity mask for a process 
I wrote to do just that.  I don't know of a way to ask Windows which cpu a 
process is currently scheduled onto.

..mark
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -