[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5628CE82.7090105@linaro.org>
Date: Thu, 22 Oct 2015 13:54:42 +0200
From: Eric Auger <eric.auger@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: eric.auger@...com, alex.williamson@...hat.com,
b.reynal@...tualopensystems.com,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
kvm@...r.kernel.org, christoffer.dall@...aro.org,
linux-kernel@...r.kernel.org, patches@...aro.org
Subject: Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset
function registration
On 10/22/2015 12:13 PM, Arnd Bergmann wrote:
> On Thursday 22 October 2015 11:41:59 Eric Auger wrote:
>> This patch adds the reset function registration/unregistration.
>>
>> Signed-off-by: Eric Auger <eric.auger@...aro.org>
>
> Looks good, except one thing:
>> @@ -70,6 +69,8 @@ int vfio_platform_calxedaxgmac_reset(struct vfio_platform_device *vdev)
>> return -ENOMEM;
>> }
>>
>> + pr_info("VFIO reset of %s\n", vdev->name);
>> +
>> /* disable IRQ */
>> writel(0, reg.ioaddr + XGMAC_DMA_INTR_ENA);
>>
>
> This probably slipped in from debugging, please remove it.
Well actually this is not an oversight but some unappropriate tracing
attempt I am afraid. I wanted to add a trace useful for the end-user to
make sure the VFIO reset function was called. Do you forbid that or do
recommend to use another tracing mechanism/level? In the past I tried
dynamic tracing but with module loading mechanism I found it not that handy.
Eric
>
> Arnd
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists