From: Michael Ellerman <michael@ellerman.id.au>
To: Hannes Hering <hannes.hering@linux.vnet.ibm.com>
Cc: rdreier@cisco.com, alexs@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, ewg@lists.openfabrics.org,
linuxppc-dev@ozlabs.org, raisch@de.ibm.com,
ossrosch@linux.vnet.ibm.com
Subject: Re: [PATCH 2.6.31] ehca: Tolerate dynamic memory operations and huge pages
Date: Wed, 10 Jun 2009 10:02:36 +1000 [thread overview]
Message-ID: <1244592156.4680.5.camel@concordia> (raw)
In-Reply-To: <200906091559.24661.hannes.hering@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
On Tue, 2009-06-09 at 15:59 +0200, Hannes Hering wrote:
> This patch implements toleration of dynamic memory operations and 16 GB
> gigantic pages. On module load the driver walks through available system
> memory, checks for available memory ranges and then registers the kernel
> internal memory region accordingly. The translation of address ranges is
> implemented via a 3-level busmap.
Hi Hannes,
For those of us who haven't read the HEA spec lately, can you give us
some more detail on that? :)
How does it interact with kexec/kdump?
> +static int ehca_update_busmap(unsigned long pfn, unsigned long nr_pages)
> +{
> + unsigned long i, start_section, end_section;
> + int top, dir, idx;
> +
> + if (!nr_pages)
> + return 0;
> +
> + if (!ehca_bmap) {
> + ehca_bmap = kmalloc(sizeof(struct ehca_bmap), GFP_KERNEL);
> + if (!ehca_bmap)
> + return -ENOMEM;
> + /* Set map block to 0xFF according to EHCA_INVAL_ADDR */
> + memset(ehca_bmap, 0xFF, EHCA_TOP_MAP_SIZE);
> + }
> +
> + start_section = phys_to_abs(pfn * PAGE_SIZE) / EHCA_SECTSIZE;
> + end_section = phys_to_abs((pfn + nr_pages) * PAGE_SIZE) / EHCA_SECTSIZE;
phys_to_abs() ? As below, or does it come from somewhere else?
arch/powerpc/include/asm/abs_addr.h:
47 static inline unsigned long phys_to_abs(unsigned long pa)
48 {
49 unsigned long chunk;
50
51 /* This is a no-op on non-iSeries */
52 if (!firmware_has_feature(FW_FEATURE_ISERIES))
53 return pa;
54
55 chunk = addr_to_chunk(pa);
56
57 if (chunk < mschunks_map.num_chunks)
58 chunk = mschunks_map.mapping[chunk];
59
60 return chunk_to_addr(chunk) + (pa & MSCHUNKS_OFFSET_MASK);
61 }
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-10 0:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 13:59 [PATCH 2.6.31] ehca: Tolerate dynamic memory operations and huge pages Hannes Hering
2009-06-09 13:59 ` Hannes Hering
2009-06-10 0:02 ` Michael Ellerman [this message]
2009-06-10 8:54 ` Hannes Hering
2009-06-13 4:50 ` Roland Dreier
2009-06-13 4:50 ` Roland Dreier
2009-06-16 7:08 ` Alexander Schmidt
2009-06-16 7:08 ` Alexander Schmidt
2009-06-16 16:10 ` [ewg] " Roland Dreier
2009-06-16 16:10 ` Roland Dreier
2009-06-17 6:41 ` Alexander Schmidt
2009-06-16 7:10 ` [PATCH 2.6.31 try 2] " Alexander Schmidt
2009-06-16 7:10 ` Alexander Schmidt
2009-06-23 5:19 ` [ewg] " Roland Dreier
2009-06-23 5:19 ` Roland Dreier
2009-06-23 8:11 ` Alexander Schmidt
2009-06-23 8:11 ` Alexander Schmidt
2009-06-23 17:30 ` Roland Dreier
2009-06-23 17:30 ` Roland Dreier
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=1244592156.4680.5.camel@concordia \
--to=michael@ellerman.id.au \
--cc=alexs@linux.vnet.ibm.com \
--cc=ewg@lists.openfabrics.org \
--cc=hannes.hering@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ossrosch@linux.vnet.ibm.com \
--cc=raisch@de.ibm.com \
--cc=rdreier@cisco.com \
/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.