Date: Tue, 12 Mar 2002 22:11:02 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Dag-Erling Smorgrav <des@ofug.org> Cc: arch@FreeBSD.ORG, peter@FreeBSD.ORG, jake@FreeBSD.ORG Subject: Re: dumpsys() rewrite Message-ID: <16769.1015967462@critter.freebsd.dk> In-Reply-To: Your message of "12 Mar 2002 22:07:38 %2B0100." <xzphenltrz9.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzphenltrz9.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes: >Poul-Henning Kamp <phk@critter.freebsd.dk> writes: >> `) Device driver or proxy for it register their ability to do dumps >> with the kernel, informing the kernel about the number of bytes >> they have room for (and the sector size of the media ?). > >Umm, no - it's simpler to just have a driver-provided helper for >disk_dumpcheck(), rather than a system for registering dump-capable >devices. > >BTW, this reminds me that the device should "know" that it's the >current dump device, so it can clear dumpdev if it disappears (e.g. >you 'camcontrol stop' the disk and remove it from the enclosure...) That is what I am talking about. You need to leave the driver (or a proxy for it: GEOM or the mini disk-layer) say "I can dump you this many bytes should you need it" or "I can no longer dump for you" As for registration, just add them to an EVENTHANDLER and you're done. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16769.1015967462>