mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: rajesh.shah@intel.com
Cc: ak@suse.de, len.brown@intel.com, akpm@osdl.org,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	acpi-devel@lists.sourceforge.net
Subject: Re: [patch 2/2] x86_64: Collect host bridge resources
Date: Mon, 23 May 2005 18:15:07 +0200	[thread overview]
Message-ID: <20050523161507.GN16164@wotan.suse.de> (raw)
In-Reply-To: <20050521004506.842235000@csdlinux-1>

On Fri, May 20, 2005 at 05:42:41PM -0700, rajesh.shah@intel.com wrote:
> This patch reads and stores host bridge resources reported by
> ACPI BIOS for x86_64 systems. This is needed since ACPI hotplug
> code now uses the PCI core for resource management. This patch
> simply adds the boot parameter (acpi=root_resources) to enable
> the functionality that is implemented in arch/i386.
> 

This means all hot plug users have to pass this strange parameter?
That does not sound very user friendly. Especially since you usually
only need pci hotplug in emergencies, and then you likely didnt pass it.

Cant you find a way to do this without parameters? Any reason
to not make it default?

-Andi


  reply	other threads:[~2005-05-23 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21  0:42 [patch 0/2] Collecting " rajesh.shah
2005-05-21  0:42 ` [patch 1/2] i386: collect " rajesh.shah
2005-05-21  0:42 ` [patch 2/2] x86_64: Collect " rajesh.shah
2005-05-23 16:15   ` Andi Kleen [this message]
2005-05-24  0:57     ` Rajesh Shah
2005-05-24 12:05       ` Andi Kleen
2005-05-24 14:58         ` Ivan Kokshaysky
2005-05-24 15:45           ` Rajesh Shah
2005-05-24 16:58             ` Ivan Kokshaysky
2005-05-24 17:37               ` Rajesh Shah
2005-05-26  9:34                 ` Ivan Kokshaysky

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=20050523161507.GN16164@wotan.suse.de \
    --to=ak@suse.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=rajesh.shah@intel.com \
    /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

all inboxes | Powered by JetHome®