All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Holst <mail@s-holst.de>
To: sparclinux@vger.kernel.org
Subject: Re: nonzero phys_base
Date: Thu, 18 Mar 2004 00:09:36 +0000	[thread overview]
Message-ID: <20040318000936.GC5754@spike> (raw)
In-Reply-To: <20040316114121.GA5170@spike>

On 03/16, Keith M Wesolowski wrote:
> On Tue, Mar 16, 2004 at 12:41:21PM +0100, Stefan Holst wrote:
> 
> > how do you think about this fix? any chances to get this into the
> > kernel? if yes, how? this is the first time i send kernel patches,
> > so hints and comments are very welcome :).
> 
> Yes, I'll consider this for inclusion.  You get patches into the
> kernel by sending them to this list, so you're off to a good start
> there.
> 
> Please use pfn_base the way sparc64 does.  Shifting every time this is
> used is unnecessarily expensive.  It would be nice if we could also

done, see patch in other post.

> dispense with making __va and __pa nonconstant, but unlike sparc64 we
> don't have the luxury of huge space to map into.

if phys_base is known at compile time, it could be a macro, at least 
in __pa and __va to make them constant. would that be an option?

> 
> Otherwise this looks pretty good at first glance.
> 
> Thanks for doing this, Stefan.

thanks :)
but that was not entirely my work. i just tied up to konrad's at
the moment.

-- 
RY  Stefan
+-----------------+----------------+
| mail@s-holst.de | www.s-holst.de |
+-----------------+----------------+

  parent reply	other threads:[~2004-03-18  0:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 11:41 nonzero phys_base Stefan Holst
2004-03-16 16:55 ` Keith M Wesolowski
2004-03-16 17:10 ` Pete Zaitcev
2004-03-17 23:58 ` Stefan Holst
2004-03-18  0:09 ` Stefan Holst [this message]
2004-03-18  2:45 ` Keith M Wesolowski
2004-03-18  3:36 ` Pete Zaitcev
2004-03-21 22:51 ` Keith M Wesolowski

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=20040318000936.GC5754@spike \
    --to=mail@s-holst.de \
    --cc=sparclinux@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 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.