public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Maly <bmaly@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix DMI for EFI
Date: Sat, 28 Feb 2009 22:58:21 -0500	[thread overview]
Message-ID: <49AA07DD.1030303@redhat.com> (raw)
In-Reply-To: <86802c440902281925m6eb68456vc3886252619b6743@mail.gmail.com>

Thanks. At this point maybe its easier just to move efi_init instead. 
Ill re-work, test and post a followup...

Brian


Yinghai Lu wrote:
> please use git log -p arch/x86/kernel/setup.c to check the history...
>
> YH
>
>
> commit 2216d199b1430d1c0affb1498a9ebdbd9c0de439
> Author: Yinghai Lu <yhlu.kernel@gmail.com>
> Date:   Mon Sep 22 02:52:26 2008 -0700
>
>     x86: fix CONFIG_X86_RESERVE_LOW_64K=y
>
>     The bad_bios_dmi_table() quirk never triggered because we do DMI setup
>     too late. Move it a bit earlier.
>
>     Also change the CONFIG_X86_RESERVE_LOW_64K quirk to operate on the e820
>     table directly instead of messing with early reservations - this handles
>     overlaps (which do occur in this low range of RAM) more gracefully.
>
>     Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 161f1b3..d29951c 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -735,7 +735,8 @@ static int __init dmi_low_memory_corruption(const
> struct dmi_system_id *d)
>                 "%s detected: BIOS may corrupt low RAM, working it around.\n",
>                 d->ident);
>
> -       reserve_early_overlap_ok(0x0, 0x10000, "BIOS quirk");
> +       e820_update_range(0, 0x10000, E820_RAM, E820_RESERVED);
> +       sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map);
>
>         return 0;
>  }
> @@ -784,8 +785,6 @@ void __init setup_arch(char **cmdline_p)
>         printk(KERN_INFO "Command line: %s\n", boot_command_line);
>  #endif
>
> -       dmi_check_system(bad_bios_dmi_table);
> -
>         early_cpu_init();
>         early_ioremap_init();
>
> @@ -880,6 +879,10 @@ void __init setup_arch(char **cmdline_p)
>
>         finish_e820_parsing();
>
> +       dmi_scan_machine();
> +
> +       dmi_check_system(bad_bios_dmi_table);
> +
>  #ifdef CONFIG_X86_32
>         probe_roms();
>  #endif
> @@ -967,8 +970,6 @@ void __init setup_arch(char **cmdline_p)
>         vsmp_init();
>  #endif
>
> -       dmi_scan_machine();
> -
>         io_delay_init();
>   


  reply	other threads:[~2009-03-01  3:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  2:40 [PATCH] fix DMI for EFI Brian Maly
2009-03-01  2:56 ` Yinghai Lu
2009-03-01  3:11   ` Brian Maly
2009-03-01  3:25     ` Yinghai Lu
2009-03-01  3:58       ` Brian Maly [this message]
2009-03-04  2:55   ` Brian Maly
2009-03-04 11:00     ` Ingo Molnar
2009-03-04 15:03       ` Brian Maly
2009-03-04 17:54         ` Ingo Molnar
2009-03-04 18:00           ` Brian Maly
2009-03-04 18:02             ` Ingo Molnar
2009-03-05  1:33           ` Huang Ying
2009-03-05 10:05             ` Ingo Molnar
2009-03-04 17:57     ` [tip:x86/urgent] x86: fix DMI on EFI Brian Maly
  -- strict thread matches above, loose matches on Subject: below --
2009-03-01  1:33 [PATCH] fix DMI for EFI Brian Maly
2009-03-01  2:01 ` Kyle McMartin

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=49AA07DD.1030303@redhat.com \
    --to=bmaly@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@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