Date: Wed, 4 Jun 2003 15:01:57 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Alan Robinson <alan.robinson@fujitsu-siemens.com> Cc: freebsd-ia64@freebsd.org Subject: Re: /dev/kmem read return value is double requested value Message-ID: <20030604220157.GA2368@athlon.pn.xcllnt.net> In-Reply-To: <20030603085052.A2520@fujitsu-siemens.com> References: <20030530132408.A3690@fujitsu-siemens.com> <20030530173029.GB568@dhcp01.pn.xcllnt.net> <20030602133112.A3892@fujitsu-siemens.com> <20030602215156.GB1345@dhcp01.pn.xcllnt.net> <20030603085052.A2520@fujitsu-siemens.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 03, 2003 at 08:50:52AM +0200, Alan Robinson wrote: > > > I'll take a look at it when I have a spare cycle. > > > I compared the ia64/i386 mmrw() and another answer is to add > a 'continue' after the /dev/kmem uiomove just like in i386. Fix committed. Thanks. BTW: don't try to read from the direct mapped regions (region 6 or region 7) with an address that uses the unimplemented phys. address bits. Instant machine check. I don't know what happens if the physical address is valid (from an architectural POV), but there's no memory installed at that address. Also, I don't know what happens if we access UC memory through region 7 (WB). In short: the direct mapped case is extremely buggy. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030604220157.GA2368>