qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci_aer_init: cleanup
Date: Wed, 2 Nov 2016 16:58:53 +0800	[thread overview]
Message-ID: <5819AACD.3060601@cn.fujitsu.com> (raw)
In-Reply-To: <1476325947-28268-1-git-send-email-caoj.fnst@cn.fujitsu.com>

ping

On 10/13/2016 10:32 AM, Cao jin wrote:
> log_max have no chance to be PCIE_AER_LOG_MAX_UNSET, unless user specify it.
>
> Bonus:
> 1. remove unnecessary local variable.
> 2. fix a typo.
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
>   hw/pci/pcie_aer.c         | 10 +---------
>   include/hw/pci/pcie_aer.h |  2 +-
>   2 files changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/hw/pci/pcie_aer.c b/hw/pci/pcie_aer.c
> index ac47f34..6cf088b 100644
> --- a/hw/pci/pcie_aer.c
> +++ b/hw/pci/pcie_aer.c
> @@ -99,18 +99,10 @@ static void aer_log_clear_all_err(PCIEAERLog *aer_log)
>   int pcie_aer_init(PCIDevice *dev, uint8_t cap_ver, uint16_t offset,
>                     uint16_t size)
>   {
> -    PCIExpressDevice *exp;
> -
>       pcie_add_capability(dev, PCI_EXT_CAP_ID_ERR, cap_ver,
>                           offset, size);
> -    exp = &dev->exp;
> -    exp->aer_cap = offset;
> +    dev->exp.aer_cap = offset;
>
> -    /* log_max is property */
> -    if (dev->exp.aer_log.log_max == PCIE_AER_LOG_MAX_UNSET) {
> -        dev->exp.aer_log.log_max = PCIE_AER_LOG_MAX_DEFAULT;
> -    }
> -    /* clip down the value to avoid unreasobale memory usage */
>       if (dev->exp.aer_log.log_max > PCIE_AER_LOG_MAX_LIMIT) {
>           return -EINVAL;
>       }
> diff --git a/include/hw/pci/pcie_aer.h b/include/hw/pci/pcie_aer.h
> index c373591..31755ef 100644
> --- a/include/hw/pci/pcie_aer.h
> +++ b/include/hw/pci/pcie_aer.h
> @@ -40,7 +40,7 @@ struct PCIEAERLog {
>        * The specified value will be clipped down to PCIE_AER_LOG_MAX_LIMIT
>        * to avoid unreasonable memory usage.
>        * I bet that 128 log size would be big enough, otherwise too many errors
> -     * for system to function normaly. But could consecutive errors occur?
> +     * for system to function normally. But could consecutive errors occur?
>        */
>   #define PCIE_AER_LOG_MAX_DEFAULT        8
>   #define PCIE_AER_LOG_MAX_LIMIT          128
>

-- 
Yours Sincerely,

Cao jin

  reply	other threads:[~2016-11-02  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  2:32 [Qemu-devel] [PATCH] pci_aer_init: cleanup Cao jin
2016-11-02  8:58 ` Cao jin [this message]
2016-11-02 10:12 ` Marcel Apfelbaum

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=5819AACD.3060601@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).