linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Gleb Natapov <gleb@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [RFCv3][PATCH 1/3] create slow_virt_to_phys()
Date: Tue, 15 Jan 2013 12:04:49 -0500	[thread overview]
Message-ID: <50F58C31.3020105@redhat.com> (raw)
In-Reply-To: <20130109185904.DD641DCE@kernel.stglabs.ibm.com>

On 01/09/2013 01:59 PM, Dave Hansen wrote:
> Broadening the cc list here a bit...  This bug is still present,
> and I still need these patches to boot 32-bit NUMA kernels.  They
> might be obscure, but if we don't care about them any more, perhaps
> we should go remove the NUMA remapping code instead of this.
>
> --
>
> This is necessary because __pa() does not work on some kinds of
> memory, like vmalloc() or the alloc_remap() areas on 32-bit
> NUMA systems.  We have some functions to do conversions _like_
> this in the vmalloc() code (like vmalloc_to_page()), but they
> do not work on sizes other than 4k pages.  We would potentially
> need to be able to handle all the page sizes that we use for
> the kernel linear mapping (4k, 2M, 1G).

Acked-by: Rik van Riel <riel@redhat.com>


-- 
All rights reversed

  parent reply	other threads:[~2013-01-15 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 18:59 [RFCv3][PATCH 1/3] create slow_virt_to_phys() Dave Hansen
2013-01-09 18:59 ` [RFCv3][PATCH 2/3] fix kvm's use of __pa() on percpu areas Dave Hansen
2013-01-15 18:38   ` Rik van Riel
2013-01-09 18:59 ` [RFCv3][PATCH 3/3] make DEBUG_VIRTUAL work earlier in boot Dave Hansen
2013-01-15 17:04 ` Rik van Riel [this message]
2013-01-15 19:46 ` [RFCv3][PATCH 1/3] create slow_virt_to_phys() H. Peter Anvin
2013-01-15 22:50   ` Dave Hansen
2013-01-15 23:46     ` H. Peter Anvin

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=50F58C31.3020105@redhat.com \
    --to=riel@redhat.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).