linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <lenb@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Ingo Molnar <mingo@elte.hu>,
	Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Yannick Roehlly <yannick.roehlly@free.fr>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	x86@kernel.org
Subject: Re: [PATCH] pci: increase alignment to make more space for hidden code
Date: Mon, 12 Oct 2009 11:59:48 -0700	[thread overview]
Message-ID: <4AD37CA4.90601@kernel.org> (raw)
In-Reply-To: <200910121059.10366.bjorn.helgaas@hp.com>

Bjorn Helgaas wrote:
> On Sunday 11 October 2009 03:17:16 pm Yinghai Lu wrote:
>> for
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=13940
>>
>> some system when acpi are enabled, acpi clears some BAR for some devices without
>> reason, and kernel will need to allocate devices for them.
> 
> "ACPI clears some BARs"?  I'm dubious.  The handoff state is the same
> whether we boot with "acpi=off" or not, so the BIOS can't be clearing
> them.  I really don't think the ACPI code in Linux clears BARs.  The
> Linux PCI code might be clearing BARs, but it sure would be nice to
> know exactly why.  Did you ever figure that out?

please check the mail is reponsed to Ingo.

> 
>> try to increase alignment to get more safe range for unassigned devices.
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>> ---
>>  arch/x86/kernel/e820.c |    4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> Index: linux-2.6/arch/x86/kernel/e820.c
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/kernel/e820.c
>> +++ linux-2.6/arch/x86/kernel/e820.c
>> @@ -1378,8 +1378,8 @@ static unsigned long ram_alignment(resou
>>  	if (mb < 16)
>>  		return 1024*1024;
>>  
>> -	/* To 32MB for anything above that */
>> -	return 32*1024*1024;
>> +	/* To 64MB for anything above that */
>> +	return 64*1024*1024;
> 
> How do we know 64MB is the correct alignment?
> 
> This feels like a hack that accidentally covers up the problem.  I
> don't think we understand what's happening well enough.

yes, we need to figure out why when acpi=on, those BAR are cleared, before pci code try to scan and read BAR.
(node early pic print out untouched, but after APCI subsystem is enabled, those BAR got clearred)

YH

  parent reply	other threads:[~2009-10-12 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 22:33 Regression in ACPI in 2.6.31-rc5 Ricardo Jorge da Fonseca Marques Ferreira
2009-08-13  3:53 ` Len Brown
2009-08-16  3:00   ` Ricardo Jorge da Fonseca Marques Ferreira
2009-10-06  3:17     ` Len Brown
2009-10-06  4:38       ` Yinghai Lu
     [not found]       ` <4ACAC8F1.1050706@kernel.org>
2009-10-11 21:17         ` [PATCH] pci: increase alignment to make more space for hidden code Yinghai Lu
2009-10-12 16:59           ` Bjorn Helgaas
2009-10-12 17:19             ` Ingo Molnar
2009-10-12 18:43               ` Yinghai Lu
2009-10-12 18:59             ` Yinghai Lu [this message]
2009-10-12 19:22               ` Ingo Molnar
2009-10-12 19:44                 ` Yinghai Lu
2009-10-13  6:08                   ` Bjorn Helgaas
2009-10-13  6:49                     ` Ingo Molnar
2009-10-13 15:15                       ` Bjorn Helgaas
2009-10-13 19:05                     ` Ricardo Jorge da Fonseca Marques Ferreira

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=4AD37CA4.90601@kernel.org \
    --to=yinghai@kernel.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jesse.barnes@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=storm@sys49152.net \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=yannick.roehlly@free.fr \
    /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).