From: Christian Hildner <christian.hildner@hob.de>
To: Ian Wienand <ianw@gelato.unsw.edu.au>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC 2/3] LVHPT - Setup LVHPT
Date: Wed, 03 May 2006 08:07:35 +0000 [thread overview]
Message-ID: <445864C7.9050800@hob.de> (raw)
In-Reply-To: 20060503074903.GB4798@cse.unsw.EDU.AU
Ian Wienand schrieb:
>Being relatively inexperienced, all this dynamic patching (SMP, page
>table, this) scares me in that what is executing diverges from what
>appears to be in source code, making difficult things even more
>difficult to debug. Is there consensus that a long term goal should
>be that short and long formats should be dynamically selectable?
>
Yes. So why not picking up Ken's idea of two parallel IVTs. Best
practice and probably the most readable solution might be the usage of
common macros for all the common entires (like EXTERNAL_INTERRUPT_CODE),
so that only the VHPT-specific entries would be coded directly in the
corrensponding ivt.S. Straightforward and without patching, code
generation, ...
Christian
WARNING: multiple messages have this Message-ID (diff)
From: Christian Hildner <christian.hildner@hob.de>
To: Ian Wienand <ianw@gelato.unsw.edu.au>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC 2/3] LVHPT - Setup LVHPT
Date: Wed, 03 May 2006 10:07:35 +0200 [thread overview]
Message-ID: <445864C7.9050800@hob.de> (raw)
In-Reply-To: 20060503074903.GB4798@cse.unsw.EDU.AU
Ian Wienand schrieb:
>Being relatively inexperienced, all this dynamic patching (SMP, page
>table, this) scares me in that what is executing diverges from what
>appears to be in source code, making difficult things even more
>difficult to debug. Is there consensus that a long term goal should
>be that short and long formats should be dynamically selectable?
>
Yes. So why not picking up Ken's idea of two parallel IVTs. Best
practice and probably the most readable solution might be the usage of
common macros for all the common entires (like EXTERNAL_INTERRUPT_CODE),
so that only the VHPT-specific entries would be coded directly in the
corrensponding ivt.S. Straightforward and without patching, code
generation, ...
Christian
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-05-03 8:07 UTC|newest]
Thread overview: 31+ 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 ` Ian Wienand
2006-05-02 5:25 ` [RFC 1/3] LVHPT - Fault handler modifications Ian Wienand
2006-05-02 5:25 ` Ian Wienand
2006-05-02 8:04 ` Keith Owens
2006-05-02 8:04 ` Keith Owens
2006-05-02 17:40 ` Chen, Kenneth W
2006-05-02 17:40 ` Chen, Kenneth W
2006-05-03 1:57 ` Ian Wienand
2006-05-03 7:42 ` Ian Wienand
2006-05-03 7:42 ` Ian Wienand
2006-05-02 5:25 ` [RFC 2/3] LVHPT - Setup LVHPT Ian Wienand
2006-05-02 5:25 ` Ian Wienand
2006-05-02 15:03 ` Luck, Tony
2006-05-02 15:03 ` Luck, Tony
2006-05-02 21:29 ` Ian Wienand
2006-05-02 21:29 ` Ian Wienand
2006-05-02 17:30 ` Chen, Kenneth W
2006-05-02 17:30 ` Chen, Kenneth W
2006-05-03 7:49 ` Ian Wienand
2006-05-03 7:49 ` Ian Wienand
2006-05-03 8:07 ` Christian Hildner [this message]
2006-05-03 8:07 ` Christian Hildner
2006-05-02 21:33 ` Luck, Tony
2006-05-02 21:33 ` Luck, Tony
2006-05-03 10:53 ` Ian Wienand
2006-05-03 11:15 ` Christian Hildner
2006-05-04 16:58 ` Luck, Tony
2006-05-04 16:58 ` Luck, Tony
2006-05-02 5:26 ` [RFC 3/3] LVHPT - LVHPT MM support functions Ian Wienand
2006-05-02 5:26 ` 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=445864C7.9050800@hob.de \
--to=christian.hildner@hob.de \
--cc=ianw@gelato.unsw.edu.au \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.