public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Persvold <sp@scali.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Status on ioremap patch
Date: Wed, 09 Jan 2002 20:01:13 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805782@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805186@msgid-missing>

Steffen Persvold wrote:
> 
> David Mosberger wrote:
> >
> > Steffen,
> >
> > I looked at your patch and have a comment and a suggestion.  First, I
> > do not think it's safe to define ioremap() as a way to install
> > write-cached mappings.  There are plenty of drivers left that use
> > ioremap() instead of ioremap_nocache() and we can't change the
> > semantics of ioremap() underneath them.
> >
> > Second, it seems to me it would be cleaner to extend
> > remap_page_range() to allow remapping into the kernel mapped segment
> > (region 5 in the case of ia64 linux).  This should work as is, except
> > that in the kernel case, you need to use pgd_offset_k().  I think you
> > could hack mm/memory.c to check whether "from" is in the range from
> > VMALLOC_START to VMALLOC_END and, if so, use pgd_offset_k() instead of
> > pgd_offset().  Can you try this and let me know if it works for your
> > needs?
> >
> 
> I've had some time to look at it, and I decided to do what you said. I also changed ioremap on all
> platforms that implements it so that they use remap_page_range()). I've tested the patch on IA64 and
> i386.
> 
> I've attached the patch (I didn't post it on the lkml even though it affects more that the IA64
> platform), it's against a vanilla 2.4.17 tree.
> 
> Please take a look and tell me what you think.
> 

So, what about this patch (posted earlier) David ? Have you seen the comments from Keith ? 

Regards,
-- 
  Steffen Persvold   | Scalable Linux Systems |   Try out the world's best   
 mailto:sp@scali.no  |  http://www.scali.com  | performing MPI implementation:
Tel: (+47) 2262 8950 |   Olaf Helsets vei 6   |      - ScaMPI 1.12.2 -         
Fax: (+47) 2262 8951 |   N0621 Oslo, NORWAY   | >300MBytes/s and <4uS latency


  parent reply	other threads:[~2002-01-09 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 23:14 [Linux-ia64] Re: Status on ioremap patch David Mosberger
2001-09-15 12:36 ` Steffen Persvold
2001-09-28 12:39 ` Jes Sorensen
2002-01-05 15:01 ` Steffen Persvold
2002-01-05 23:30 ` Keith Owens
2002-01-06 11:02 ` Steffen Persvold
2002-01-06 11:55 ` Keith Owens
2002-01-06 14:27 ` Steffen Persvold
2002-01-09 20:01 ` Steffen Persvold [this message]
2002-01-10  3:01 ` David Mosberger
  -- strict thread matches above, loose matches on Subject: below --
2004-03-03 15:12 Hugo Kohmann
2004-03-03 22:58 ` David Mosberger

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=marc-linux-ia64-105590698805782@msgid-missing \
    --to=sp@scali.no \
    --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