Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Nov 2015 15:54:52 +0100
From:      Hans Petter Selasky <hps@selasky.org>
To:        David Chisnall <theraven@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com>
Cc:        cem@FreeBSD.org, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r290711 - head/sys/ofed/drivers/infiniband/core
Message-ID:  <5645F9BC.8020308@selasky.org>
In-Reply-To: <0330812D-2FB6-4490-BFB3-67F9E66975A7@FreeBSD.org>
References:  <201511121012.tACACKTI075143@repo.freebsd.org> <CAG6CVpWKsa3SwX27JpxBeQDikeDWJXyUGWG8sS=9DvzbML9xcA@mail.gmail.com> <56459CEE.4090007@selasky.org> <20151113083543.GV2257@kib.kiev.ua> <0330812D-2FB6-4490-BFB3-67F9E66975A7@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/13/15 15:10, David Chisnall wrote:
> Note that this is not true of all downstreams.  We currently have 128 and 256-bit void*s with 64-bit longs on CHERI, and I believe that bde’s version has 32-bit longs on all platforms.
>
> David

Hi David,

Converting the LinuxKPI to use uintptr_t instead of "unsigned long" is 
possible, though it affects several modules depending on the LinuxKPI 
which needs auditing, for this kind of issues. For now the LinuxKPI 
should not be built for CHERI. Sorry about the inconvenience.

Will a CHERI build warn if you cast from "long" to "void *"? Then 
cleaning up the code with this regard might be a very simple and 
straight forward task.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5645F9BC.8020308>