All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Gabriel Somlo <somlo@cmu.edu>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vasyl Gomonovych <gomonovych@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fw_cfg: avoid unused function warning
Date: Wed, 28 Feb 2018 15:22:51 +0100	[thread overview]
Message-ID: <CAMxuvayxXG2526Z6p7-fEJM_sVefn8EkjWnY=ZozuiS_UiJS2Q@mail.gmail.com> (raw)
In-Reply-To: <20180228133357.1848600-1-arnd@arndb.de>

Hi

On Wed, Feb 28, 2018 at 2:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> The newly introduced fw_cfg_dma_transfer() function is unused when
> CONFIG_CRASH_CORE is disabled:
>
> drivers/firmware/qemu_fw_cfg.c:89:16: error: 'fw_cfg_dma_transfer' defined but not used [-Werror=unused-function]
>  static ssize_t fw_cfg_dma_transfer(void *address, u32 length, u32 control)
>
> This moves it into the #ifdef section that hides its caller to avoid the
> warning.
>
> Fixes: 47e78bfb5426 ("fw_cfg: write vmcoreinfo details")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

I don't know from which tree you found this, I suppose from
mst/linux-next (which btw, I don't know which version got partially
applied).

This is a regression in v13, because dma read is last patch now, as RFC.
Fixed in upcoming v16.

thanks

> ---
>  drivers/firmware/qemu_fw_cfg.c | 60 +++++++++++++++++++++---------------------
>  1 file changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/firmware/qemu_fw_cfg.c b/drivers/firmware/qemu_fw_cfg.c
> index 3015e77aebca..f002bb40519b 100644
> --- a/drivers/firmware/qemu_fw_cfg.c
> +++ b/drivers/firmware/qemu_fw_cfg.c
> @@ -66,6 +66,36 @@ static void fw_cfg_sel_endianness(u16 key)
>                 iowrite16(key, fw_cfg_reg_ctrl);
>  }
>
> +/* read chunk of given fw_cfg blob (caller responsible for sanity-check) */
> +static ssize_t fw_cfg_read_blob(u16 key,
> +                               void *buf, loff_t pos, size_t count)
> +{
> +       u32 glk = -1U;
> +       acpi_status status;
> +
> +       /* If we have ACPI, ensure mutual exclusion against any potential
> +        * device access by the firmware, e.g. via AML methods:
> +        */
> +       status = acpi_acquire_global_lock(ACPI_WAIT_FOREVER, &glk);
> +       if (ACPI_FAILURE(status) && status != AE_NOT_CONFIGURED) {
> +               /* Should never get here */
> +               WARN(1, "fw_cfg_read_blob: Failed to lock ACPI!\n");
> +               memset(buf, 0, count);
> +               return -EINVAL;
> +       }
> +
> +       mutex_lock(&fw_cfg_dev_lock);
> +       fw_cfg_sel_endianness(key);
> +       while (pos-- > 0)
> +               ioread8(fw_cfg_reg_data);
> +       ioread8_rep(fw_cfg_reg_data, buf, count);
> +       mutex_unlock(&fw_cfg_dev_lock);
> +
> +       acpi_release_global_lock(glk);
> +       return count;
> +}
> +
> +#ifdef CONFIG_CRASH_CORE
>  static inline bool fw_cfg_dma_enabled(void)
>  {
>         return (fw_cfg_rev & FW_CFG_VERSION_DMA) && fw_cfg_reg_dma;
> @@ -124,36 +154,6 @@ static ssize_t fw_cfg_dma_transfer(void *address, u32 length, u32 control)
>         return ret;
>  }
>
> -/* read chunk of given fw_cfg blob (caller responsible for sanity-check) */
> -static ssize_t fw_cfg_read_blob(u16 key,
> -                               void *buf, loff_t pos, size_t count)
> -{
> -       u32 glk = -1U;
> -       acpi_status status;
> -
> -       /* If we have ACPI, ensure mutual exclusion against any potential
> -        * device access by the firmware, e.g. via AML methods:
> -        */
> -       status = acpi_acquire_global_lock(ACPI_WAIT_FOREVER, &glk);
> -       if (ACPI_FAILURE(status) && status != AE_NOT_CONFIGURED) {
> -               /* Should never get here */
> -               WARN(1, "fw_cfg_read_blob: Failed to lock ACPI!\n");
> -               memset(buf, 0, count);
> -               return -EINVAL;
> -       }
> -
> -       mutex_lock(&fw_cfg_dev_lock);
> -       fw_cfg_sel_endianness(key);
> -       while (pos-- > 0)
> -               ioread8(fw_cfg_reg_data);
> -       ioread8_rep(fw_cfg_reg_data, buf, count);
> -       mutex_unlock(&fw_cfg_dev_lock);
> -
> -       acpi_release_global_lock(glk);
> -       return count;
> -}
> -
> -#ifdef CONFIG_CRASH_CORE
>  /* write chunk of given fw_cfg blob (caller responsible for sanity-check) */
>  static ssize_t fw_cfg_write_blob(u16 key,
>                                  void *buf, loff_t pos, size_t count)
> --
> 2.9.0
>

WARNING: multiple messages have this Message-ID (diff)
From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Gabriel Somlo <somlo@cmu.edu>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vasyl Gomonovych <gomonovych@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] fw_cfg: avoid unused function warning
Date: Wed, 28 Feb 2018 15:22:51 +0100	[thread overview]
Message-ID: <CAMxuvayxXG2526Z6p7-fEJM_sVefn8EkjWnY=ZozuiS_UiJS2Q@mail.gmail.com> (raw)
In-Reply-To: <20180228133357.1848600-1-arnd@arndb.de>

