From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Huang, Ying" <ying.huang@intel.com>, linux-mm@kvack.org
Cc: "H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
Date: Tue, 9 Oct 2007 01:25:26 +1000 [thread overview]
Message-ID: <200710090125.27263.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <1191912010.9719.18.camel@caritas-dev.intel.com>
On Tuesday 09 October 2007 16:40, Huang, Ying wrote:
> +unsigned long copy_from_phys(void *to, unsigned long from_phys,
> + unsigned long n)
> +{
> + struct page *page;
> + void *from;
> + unsigned long remain = n, offset, trunck;
> +
> + while (remain) {
> + page = pfn_to_page(from_phys >> PAGE_SHIFT);
> + from = kmap_atomic(page, KM_USER0);
> + offset = from_phys & ~PAGE_MASK;
> + if (remain > PAGE_SIZE - offset)
> + trunck = PAGE_SIZE - offset;
> + else
> + trunck = remain;
> + memcpy(to, from + offset, trunck);
> + kunmap_atomic(from, KM_USER0);
> + to += trunck;
> + from_phys += trunck;
> + remain -= trunck;
> + }
> + return n;
> +}
I suppose that's not unreasonable to put in mm/memory.c, although
it's not really considered a problem to do this kind of stuff in
a low level arch file...
You have no kernel virtual mapping for the source data?
Should it be __init?
Care to add a line of documentation if you keep it in mm/memory.c?
Thanks,
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2007-10-08 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1191912010.9719.18.camel@caritas-dev.intel.com>
2007-10-08 15:25 ` Nick Piggin [this message]
2007-10-09 8:22 ` Huang, Ying
2007-10-08 16:06 ` Nick Piggin
2007-10-09 8:55 ` Huang, Ying
2007-10-08 16:28 ` Nick Piggin
2007-10-09 9:26 ` Huang, Ying
2007-10-09 11:44 ` Oleg Verych
2007-10-09 11:13 ` Andi Kleen
2007-10-09 14:00 ` huang ying
2007-10-09 14:04 ` Andi Kleen
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=200710090125.27263.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mouli@linux.intel.com \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox