diff options
| author | neel <neel@FreeBSD.org> | 2013-04-10 18:53:14 +0000 |
|---|---|---|
| committer | neel <neel@FreeBSD.org> | 2013-04-10 18:53:14 +0000 |
| commit | 6ca7b417ee49832652eca77c91604b20da8e93be (patch) | |
| tree | a2edd0a017ef3a0562b4e9938c50729ed86693b6 | |
| parent | 39a8419a58c1c36261f11f10e9ec509d1538e8cc (diff) | |
| download | FreeBSD-src-6ca7b417ee49832652eca77c91604b20da8e93be.zip FreeBSD-src-6ca7b417ee49832652eca77c91604b20da8e93be.tar.gz | |
Remove obsolete comment about lack of locking for MMIO range lookup.
Pointed out by: Tycho Nightingale (tycho.nightingale@plurisbusnetworks.com)
| -rw-r--r-- | usr.sbin/bhyve/mem.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/usr.sbin/bhyve/mem.c b/usr.sbin/bhyve/mem.c index 6d4f263..d5c7935 100644 --- a/usr.sbin/bhyve/mem.c +++ b/usr.sbin/bhyve/mem.c @@ -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> |
