All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] ACPI/APEI: revert "accept validly sized ERST on Intel systems only for now"
Date: Tue, 26 Mar 2013 14:24:45 +0000	[thread overview]
Message-ID: <5151AFAD.9030304@citrix.com> (raw)
In-Reply-To: <515177CD02000078000C875D@nat28.tlf.novell.com>

On 26/03/2013 09:26, Jan Beulich wrote:
> With the recent two fixes to ERST handling, this should no longer be
> necessary.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

There are still no failures from our regression testing, so a tentative

Tested-by: Andrew Cooper <andrew.cooper3@citrix.com>

>
> --- a/xen/drivers/acpi/apei/erst.c
> +++ b/xen/drivers/acpi/apei/erst.c
> @@ -738,19 +738,6 @@ static int __init erst_check_table(struc
>  
>  	switch (erst_tab->header_length) {
>  	case sizeof(*erst_tab) - sizeof(erst_tab->header):
> -#ifdef CONFIG_X86
> -		/* XXX
> -		 * While the rest of the ERST code appears to work on Intel
> -		 * systems with properly sized tables, various AMD systems
> -		 * appear to get hung (at boot time) by allowing this. Until
> -		 * someone with access to suitable hardware can debug this,
> -		 * disable the rest of the code by considering this case
> -		 * invalid.
> -		 */
> -		if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> -			return -EINVAL;
> -		/* fall through */
> -#endif
>  	/*
>  	 * While invalid per specification, there are (early?) systems
>  	 * indicating the full header size here, so accept that value too.
>
>
>

  reply	other threads:[~2013-03-26 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  9:26 [PATCH] ACPI/APEI: revert "accept validly sized ERST on Intel systems only for now" Jan Beulich
2013-03-26 14:24 ` Andrew Cooper [this message]
2013-03-26 14:31   ` Jan Beulich
2013-03-26 16:37 ` Ian Jackson
2013-03-26 16:46   ` Jan Beulich
2013-03-27  9:36   ` Jan Beulich
2013-03-27 13:56     ` Ian Jackson

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=5151AFAD.9030304@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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.