Date: Fri, 30 Dec 2005 15:17:41 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_malloc.c src/sys/sys malloc.h src/sys/vm memguard.c memguard.h Message-ID: <20051230141741.GG779@garage.freebsd.pl> In-Reply-To: <200512300904.14227.jhb@freebsd.org> References: <200512301145.jBUBj7fW043290@repoman.freebsd.org> <200512300815.57417.jhb@freebsd.org> <20051230134215.GE779@garage.freebsd.pl> <200512300904.14227.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--kadn00tgSopKmJ1H Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 30, 2005 at 09:04:12AM -0500, John Baldwin wrote: +> For the case I quoted (_before_ kldload) you must be doing all that chec= king=20 +> when you load the module either via MOD_LOAD in a module event or a SYSI= NIT. =20 +> In that case, setting the tunable via kenv before you kldload is identic= al to=20 +> setting the tunable in the loader, then booting and then kldloading the= =20 +> module. I understand, but in memguard's case, vm.memguard.desc is part of the kernel, not the module and I don't know when module is loaded from memguard. The module also knows nothing about memguard. I see your point in general case, but it doesn't fits here. Sorry if my commit log wasn't clear about that. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --kadn00tgSopKmJ1H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDtUGFForvXbEpPzQRAmJaAKDKFdXb3eX5cU+5PQg0XxMOvQlANACguNf9 htjiWx/rb3IkYEfFwfDFCYk= =OR/f -----END PGP SIGNATURE----- --kadn00tgSopKmJ1H--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051230141741.GG779>