Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Nov 2015 02:50:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 204685] panic: mp_setmaxid: one CPU but mp_maxid is not zero
Message-ID:  <bug-204685-8-ln54axQH8g@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204685-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-204685-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204685

--- Comment #5 from commit-hook@freebsd.org ---
A commit references this bug:

Author: marius
Date: Sat Nov 21 02:49:33 UTC 2015
New revision: 291121
URL: https://svnweb.freebsd.org/changeset/base/291121

Log:
  Merge from r290547:
  Since r289279 bufinit() uses mp_ncpus so adapt to what x86 does and
  set this variable already in cpu_mp_setmaxid().
  While at it, rename cpu_cpuid_prop() to cpu_portid_prop() as well as
  the MD cpuid variable to portid to avoid confusion with the MI use
  of "cpuid" and make some variable static/global in order to reduce
  stack usage.

  PR:        204685

Changes:
  head/sys/sparc64/include/md_var.h
  head/sys/sparc64/sparc64/machdep.c
  head/sys/sparc64/sparc64/mp_machdep.c

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204685-8-ln54axQH8g>