From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [PATCH 3/4] introduce boot parameter for setting XENFEAT_virtual_p2m Date: Thu, 20 Nov 2014 05:46:35 +0100 Message-ID: <546D722B.5040606@suse.com> References: <1415957846-22703-1-git-send-email-jgross@suse.com> <1415957846-22703-4-git-send-email-jgross@suse.com> <20141119210453.GC20440@laptop.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141119210453.GC20440@laptop.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, david.vrabel@citrix.com, jbeulich@suse.com List-Id: xen-devel@lists.xenproject.org On 11/19/2014 10:04 PM, Konrad Rzeszutek Wilk wrote: > On Fri, Nov 14, 2014 at 10:37:25AM +0100, Juergen Gross wrote: >> Introduce a new boot parameter "virt_p2m" to be able to set >> XENFEAT_virtual_p2m for a pv domain. >> >> As long as Xen tools and kdump don't support this new feature it is >> turned off by default. > > Couldn't the dom0_large and dom0 be detected automatically? That is > the dom0 could advertise it can do large-dom0 support and Xen would > automatically switch to the right mode? No, that's not the problem. Xen has to indicate it is capable to handle the new mode. At dom0 construction time the dom0 kernel can't know about the capability of kdump to handle the new mode. In case the new interface is accepted I'll set up some kdump patches to handle it. We can switch to dom0/dom0_large set on default if they are accepted on time (e.g. at the time the kernel support for the new interface is put in place). Juergen