mirror of
https://git.FreeBSD.org/src.git
synced 2025-02-01 17:00:36 +00:00
Remove obsolete comment about lack of locking for MMIO range lookup.
Pointed out by: Tycho Nightingale (tycho.nightingale@plurisbusnetworks.com)
This commit is contained in:
parent
f0105d2d23
commit
f1280b3805
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=249342
@ -30,12 +30,6 @@
|
||||
* Memory ranges are represented with an RB tree. On insertion, the range
|
||||
* is checked for overlaps. On lookup, the key has the same base and limit
|
||||
* so it can be searched within the range.
|
||||
*
|
||||
* It is assumed that all setup of ranges takes place in single-threaded
|
||||
* mode before vCPUs have been started. As such, no locks are used on the
|
||||
* RB tree. If this is no longer the case, then a r/w lock could be used,
|
||||
* with readers on the lookup and a writer if the tree needs to be changed
|
||||
* (and per vCPU caches flushed)
|
||||
*/
|
||||
|
||||
#include <sys/cdefs.h>
|
||||
|
Loading…
Reference in New Issue
Block a user