NetBSD Problem Report #41099

From rmind@NetBSD.org  Mon Mar 30 14:24:20 2009
Return-Path: <rmind@NetBSD.org>
Received: by www.NetBSD.org (Postfix, from userid 1391)
	id 9C17D63B8C8; Mon, 30 Mar 2009 14:24:20 +0000 (UTC)
Message-Id: <20090330142420.9C17D63B8C8@www.NetBSD.org>
Date: Mon, 30 Mar 2009 14:24:20 +0000 (UTC)
From: rmind@NetBSD.org
Reply-To: rmind@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: CPU_INFO_FOREACH / CPU_INFO_ITERATOR issues
X-Send-Pr-Version: 3.95

>Number:         41099
>Category:       kern
>Synopsis:       CPU_INFO_FOREACH / CPU_INFO_ITERATOR issues
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    rmind
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 30 14:25:00 +0000 2009
>Last-Modified:  Wed Apr 15 23:27:04 +0000 2009
>Originator:     Mindaugas Rasiukevicius
>Release:        NetBSD -current
>Organization:
The NetBSD Project
>Environment:
>Description:

There are issues with the CPU_INFO_FOREACH / CPU_INFO_ITERATOR interface:

- Order of CPU list is not strict, therefore double-locking of CPUs 
  (eg. if (ci1 > ci2) assumptions) and locking of all CPUs is unsafe.

- There is no clear abstraction of struct cpu_info into MI and MD.

- Interface could be dynamic to support CPU attach/detach on runtime.

>How-To-Repeat:
Code inspection.
>Fix:
Implement dynamic MI interface.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->rmind
Responsible-Changed-By: rmind@NetBSD.org
Responsible-Changed-When: Wed, 15 Apr 2009 23:27:04 +0000
Responsible-Changed-Why:
Take, so I wont forget it.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.