From: tip-bot for Jan Kiszka <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, jailhouse-dev@googlegroups.com,
linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
jan.kiszka@siemens.com
Subject: [tip:x86/platform] x86/jailhouse: Respect pci=lastbus command line settings
Date: Fri, 19 Jan 2018 23:19:37 -0800 [thread overview]
Message-ID: <tip-3b42349d56c96e144401d2317d8eeb9937511423@git.kernel.org> (raw)
In-Reply-To: <51f5fe62-ca8f-9286-5cdb-39df3fad78b4@siemens.com>
Commit-ID: 3b42349d56c96e144401d2317d8eeb9937511423
Gitweb: https://git.kernel.org/tip/3b42349d56c96e144401d2317d8eeb9937511423
Author: Jan Kiszka <jan.kiszka@siemens.com>
AuthorDate: Fri, 19 Jan 2018 11:06:30 +0100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Sat, 20 Jan 2018 08:15:44 +0100
x86/jailhouse: Respect pci=lastbus command line settings
Limiting the scan width to the known last bus via the command line can
accelerate the boot noteworthy.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Jailhouse <jailhouse-dev@googlegroups.com>
Link: https://lkml.kernel.org/r/51f5fe62-ca8f-9286-5cdb-39df3fad78b4@siemens.com
---
arch/x86/kernel/jailhouse.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c
index 2b7ebbe..b68fd89 100644
--- a/arch/x86/kernel/jailhouse.c
+++ b/arch/x86/kernel/jailhouse.c
@@ -119,8 +119,10 @@ static int __init jailhouse_pci_arch_init(void)
/*
* There are no bridges on the virtual PCI root bus under Jailhouse,
* thus no other way to discover all devices than a full scan.
+ * Respect any overrides via the command line, though.
*/
- pcibios_last_bus = 0xff;
+ if (pcibios_last_bus < 0)
+ pcibios_last_bus = 0xff;
return 0;
}
prev parent reply other threads:[~2018-01-20 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 10:06 [PATCH] " Jan Kiszka
2018-01-20 7:19 ` tip-bot for Jan Kiszka [this message]
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=tip-3b42349d56c96e144401d2317d8eeb9937511423@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome