>>> On 08.12.14 at 03:30, <mdo...@bitdefender.com> wrote:
> +#ifndef NDEBUG
> +static bool_t xmem_pool_check_size(const struct bhdr *b, int fl, int sl)
> +{
> + while ( b )
> + {
> + int __fl;
> + int __sl;
> +
> + MAPPING_INSERT(b->size, &__fl, &__sl);
> + if ( __fl != fl || __sl != sl )
> + {
> + printk(XENLOG_ERR "xmem_pool: for block %p size = %u, { fl = %d,
> sl = %d } should be { fl = %d, sl = %d }\n",
Quoting my reply to v1: "Long line. Only the format message alone
is allowed to exceed 80 characters."
Also with there potentially being multiple pools, shouldn't all of the
log messages the patch issues be extended to allow identifying the
offending one?
> +bool_t __xmem_pool_check(const char *file, int line, struct xmem_pool *pool)
> +{
> + return __xmem_pool_check_unlocked(file, line, pool ? pool : xenpool);
For brevity, the shorter "pool ?: xenpool" is generally preferable. The
only place using this is not allowed are the public headers.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
