linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org,
	michael@ellerman.id.au, anton@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [Early RFC 0/6] arch/powerpc: Add 64TB support to ppc64
Date: Fri,  1 Jun 2012 01:20:35 +0530	[thread overview]
Message-ID: <1338493841-9926-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)

Hi,

This patchset include preparatory patches for supporting 64TB with ppc64. I haven't
completed the actual patch that bump the USER_ESID bits. I wanted the share the
changes early so that I can get feedback on the approach. The changes itself
contains few FIXME!! which I will be addressing in the later updates.

Thanks,
-aneesh

             reply	other threads:[~2012-05-31 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 19:50 Aneesh Kumar K.V [this message]
2012-05-31 19:50 ` [Early RFC 1/6] arch/powerpc: Use hpt_va to compute virtual address Aneesh Kumar K.V
2012-05-31 19:50 ` [Early RFC 2/6] arch/powerpc: Convert virtual address to a struct Aneesh Kumar K.V
2012-05-31 19:50 ` [Early RFC 3/6] arch/powerpc: Simplify hpte_decode Aneesh Kumar K.V
2012-05-31 19:50 ` [Early RFC 4/6] arch/powerpc: Use vsid and segment offset to represent virtual address Aneesh Kumar K.V
2012-05-31 19:50 ` [Early RFC 5/6] arch/powerpc: Make KERN_VIRT_SIZE not dependend on PGTABLE_RANGE Aneesh Kumar K.V
2012-05-31 19:50 ` [Early RFC 6/6] arch/powerpc: Increase the slice range to 64TB Aneesh Kumar K.V
2012-05-31 19:58 ` [Early RFC 0/6] arch/powerpc: Add 64TB support to ppc64 Aneesh Kumar K.V

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=1338493841-9926-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).