Date: Wed, 17 May 2006 09:06:45 -0700
From: Pete Zaitcev <zaitcev@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
       Christian.Limpach@cl.cam.ac.uk, xen-devel@lists.xensource.com,
       ian.pratt@xensource.com, zaitcev@redhat.com
Subject: Re: [RFC PATCH 08/35] Add Xen-specific memory management
 definitions
Message-Id: <20060517090645.0b72bd2d.zaitcev@redhat.com>
In-Reply-To: <20060509085151.047254000@sous-sol.org>
References: <20060509084945.373541000@sous-sol.org>
	<20060509085151.047254000@sous-sol.org>
Organization: Red Hat, Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 866
Lines: 26

On Tue, 09 May 2006 00:00:08 -0700, Chris Wright <chrisw@sous-sol.org> wrote:

> +static inline unsigned long pfn_to_mfn(unsigned long pfn)
> +{
> +#ifndef CONFIG_XEN_SHADOW_MODE
> +	if (xen_feature(XENFEAT_auto_translated_physmap))
> +		return pfn;
> +	return phys_to_machine_mapping[(unsigned int)(pfn)] &
> +		~FOREIGN_FRAME_BIT;
> +#else
> +	return pfn;
> +#endif
> +}

Why do we need several modes in Linux guests?

If a significant tradeoff exists (for example, between performance
and maximum addressable memory), then we need to think about the
real issue instead of throwing config options into the pot.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/