Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)

[Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>]

The following reply was made to PR kern/52111; it has been noted by GNATS.

From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	Frank Kardel <kardel%netbsd.org@localhost>
Subject: Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
Date: Mon, 27 Mar 2017 11:12:10 +0200

 Right, a function would be good. E.g. nvme(4) also uses ncpu, so would
 fail the same way when system for 'boot -1'. But maybe the bug is in
 that ncpu is set wrongly in this case? I mean, is there a way to
 activate the additional cpus after the system is booted with -1?
 
 Jaromir
 
 2017-03-27 10:45 GMT+02:00 Martin Husemann <martin%duskware.de@localhost>:
 > The following reply was made to PR kern/52111; it has been noted by GNATS.
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>
 > Cc: gnats-bugs%NetBSD.org@localhost
 > Subject: Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
 > Date: Mon, 27 Mar 2017 10:42:33 +0200
 >
 >  On Mon, Mar 27, 2017 at 11:27:17AM +0900, Kengo NAKAHARA wrote:
 >  > Hmm...., It is strange to me that wm(4) use two TX and RX interrupts on
 >  > uniprocessor system.
 >
 >  He means using "boot -1" on a multiprocessor system.
 >
 >  I don't know if on x86 that makes ncpu be 1 or if wm should better use
 >  ncpuonline instead. The pool code seems to use
 >
 >         if (ncpu < 2 || !mp_online)
 >
 >  instead, maybe we should provide a simple inline function and make it
 >  all the same?
 >
 >  Martin
 >