All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edgar Hucek <hostmaster@ed-soft.at>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Fix boot on efi 32 bit Machines [try #4]
Date: Fri, 14 Jul 2006 21:28:40 +0200	[thread overview]
Message-ID: <44B7F068.3050500@ed-soft.at> (raw)
In-Reply-To: <200607141000_MC3-1-C4FF-9460@compuserve.com>

Rajesh's patch does not solve my problem. Actually i work on a force patch.

cu

Edgar

Chuck Ebbert schrieb:
> In-Reply-To: <Pine.LNX.4.64.0607131507220.5623@g5.osdl.org>
> 
> On Thu, 13 Jul 2006 15:15:21 -0700, Linus Torvalds wrote:
> 
>>> From kernel 2.6.16 to kernel 2.6.17 a new check is made.
>>> File arch/i386/pci/mmconfig.c -> funktion pci_mmcfg_init -> check e820_all_mapped
>>> The courios thing is that this check will always fail on the
>>> Intel Macs booted through efi. Parsing of the ACPI_MCFG table
>>> returns e0000000 for the start. But this location is
>>> not in the memory map which the efi firmware have :
>>> BIOS-EFI: 00000000e00f8000 - 00000000e00f9000 (reserved)
>> It _sounds_ like you may not have converted all the EFI types 
>> (EFI_UNUSABLE_MEMORY?), but regardless, I think it would be fine to have 
>> perhaps a "PCI_FORCE_MMCONF" flag that avoided that sanity check, and then 
>> you could have some code (either the EFI code _or_ some DMI code) that 
>> sets it for the Intel Macs.
>>
>> Note that the check in pci_mmcfg_init() shouldn't be some EFI hack itself, 
>> it would be a real flag for the PCI subsystem, independently of EFI (I can 
>> see it being useful for a kernel command line option, even), and the only 
>> EFI connection would be that perhaps the EFI code ends up setting that 
>> flag (especially if there is some EFI command for doing this).
>>
>> Btw, if you do do this, I think we should make sure that the MMCONFIG base 
>> address is reserved in the PCI MMIO resource structures (which we don't do 
>> now, I think - part of the whole point of verifying that it's marked as 
>> E820_RESERVED is exactly the fact that otherwise we migth have problems 
>> with PCI MMIO resource allocations allocating a regular PCI resource over 
>> the MMCONFIG space..)
> 
> I just reposted Rajesh's patch for this (fixed the one previous complaint
> from the list.)
> 
>  Subj:  [patch, take 3] PCI: use ACPI to verify extended config space on x86
> 
> Edgar, can you get it and test?
> 
> Discussion should probably continue in that thread...
> 


  parent reply	other threads:[~2006-07-14 19:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 13:57 [PATCH 1/1] Fix boot on efi 32 bit Machines [try #4] Chuck Ebbert
2006-07-14 14:45 ` Edgar Hucek
2006-07-14 19:28 ` Edgar Hucek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-16 12:09 Thomas Meyer
2006-06-26 22:22 Thomas Meyer
2006-06-26 21:19 Edgar Hucek
2006-06-26 21:33 ` Linus Torvalds
2006-06-27  6:15   ` Edgar Hucek
2006-06-27  6:20     ` Linus Torvalds
2006-06-28 22:37       ` H. Peter Anvin
2006-07-02 17:39         ` Eric W. Biederman
2006-07-02 17:42           ` H. Peter Anvin
2006-07-02 18:26             ` Eric W. Biederman
2006-07-02 18:46               ` Arjan van de Ven
2006-07-05  9:38               ` Edgar Hucek
2006-07-05 15:52                 ` Eric W. Biederman
2006-07-13 21:46                   ` Edgar Hucek
2006-07-13 22:15                     ` Linus Torvalds
2006-07-14  4:23                       ` Eric W. Biederman
2006-07-14  6:22                         ` H. Peter Anvin
2006-07-14  6:20                       ` Edgar Hucek
2006-07-14 16:09                         ` Linus Torvalds

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=44B7F068.3050500@ed-soft.at \
    --to=hostmaster@ed-soft.at \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.