From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC 2/3] LVHPT - Setup LVHPT
Date: Wed, 03 May 2006 11:15:04 +0000 [thread overview]
Message-ID: <445890B8.9050506@hob.de> (raw)
In-Reply-To: <20060502052557.8990.87273.sendpatchset@wagner.orchestra.cse.unsw.EDU.AU>
Ian Wienand schrieb:
>On Wed, May 03, 2006 at 10:07:35AM +0200, Christian Hildner wrote:
>
>
>>Yes. So why not picking up Ken's idea of two parallel IVTs.
>>
>>
>
>I have a version of this, which I've tried to post here but I think
>the size limit here is very low. It made it through to linux-mm
>
>http://marc.theaimsgroup.com/?l=linux-mm&m\x114664224732618&w=2
>
>or the patches are at
>
>http://www.gelato.unsw.edu.au/~ianw/lvhpt/patches/v2
>
>It generates ivt.S using a little script. Any feedback on this
>approach welcome.
>
Ian,
I suggested a solution without having any script at all instead working
with something like ivt.h containing macros for all common code and
ivt_svhpt.S and ivt_lvhpt.S in parallel for specific code. It just might
be more readable than your approach and both ways would be treated equal
by the make process. Technically they are the same.
Christian
next prev parent reply other threads:[~2006-05-03 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 5:25 [RFC 0/3] IA64 Long Format VHPT support Ian Wienand
2006-05-02 5:25 ` [RFC 1/3] LVHPT - Fault handler modifications Ian Wienand
2006-05-02 8:04 ` Keith Owens
2006-05-02 17:40 ` Chen, Kenneth W
2006-05-03 7:42 ` Ian Wienand
2006-05-02 5:25 ` [RFC 2/3] LVHPT - Setup LVHPT Ian Wienand
2006-05-02 15:03 ` Luck, Tony
2006-05-02 21:29 ` Ian Wienand
2006-05-02 17:30 ` Chen, Kenneth W
2006-05-03 7:49 ` Ian Wienand
2006-05-03 8:07 ` Christian Hildner
2006-05-02 21:33 ` Luck, Tony
2006-05-03 10:53 ` Ian Wienand
2006-05-03 11:15 ` Christian Hildner [this message]
2006-05-04 16:58 ` Luck, Tony
2006-05-02 5:26 ` [RFC 3/3] LVHPT - LVHPT MM support functions Ian Wienand
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=445890B8.9050506@hob.de \
--to=christian.hildner@hob.de \
--cc=linux-ia64@vger.kernel.org \
/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