public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC/PATCH] discontig update for linux-ia64-2.5 bk tree
Date: Thu, 19 Jun 2003 00:14:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105598178814109@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105595347015732@msgid-missing>

On Wed, Jun 18, 2003 at 05:11:10PM -0700, David Mosberger wrote:
> I missed this on first reading:
> 
>  		for (cpu = 0; cpu < NR_CPUS; cpu++) {
> -			memcpy(cpu_data, __phys_per_cpu_start, __per_cpu_end - __per_cpu_start);
>  			__per_cpu_offset[cpu] = (char *) cpu_data - __per_cpu_start;
>  			cpu_data += PERCPU_PAGE_SIZE;
>  		}
> +		for (cpu = 0; cpu < NR_CPUS; cpu++) {
> +			cpu_data = __per_cpu_offset[cpu] + __per_cpu_start;
> +			memcpy(cpu_data, __phys_per_cpu_start, __per_cpu_end - __per_cpu_start);
> +		}
> 
> What's the point of this?

Arg, I saw that when I got my copy back (along with a couple of other
things).  I'll fix them up.

> The patch still removes CONFIG_VIRTUAL_MEM_MAP.

...

> Also, please note that I don't want to add any ia64 patches that
> create additional dependencies on core code (I'm trying to sync things
> such that ia64 builds out of the box).  So before submitting
> ia64-specific changes, please make sure the core-code is ready for it.

Ok.  I'll try to get the bootmem changes in first.

Thanks,
Jesse

      parent reply	other threads:[~2003-06-19  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 16:14 [RFC/PATCH] discontig update for linux-ia64-2.5 bk tree Jesse Barnes
2003-06-18 17:42 ` David Mosberger
2003-06-18 17:48 ` Jesse Barnes
2003-06-18 23:57 ` Jesse Barnes
2003-06-19  0:11 ` David Mosberger
2003-06-19  0:14 ` Jesse Barnes [this message]

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=marc-linux-ia64-105598178814109@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox