From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Ian Wienand' <ianw@gelato.unsw.edu.au>, linux-ia64@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: RE: [RFC 1/3] LVHPT - Fault handler modifications
Date: Tue, 2 May 2006 10:40:37 -0700 [thread overview]
Message-ID: <4t153d$t4guc@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20060502052551.8990.16410.sendpatchset@wagner.orchestra.cse.unsw.EDU.AU>
Ian Wienand wrote on Monday, May 01, 2006 10:26 PM
> Firstly, we have stripped out common code in ivt.S into assembler
> macros in ivt-macro.S. The comments before the macros should explain
> what each is doing.
I think at current state, it's way too early to extract out the common
code into macros, because for long format vhpt, the low level handler is
not even optimal. And in the final form, it may not be the same as the
short format vhpt (OK, the linux page table walk will be the same, but
other part maybe not).
I would like to experiment with a few algorithms for lvhpt and best thing
to do in my opinion is to have parallel ivt.S (or ivt table to be precise).
- Ken
--
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-02 17:40 UTC|newest]
Thread overview: 8+ 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 [this message]
2006-05-03 1:57 ` 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: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='4t153d$t4guc@azsmga001.ch.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=ianw@gelato.unsw.edu.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.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