[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-x68k/51663 (crash dump related bugs in x68k/machdep.c)
The following reply was made to PR port-x68k/51663; it has been noted by GNATS.
From: Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost>
To: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
Subject: Re: port-x68k/51663 (crash dump related bugs in x68k/machdep.c)
Date: Thu, 1 Dec 2016 12:38:27 +0900
On 2016/12/01 6:49, Izumi Tsutsui wrote:
> I slightly modified your patch and have confirmed it on my X68030
> (which has no highmem, so it just means "no bad side effect").
> Changes are:
> - use psize_t (instead of int) for "size" of memory regions
> - explicitly calculate size of basemem_seg (for future readers)
> even though phys_basemem_seg.start (== lowram) is zero on x68k
> Could you also confirm? (sorry I'm so lazy not to setup XM6i)
Thank you for your revision. It seems very reasonable to me. I've
tested your patch on XM6i with 12MB of base memory and the following
layouts of extended memory:
(1) 16MB at 0x01000000 (TS-6BE16 mode)
(2) 128MB at 0x10000000 (060turbo mode)
(3) 240MB at 0x01000000 and 768MB at 0x01000000
dmesg, ps, vmstat, and gdb work just fine for the all layouts.
Main Index |
Thread Index |