From: Bob Picco <bpicco@meloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: swapper_tsb and swapper_4m_tsb phys correction
Date: Wed, 17 Sep 2014 12:42:53 +0000 [thread overview]
Message-ID: <20140917124253.GM17331@zareason> (raw)
In-Reply-To: <1410886239-15774-1-git-send-email-bpicco@meloft.net>
David Miller wrote: [Tue Sep 16 2014, 09:48:03PM EDT]
> From: Bob Picco <bpicco@meloft.net>
> Date: Tue, 16 Sep 2014 12:50:39 -0400
>
> > From: bob picco <bpicco@meloft.net>
> >
> > For physical address larger than 47 bits the computed physical address
> > was insufficient within KERN_TSB_LOOKUP_TL1. This resulted in a vmlinux
> > loaded above 47 bits of physical address unable to boot in spectacular
> > ways.
> >
> > For now we've expanded the physical address range to 52 bits at the cost of
> > two instructions. Older sparc64 incur two nop-s.
> >
> > The two new instructions from this patch and the former KTSB_PHYS_SHIFT can
> > potentially be eliminated using memblock aligning large and constraining
> > the physical limit. Essentially use the "sethi" for a physical manipulated
> > address and replacing the "or" at patch time with a "sllx". This would leave
> > the tsb within head_64.S unused and possibly not a good solution for Cheetah+.
> > We'll comtemplate this more in another round.
> >
> > Cc: sparclinux@vger.kernel.org
> > Signed-off-by: Bob Picco <bob.picco@oracle.com>
>
> Bob, thanks for doing this work to support up to 49-bits of physical
> addressing.
You are very welcome.
>
> There are a lot of tradeoffs and thorny issues involved here, so I'm
> going to take some time reviewing this set of patches.
Indeed many tricky issues. I took a first stab at it.
>
> I'll try to get back to you on these changes in a reasonable amount of
> time, thanks for your patience.
No hurry and thanx.
next prev parent reply other threads:[~2014-09-17 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 16:50 [PATCH] sparc64: swapper_tsb and swapper_4m_tsb phys correction Bob Picco
2014-09-17 1:48 ` David Miller
2014-09-17 12:42 ` Bob Picco [this message]
2014-09-17 17:16 ` David Miller
2014-09-17 19:22 ` Bob Picco
2014-09-17 20:04 ` David Miller
2014-09-17 21:00 ` Bob Picco
2014-09-18 10:09 ` Bob Picco
2014-09-18 17:08 ` David Miller
2014-09-18 19:43 ` David Miller
2014-09-18 21:34 ` Bob Picco
2014-09-18 22:15 ` Bob Picco
2014-09-18 23:16 ` David Miller
2014-09-19 19:28 ` David Miller
2014-09-19 19:57 ` Bob Picco
2014-09-22 4:22 ` David Miller
2014-09-22 18:56 ` Bob Picco
2014-09-22 19:13 ` David Miller
2014-09-24 22:26 ` David Miller
2014-09-24 23:12 ` Bob Picco
2014-09-25 17:43 ` Bob Picco
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=20140917124253.GM17331@zareason \
--to=bpicco@meloft.net \
--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.