From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Michael Matz <matz@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andy Lutomirski <luto@amacapital.net>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Michael Brown <mcb30@ipxe.org>, Juergen Gross <jgross@suse.com>,
Jan Beulich <JBeulich@suse.com>, Joerg Roedel <joro@8bytes.org>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
long.wanglong@huawei.com, qiuxishi@huawei.com,
aryabinin@virtuozzo.com,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Peter Senna Tschudin <peter.senna@gmail.com>,
X86 ML <x86@kernel.org>, Michal Marek <mmarek@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v1 0/8] x86/init: Linux linker tables
Date: Tue, 02 Feb 2016 16:25:03 -0800 [thread overview]
Message-ID: <56B148DF.4050506@zytor.com> (raw)
In-Reply-To: <CAB=NE6V3u2KQmsV1SrUxpLUb=z-DMsRO9UQPfqAO+YpQZeMZZw@mail.gmail.com>
On 02/02/2016 04:22 PM, Luis R. Rodriguez wrote:
>>
>> Should it be possible to resuse free_init_pages() and/or
>> free_reserved_area() only for routines (members in the array in this
>> case of a struct of fns) that don't meet our subarch once we're done
>> iterating over the routies and know we can discard things we know we
>> can drop? Through a cursory glance, *I think* its possible as-is, we
>> would just need easy access to the respective start and end addresses
>> and I guess there lies the challenge. Question is, is would that be
>> clean enough for us? Or are there other things you can think of that
>> perhaps might make this prospect cleaner later to add?
>>
>> I figure better ask now for architectural purposes than later after merged.
>
> I don't think its needed we iron out in a solution *now* to be able to
> free code we know we won't need at run time but having a solid
> understanding adding this feature later without much impact to users
> might be worthy. As such I was pursuing a very basic proof of concept
> to ensure this is possible first given I didn't hear back if folks
> were sure this might be possible. I don't think a proof of concept
> should take long so just want to get fleshed out.
>
This applies to the specific subarch use rather than generic linker
tables, right?
-hpa
next prev parent reply other threads:[~2016-02-03 0:25 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
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 [this message]
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=56B148DF.4050506@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=aryabinin@virtuozzo.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=long.wanglong@huawei.com \
--cc=luto@amacapital.net \
--cc=matz@suse.de \
--cc=mcb30@ipxe.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mingo@redhat.com \
--cc=mmarek@suse.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).