public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 03/28] ia64/xen: increase IA64_MAX_RSVD_REGIONS.
Date: Fri, 22 Feb 2008 05:33:16 +0000	[thread overview]
Message-ID: <20080222053316.GL11391@sgi.com> (raw)
In-Reply-To: <12036570474112-git-send-email-yamahata@valinux.co.jp>

On Fri, Feb 22, 2008 at 02:10:19PM +0900, Isaku Yamahata wrote:
> Xenlinux/ia64 needs to reserve one more region passed from xen hypervisor
> as start info.
> 
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
> ---
>  include/asm-ia64/meminit.h |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/include/asm-ia64/meminit.h b/include/asm-ia64/meminit.h
> index f93308f..7c12c08 100644
> --- a/include/asm-ia64/meminit.h
> +++ b/include/asm-ia64/meminit.h
> @@ -18,10 +18,17 @@
>   * 	- crash dumping code reserved region
>   * 	- Kernel memory map built from EFI memory map
>   * 	- ELF core header
> + * ifdef CONFIG_XEN
> + *	- xen start info
> + * endif
>   *
>   * More could be added if necessary
>   */
> +#ifdef CONFIG_XEN
>  #define IA64_MAX_RSVD_REGIONS 8
> +#else
> +#define IA64_MAX_RSVD_REGIONS 9
> +#endif

This one seems upside down to me.  You are saying there is an additional
region when CONFIG_XEN, but you are defining it larger for !CONFIG_XEN.
I concede the point that I know nothing about Xen, so please straighten
me out here.

Thanks,
Robin

  reply	other threads:[~2008-02-22  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  5:10 [PATCH 03/28] ia64/xen: increase IA64_MAX_RSVD_REGIONS Isaku Yamahata
2008-02-22  5:33 ` Robin Holt [this message]
2008-02-22  6:02 ` Isaku Yamahata
2008-02-25 17:18 ` Bjorn Helgaas
2008-02-26  1:57 ` Isaku Yamahata

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=20080222053316.GL11391@sgi.com \
    --to=holt@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