All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	gregkh@suse.de
Subject: Re: [RFC] Runtime allocation of PCI resources
Date: Mon, 11 Jun 2007 18:41:21 +0100	[thread overview]
Message-ID: <20070611174121.GA31647@srcf.ucam.org> (raw)
In-Reply-To: <p73d502uzsj.fsf@bingen.suse.de>

On Mon, Jun 11, 2007 at 08:11:24PM +0200, Andi Kleen wrote:
> Matthew Garrett <mjg59@srcf.ucam.org> writes:
> 
> > BIOS authors don't always program all the features of hardware. This is 
> > often the case for Intel IDE controllers, which are usually able to run 
> > in AHCI mode but are rarely configured to do so. Reprogramming them is 
> > easy enough other than the requirement for some MMIO space. If the BIOS 
> > hasn't allocated this, it's necessary for us to do so manually.
> 
> Traditionally we've had bad experiences forcing hardware to do something
> the BIOS didn't consider. e.g. occasionally the BIOS has good reasons
> to not allow it; maybe it knows about some errata or other problem
> the kernel doesn't. 

AHCI is generally disabled because it makes Windows insanely difficult 
to install. I'm not aware of any hardware issues in this case.

> I tried something similar some time ago for the IOMMU aperture.
> It turned out that some systems put something into the e820 holes
> and didn't boot anymore if you put something else in there.
> Your resource allocation will just do that.
> 
> You might be lucky because your resources are typically
> small (IOMMU aperture was 64+MB) or you might not.

Hm. Yes, that would be a problem (sigh BIOS authors).
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2007-06-11 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:51 [RFC] Runtime allocation of PCI resources Matthew Garrett
2007-06-11 18:11 ` Andi Kleen
2007-06-11 17:41   ` Matthew Garrett [this message]
2007-06-11 18:11   ` Yinghai Lu

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=20070611174121.GA31647@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=andi@firstfloor.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.