public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "Brown, Len" <len.brown@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH, resend] ACPI/HEST: avoid stack traces when	 encountering duplicate source IDs
Date: Wed, 08 Dec 2010 08:36:41 +0800	[thread overview]
Message-ID: <1291768601.12648.663.camel@yhuang-dev> (raw)
In-Reply-To: <4CFE59A50200007800026700@vpn.id2.novell.com>

On Tue, 2010-12-07 at 22:58 +0800, Jan Beulich wrote:
> Rather than trying to create duplicate platform devices, check for
> duplication up front.
> 
> Generally the kernel doesn't require uniqueness of the source IDs
> other than for obtaining unique platform device names (and making log
> message non-ambiguous) - therefore, it would be possible to simply
> replace eventual duplicate IDs with kernel assigned ones.

Do you have a machine with duplicated source ID in HEST?

> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: Huang Ying <ying.huang@intel.com>
> 
> ---
>  drivers/acpi/apei/hest.c |   11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> --- linux-2.6.37-rc5/drivers/acpi/apei/hest.c
> +++ 2.6.37-rc5-acpi-hest-unique/drivers/acpi/apei/hest.c
> @@ -139,6 +139,7 @@ static int hest_parse_ghes(struct acpi_h
>  {
>  	struct platform_device *ghes_dev;
>  	struct ghes_arr *ghes_arr = data;
> +	unsigned int i;
>  	int rc;
>  
>  	if (hest_hdr->type != ACPI_HEST_TYPE_GENERIC_ERROR)
> @@ -146,6 +147,16 @@ static int hest_parse_ghes(struct acpi_h
>  
>  	if (!((struct acpi_hest_generic *)hest_hdr)->enabled)
>  		return 0;
> +	for (i = 0; i < ghes_arr->count; ++i) {
> +		const struct acpi_hest_header *h;
> +
> +		h = *(void **)dev_get_platdata(&ghes_arr->ghes_devs[i]->dev);
> +		if (hest_hdr->source_id == h->source_id) {
> +			pr_warn("Duplicate generic error source ID %#x\n",

I think we can add FW_WARN prefix here.

Best Regards,
Huang Ying



  reply	other threads:[~2010-12-08  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 14:58 [PATCH, resend] ACPI/HEST: avoid stack traces when encountering duplicate source IDs Jan Beulich
2010-12-08  0:36 ` Huang Ying [this message]
2010-12-08  7:37   ` Jan Beulich

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=1291768601.12648.663.camel@yhuang-dev \
    --to=ying.huang@intel.com \
    --cc=JBeulich@novell.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.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