Hi

On Wed, Feb 28, 2018 at 2:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> The newly introduced fw_cfg_dma_transfer() function is unused when
> CONFIG_CRASH_CORE is disabled:
>
> drivers/firmware/qemu_fw_cfg.c:89:16: error: 'fw_cfg_dma_transfer' defined but not used [-Werror=unused-function]
>  static ssize_t fw_cfg_dma_transfer(void *address, u32 length, u32 control)
>
> This moves it into the #ifdef section that hides its caller to avoid the
> warning.
>
> Fixes: 47e78bfb5426 ("fw_cfg: write vmcoreinfo details")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

I don't know from which tree you found this, I suppose from
mst/linux-next (which btw, I don't know which version got partially
applied).

This is a regression in v13, because dma read is last patch now, as RFC.
Fixed in upcoming v16.

thanks

> ---
>  drivers/firmware/qemu_fw_cfg.c | 60 +++++++++++++++++++++---------------------
>  1 file changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/firmware/qemu_fw_cfg.c b/drivers/firmware/qemu_fw_cfg.c
> index 3015e77aebca..f002bb40519b 100644
> --- a/drivers/firmware/qemu_fw_cfg.c
> +++ b/drivers/firmware/qemu_fw_cfg.c
> @@ -66,6 +66,36 @@ static void fw_cfg_sel_endianness(u16 key)
>                 iowrite16(key, fw_cfg_reg_ctrl);
>  }
>
> +/* read chunk of given fw_cfg blob (caller responsible for sanity-check) */
> +static ssize_t fw_cfg_read_blob(u16 key,
> +                               void *buf, loff_t pos, size_t count)
> +{
> +       u32 glk = -1U;
> +       acpi_status status;
> +
> +       /* If we have ACPI, ensure mutual exclusion against any potential
> +        * device access by the firmware, e.g. via AML methods:
> +        */
> +       status = acpi_acquire_global_lock(ACPI_WAIT_FOREVER, &glk);
> +       if (ACPI_FAILURE(status) && status != AE_NOT_CONFIGURED) {
> +               /* Should never get here */
> +               WARN(1, "fw_cfg_read_blob: Failed to lock ACPI!\n");
> +               memset(buf, 0, count);
> +               return -EINVAL;
> +       }
> +
> +       mutex_lock(&fw_cfg_dev_lock);
> +       fw_cfg_sel_endianness(key);
> +       while (pos-- > 0)
> +               ioread8(fw_cfg_reg_data);
> +       ioread8_rep(fw_cfg_reg_data, buf, count);
> +       mutex_unlock(&fw_cfg_dev_lock);
> +
> +       acpi_release_global_lock(glk);
> +       return count;
> +}
> +
> +#ifdef CONFIG_CRASH_CORE
>  static inline bool fw_cfg_dma_enabled(void)
>  {
>         return (fw_cfg_rev & FW_CFG_VERSION_DMA) && fw_cfg_reg_dma;
> @@ -124,36 +154,6 @@ static ssize_t fw_cfg_dma_transfer(void *address, u32 length, u32 control)
>         return ret;
>  }
>
> -/* read chunk of given fw_cfg blob (caller responsible for sanity-check) */
> -static ssize_t fw_cfg_read_blob(u16 key,
> -                               void *buf, loff_t pos, size_t count)
> -{
> -       u32 glk = -1U;
> -       acpi_status status;
> -
> -       /* If we have ACPI, ensure mutual exclusion against any potential
> -        * device access by the firmware, e.g. via AML methods:
> -        */
> -       status = acpi_acquire_global_lock(ACPI_WAIT_FOREVER, &glk);
> -       if (ACPI_FAILURE(status) && status != AE_NOT_CONFIGURED) {
> -               /* Should never get here */
> -               WARN(1, "fw_cfg_read_blob: Failed to lock ACPI!\n");
> -               memset(buf, 0, count);
> -               return -EINVAL;
> -       }
> -
> -       mutex_lock(&fw_cfg_dev_lock);
> -       fw_cfg_sel_endianness(key);
> -       while (pos-- > 0)
> -               ioread8(fw_cfg_reg_data);
> -       ioread8_rep(fw_cfg_reg_data, buf, count);
> -       mutex_unlock(&fw_cfg_dev_lock);
> -
> -       acpi_release_global_lock(glk);
> -       return count;
> -}
> -
> -#ifdef CONFIG_CRASH_CORE
>  /* write chunk of given fw_cfg blob (caller responsible for sanity-check) */
>  static ssize_t fw_cfg_write_blob(u16 key,
>                                  void *buf, loff_t pos, size_t count)
> --
> 2.9.0
>

  reply	other threads:[~2018-02-28 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 13:33 [PATCH] fw_cfg: avoid unused function warning Arnd Bergmann
2018-02-28 13:33 ` [Qemu-devel] " Arnd Bergmann
2018-02-28 14:22 ` Marc-André Lureau [this message]
2018-02-28 14:22   ` Marc-André Lureau

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='CAMxuvayxXG2526Z6p7-fEJM_sVefn8EkjWnY=ZozuiS_UiJS2Q@mail.gmail.com' \
    --to=marcandre.lureau@redhat.com \
    --cc=arnd@arndb.de \
    --cc=gomonovych@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=somlo@cmu.edu \
    /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.