On Fri, Apr 05, 2013 at 02:06, Ted Unangst wrote:
> take 42. http://marc.info/?l=openbsd-tech&m=130999022613838&w=2
>
> Updated diff follows below. Add rrwlocks. Make lockmgr a wrapper shim.
> + * Copyright (c) 2011 Thordur Bjornsson
I suffered a minor highlighted text targeting failure here, b
take 42. http://marc.info/?l=openbsd-tech&m=130999022613838&w=2
Updated diff follows below. Add rrwlocks. Make lockmgr a wrapper shim.
Tests, oks, the whole nine yards, please. And maybe if I get lucky this
can get committed before it's two years old...
Index: kern/kern_lock.c
==
On Thu, Apr 04, 2013 at 11:06:16PM +0200, Mark Kettenis wrote:
> Machines with Intel integrated graphics have this concept of stolen
> memory; system memory set aside by the BIOS for use by the graphics
> chip. On OpenBSD we don't touch that memory since we don't want to
> step on the BIOS' toes.
This is a stupid simple diff to see just how much time you spend
waiting for your disk. If you're into measuring that kind of thing.
Index: vfs_bio.c
===
RCS file: /cvs/src/sys/kern/vfs_bio.c,v
retrieving revision 1.146
diff -u -p -r1
To prevent the future recurrence of some rather serious libc build
bugs, such as a macro like strong_alias suddenly turning into an
implicit function prototype, I think we should add some warnings and
use as much -Werror as possible. (I'm not entirely sure this would
have caught the missing strong_
Machines with Intel integrated graphics have this concept of stolen
memory; system memory set aside by the BIOS for use by the graphics
chip. On OpenBSD we don't touch that memory since we don't want to
step on the BIOS' toes. We also assume that this memory is mapped in
the graphics translation
On 04/03/13 09:08, Stuart Henderson wrote:
> moving this to tech@ - original message with dmesg is at
> http://marc.info/?l=openbsd-misc&m=136498447228598&w=2 - summary:
> asus P8H77-M, intel 7 series chipset, "Intel HD Graphics 3000"
> running i386 or amd64, fails during boot with recent kernels u
