From: Peter Maydell <peter.maydell@linaro.org>
To: shiju.jose@huawei.com
Cc: qemu-devel@nongnu.org, linux-edac@vger.kernel.org,
jonathan.cameron@huawei.com, mchehab+huawei@kernel.org,
tanxiaofei@huawei.com, prime.zeng@hisilicon.com,
linuxarm@huawei.com
Subject: Re: [RFC PATCH 1/1] hw/arm: FW first ARM processor error injection.
Date: Mon, 24 Jun 2024 14:47:38 +0100 [thread overview]
Message-ID: <CAFEAcA9CQ_D168MmD+VbQsegUVsJuiXBP64oH0SgL=bD8EDJOA@mail.gmail.com> (raw)
In-Reply-To: <20240621165115.336-1-shiju.jose@huawei.com>
On Fri, 21 Jun 2024 at 17:52, shiju.jose--- via <qemu-devel@nongnu.org> wrote:
>
> From: Shiju Jose <shiju.jose@huawei.com>
>
> diff --git a/hw/arm/arm_error_inject.c b/hw/arm/arm_error_inject.c
> new file mode 100644
> index 0000000000..953a9d6705
> --- /dev/null
> +++ b/hw/arm/arm_error_inject.c
> @@ -0,0 +1,49 @@
> +/*
> + * CXL Type 3 (memory expander) device
This doesn't seem to match what the file actually does.
> + *
> + * Copyright(C) 2020 Intel Corporation.
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2. See the
> + * COPYING file in the top-level directory.
> + *
> + * SPDX-License-Identifier: GPL-v2-only
Why are these new files GPL-v2-only? Our general preference
(see the LICENSE) file is for GPL-v2-or-any-later-version.
I also notice that this file is marked as copyright Intel, but
you're submitting from a Huawei email address. What's the history
of this code?
> + */
> +
> +#include "qemu/osdep.h"
> +#include "qemu/units.h"
> +#include "qemu/error-report.h"
> +#include "qapi-commands-arm-error-inject.h"
> +#include "hw/qdev-properties.h"
> +#include "qapi/error.h"
> +#include "qemu/log.h"
> +#include "qemu/module.h"
> +#include "qemu/pmem.h"
> +#include "qemu/range.h"
> +#include "qemu/rcu.h"
> +#include "qemu/guest-random.h"
> +#include "sysemu/hostmem.h"
> +#include "sysemu/numa.h"
> +#include "hw/boards.h"
> +#include "hw/acpi/ghes.h"
Looking at the code here I'm pretty sure you don't need
anywhere near all of these include lines.
> +
> +#define DWORD_BYTE 4
This seems to be unused.
thanks
-- PMM
next prev parent reply other threads:[~2024-06-24 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 16:51 [RFC PATCH 1/1] hw/arm: FW first ARM processor error injection shiju.jose--- via
2024-06-21 18:33 ` Jonathan Cameron via
2024-06-24 9:45 ` Mauro Carvalho Chehab
2024-06-24 13:47 ` Peter Maydell [this message]
2024-06-24 14:52 ` Shiju Jose via
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='CAFEAcA9CQ_D168MmD+VbQsegUVsJuiXBP64oH0SgL=bD8EDJOA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
/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).