All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kvm@vger.kernel.org, patches@linaro.org,
	linux-kernel@vger.kernel.org, alex.williamson@redhat.com,
	eric.auger@st.com, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration
Date: Thu, 22 Oct 2015 13:54:42 +0200	[thread overview]
Message-ID: <5628CE82.7090105@linaro.org> (raw)
In-Reply-To: <4810974.apRDTjc3oB@wuerfel>

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@linaro.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
> 

WARNING: multiple messages have this Message-ID (diff)
From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration
Date: Thu, 22 Oct 2015 13:54:42 +0200	[thread overview]
Message-ID: <5628CE82.7090105@linaro.org> (raw)
In-Reply-To: <4810974.apRDTjc3oB@wuerfel>

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@linaro.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
> 

WARNING: multiple messages have this Message-ID (diff)
From: Eric Auger <eric.auger@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: eric.auger@st.com, alex.williamson@redhat.com,
	b.reynal@virtualopensystems.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	christoffer.dall@linaro.org, linux-kernel@vger.kernel.org,
	patches@linaro.org
Subject: Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration
Date: Thu, 22 Oct 2015 13:54:42 +0200	[thread overview]
Message-ID: <5628CE82.7090105@linaro.org> (raw)
In-Reply-To: <4810974.apRDTjc3oB@wuerfel>

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@linaro.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
> 


  reply	other threads:[~2015-10-22 11:52 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  9:41 [PATCH v2 0/6] VFIO platform reset module rework Eric Auger
2015-10-22  9:41 ` Eric Auger
2015-10-22  9:41 ` [PATCH v2 1/6] vfio: platform: add capability to register a reset function Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22 10:06   ` Arnd Bergmann
2015-10-22 10:06     ` Arnd Bergmann
2015-10-22  9:41 ` [PATCH v2 2/6] vfio: platform: reset: add vfio_platform_reset_private.h Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22 10:12   ` Arnd Bergmann
2015-10-22 10:12     ` Arnd Bergmann
2015-10-22 10:12     ` Arnd Bergmann
2015-10-22  9:41 ` [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22  9:41   ` Eric Auger
2015-10-22 10:13   ` Arnd Bergmann
2015-10-22 10:13     ` Arnd Bergmann
2015-10-22 11:54     ` Eric Auger [this message]
2015-10-22 11:54       ` Eric Auger
2015-10-22 11:54       ` Eric Auger
2015-10-22 12:09       ` Arnd Bergmann
2015-10-22 12:09         ` Arnd Bergmann
2015-10-22 12:29         ` Eric Auger
2015-10-22 12:29           ` Eric Auger
2015-10-22 12:29           ` Eric Auger
2015-10-22  9:42 ` [PATCH v2 4/6] vfio: platform: add compat in vfio_platform_device Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22  9:42 ` [PATCH v2 5/6] vfio: platform: use list of registered reset function Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22 10:19   ` Arnd Bergmann
2015-10-22 10:19     ` Arnd Bergmann
2015-10-22 10:19     ` Arnd Bergmann
2015-10-22 11:46     ` Eric Auger
2015-10-22 11:46       ` Eric Auger
2015-10-22 11:46       ` Eric Auger
2015-10-22  9:42 ` [PATCH v2 6/6] vfio: platform: move get/put reset at open/release Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22  9:42   ` Eric Auger
2015-10-22 10:29   ` Arnd Bergmann
2015-10-22 10:29     ` Arnd Bergmann
2015-10-22 10:29     ` Arnd Bergmann
2015-10-22 11:40     ` Eric Auger
2015-10-22 11:40       ` Eric Auger
2015-10-22 12:05       ` Arnd Bergmann
2015-10-22 12:05         ` Arnd Bergmann
2015-10-22 12:27         ` Eric Auger
2015-10-22 12:27           ` Eric Auger
2015-10-22 12:27           ` Eric Auger
2015-10-22 13:26     ` Eric Auger
2015-10-22 13:26       ` Eric Auger
2015-10-22 13:26       ` Eric Auger
2015-10-22 14:10       ` Arnd Bergmann
2015-10-22 14:10         ` Arnd Bergmann
2015-10-22 14:10         ` Arnd Bergmann
2015-10-22 14:23         ` Eric Auger
2015-10-22 14:23           ` Eric Auger
2015-10-22 14:23           ` Eric Auger
2015-10-22 15:40           ` Alex Williamson
2015-10-22 15:40             ` Alex Williamson
2015-10-22 15:40             ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5628CE82.7090105@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=arnd@arndb.de \
    --cc=eric.auger@st.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.