From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: peter.senna@gmail.com, ryabinin.a.a@gmail.com, JBeulich@suse.com,
hpa@zytor.com, qiuxishi@huawei.com, boris.ostrovsky@oracle.com,
xen-devel@lists.xensource.com, joro@8bytes.org, x86@kernel.org,
mingo@redhat.com, aryabinin@virtuozzo.com,
mchehab@osg.samsung.com, andreyknvl@google.com, mcgrof@suse.com,
rusty@rustcorp.com.au, bp@alien8.de, tglx@linutronix.de,
mcb30@ipxe.org, valentinrothberg@gmail.com, jgross@suse.com,
linux-kernel@vger.kernel.org, luto@amacapital.net,
long.wanglong@huawei.com
Subject: Re: [RFC v1 6/8] x86/init: use linker table for i386 early setup
Date: Wed, 20 Jan 2016 16:14:24 -0500 [thread overview]
Message-ID: <20160120211424.GG4769@char.us.oracle.com> (raw)
In-Reply-To: <1450217797-19295-7-git-send-email-mcgrof@do-not-panic.com>
On Tue, Dec 15, 2015 at 02:16:35PM -0800, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> This also annotates this is only used for PC and
> lguest hardware subarchitectures.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
On Xen the code path (before this patch) was:
xen_start_kernel->i386_start_kernel->i386_default_early_setup
and now you remove the i386_default_early_setup call?
The mpparse.setup_ioapic_ids is irrelevant as under Xen code it
does:
709 /* Avoid searching for BIOS MP tables */
1710 x86_init.mpparse.find_smp_config = x86_init_noop;
1711 x86_init.mpparse.get_smp_config = x86_init_uint_noop;
Great, MP tables is completly ignored.
The next one : i386_reserve_resources
Looks to be reserving VGA RAM .. which is a bit pointless when you
have no legacy devices.
The reserve_standard_io_resources means the /proc/ioport is smaller now.
Actually looking under an PV guest it is:
# cat /proc/ioports
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc_cmos
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
# cat /proc/iomem
00000000-00000fff : reserved
00001000-0009ffff : System RAM
000a0000-000fffff : reserved
Which means /proc/ioports won't have anything in it (with your change)
And /proc/iomem will have the 000a0000-000fffff region available (maybe?)
Ah no. We mark it as reserved in the early part of boot:
[ 0.000000] Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
I am curious - what does your kernel run as PV look like?
Thanks.
> ---
> arch/x86/kernel/head32.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kernel/head32.c b/arch/x86/kernel/head32.c
> index 768fa3888066..1db8eec5b0e2 100644
> --- a/arch/x86/kernel/head32.c
> +++ b/arch/x86/kernel/head32.c
> @@ -21,12 +21,15 @@
> #include <asm/bootparam_utils.h>
> #include <asm/x86_init.h>
>
> -static void __init i386_default_early_setup(void)
> +static void __init i386_set_setup_funcs(void)
> {
> /* Initialize 32bit specific setup functions */
> x86_init.resources.reserve_resources = i386_reserve_resources;
> x86_init.mpparse.setup_ioapic_ids = setup_ioapic_ids_from_mpc;
> }
> +x86_init_early(BIT(X86_SUBARCH_PC) |
> + BIT(X86_SUBARCH_LGUEST),
> + NULL, NULL, i386_set_setup_funcs);
>
> asmlinkage __visible void __init i386_start_kernel(void)
> {
> @@ -41,9 +44,6 @@ asmlinkage __visible void __init i386_start_kernel(void)
> case X86_SUBARCH_CE4100:
> x86_ce4100_early_setup();
> break;
> - default:
> - i386_default_early_setup();
> - break;
> }
>
> x86_init_fn_init_tables();
> --
> 2.6.2
>
next prev parent reply other threads:[~2016-01-20 21:14 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 22:16 [RFC v1 0/8] x86/init: Linux linker tables Luis R. Rodriguez
2015-12-15 22:16 ` [RFC v1 1/8] paravirt: rename paravirt_enabled to paravirt_legacy Luis R. Rodriguez
2016-01-20 19:32 ` Konrad Rzeszutek Wilk
2016-02-04 22:50 ` Luis R. Rodriguez
2015-12-15 22:16 ` [RFC v1 2/8] tables.h: add linker table support Luis R. Rodriguez
2016-01-20 20:04 ` Konrad Rzeszutek Wilk
2016-01-20 23:15 ` Michael Brown
2016-01-20 23:24 ` H. Peter Anvin
2015-12-15 22:16 ` [RFC v1 3/8] x86/boot: add BIT() to boot/bitops.h Luis R. Rodriguez
2016-01-20 20:17 ` Konrad Rzeszutek Wilk
2016-01-20 20:33 ` Luis R. Rodriguez
2015-12-15 22:16 ` [RFC v1 4/8] x86/init: add linker table support Luis R. Rodriguez
2016-01-20 20:45 ` Konrad Rzeszutek Wilk
2016-01-20 21:00 ` Konrad Rzeszutek Wilk
2016-01-20 21:33 ` Luis R. Rodriguez
2016-01-20 21:41 ` H. Peter Anvin
2016-01-20 22:12 ` Luis R. Rodriguez
2016-01-20 22:20 ` H. Peter Anvin
2016-01-22 0:25 ` Luis R. Rodriguez
2016-01-22 0:42 ` H. Peter Anvin
2016-02-11 20:45 ` Luis R. Rodriguez
2016-01-21 8:38 ` Roger Pau Monné
2016-01-21 13:45 ` Boris Ostrovsky
2016-01-21 19:25 ` H. Peter Anvin
2016-01-21 19:46 ` Luis R. Rodriguez
2016-01-21 19:50 ` H. Peter Anvin
2016-01-21 19:52 ` H. Peter Anvin
2016-01-22 0:19 ` Luis R. Rodriguez
2016-01-21 20:05 ` Luis R. Rodriguez
2016-01-21 21:36 ` H. Peter Anvin
2015-12-15 22:16 ` [RFC v1 5/8] x86/init: move ebda reservations into linker table Luis R. Rodriguez
2015-12-17 20:48 ` Andy Lutomirski
2015-12-17 20:55 ` H. Peter Anvin
2015-12-17 20:57 ` Andy Lutomirski
2015-12-17 23:40 ` Luis R. Rodriguez
2016-01-20 20:46 ` Konrad Rzeszutek Wilk
2015-12-15 22:16 ` [RFC v1 6/8] x86/init: use linker table for i386 early setup Luis R. Rodriguez
2016-01-20 21:14 ` Konrad Rzeszutek Wilk [this message]
2016-01-20 21:41 ` Luis R. Rodriguez
2016-02-11 19:55 ` Luis R. Rodriguez
2015-12-15 22:16 ` [RFC v1 7/8] x86/init: user linker table for ce4100 " Luis R. Rodriguez
2016-01-20 21:14 ` Konrad Rzeszutek Wilk
2015-12-15 22:16 ` [RFC v1 8/8] x86/init: use linker table for mid " Luis R. Rodriguez
2016-01-20 21:15 ` Konrad Rzeszutek Wilk
2015-12-15 22:59 ` [RFC v1 0/8] x86/init: Linux linker tables H. Peter Anvin
2015-12-17 20:38 ` H. Peter Anvin
2015-12-17 23:46 ` Luis R. Rodriguez
2015-12-17 23:58 ` Luis R. Rodriguez
2015-12-18 4:25 ` H. Peter Anvin
2015-12-18 4:40 ` H. Peter Anvin
2016-01-21 20:19 ` H. Peter Anvin
2016-01-21 20:33 ` Luis R. Rodriguez
2016-01-21 21:37 ` Konrad Rzeszutek Wilk
2016-01-21 22:25 ` [Xen-devel] " Luis R. Rodriguez
2016-01-21 23:56 ` H. Peter Anvin
2016-01-22 0:28 ` Luis R. Rodriguez
2016-01-22 8:15 ` Michael Brown
2016-01-22 13:44 ` Michael Matz
2016-01-22 19:06 ` H. Peter Anvin
2016-01-22 21:52 ` Luis R. Rodriguez
2016-02-03 0:22 ` Luis R. Rodriguez
2016-02-03 0:25 ` H. Peter Anvin
2016-02-03 0:28 ` Luis R. Rodriguez
2016-02-03 0:48 ` Luis R. Rodriguez
2016-02-02 23:48 ` H. Peter Anvin
2016-02-03 0:15 ` Luis R. Rodriguez
2015-12-18 18:50 ` Luis R. Rodriguez
2015-12-18 18:58 ` H. Peter Anvin
2016-01-20 21:16 ` Konrad Rzeszutek Wilk
2016-01-20 21:49 ` Luis R. Rodriguez
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=20160120211424.GG4769@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=long.wanglong@huawei.com \
--cc=luto@amacapital.net \
--cc=mcb30@ipxe.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mchehab@osg.samsung.com \
--cc=mingo@redhat.com \
--cc=peter.senna@gmail.com \
--cc=qiuxishi@huawei.com \
--cc=rusty@rustcorp.com.au \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=valentinrothberg@gmail.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).