public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization@lists.osdl.org, xen-devel@lists.xensource.com
Subject: Re: [PATCH, experimental] i386 Allow the fixmap to be relocated at boot time
Date: Fri, 5 Aug 2005 17:22:06 -0700	[thread overview]
Message-ID: <20050806002206.GZ7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <42F3FFBA.3040009@vmware.com>

* Zachary Amsden (zach@vmware.com) wrote:
> Your patch looks good, although the minimal change to subarch is to 
> merely have __FIXADDR_TOP defined by the sub-architecture.  Is there any 
> additional benefit to moving the fixmaps into the subarch - i.e. moving 
> subarch-specific pieces out of mach-default?

As you've identified, so subarch can put whatever wonky junk
it needs in there.

> I guess there is.  For example include/asm-i386/mach-visws/mach_fixmap.h 
> could do this:
> 
> #define SUBARCH_FIXMAPS \
>        FIX_CO_CPU,     /* Cobalt timer */ \
>        FIX_CO_APIC,    /* Cobalt APIC Redirection Table */ \
>        FIX_LI_PCIA,    /* Lithium PCI Bridge A */ \
>        FIX_LI_PCIB,    /* Lithium PCI Bridge B */
> 
> Then include/asm-i386/fixmap.h includes <mach_fixmap.h>, for which the 
> default is an empty define for SUBARCH_FIXMAPS.

nice.

> Also, it seems reasonable that people may want to poke holes in high 
> linear space for other hypervisor projects, research, or performance 
> reasons without having to build a custom sub-architecture just for 
> that.  So I think there is some benefit to making the hole size a 
> general configurable option (with defaults depending on the sub-arch you 
> select).

It needs to have tangible value for in-tree code.  Seems worthwhile to
play with it a bit though.

thanks,
-chris

  reply	other threads:[~2005-08-06  0:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 23:28 [PATCH,experimental] i386 Allow the fixmap to be relocated at boot time Zachary Amsden
2005-08-05 23:46 ` [PATCH, experimental] " Chris Wright
2005-08-06  0:09   ` Zachary Amsden
2005-08-06  0:22     ` Chris Wright [this message]
2005-08-06 12:48     ` Rusty Russell

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=20050806002206.GZ7762@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=zach@vmware.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