From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC v2 03/20] memory: merge adjacent segments of a single memory region Date: Mon, 27 Jun 2011 15:56:24 +0200 Message-ID: <4E088C08.3090408@siemens.com> References: <1309180927-19003-1-git-send-email-avi@redhat.com> <1309180927-19003-4-git-send-email-avi@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from goliath.siemens.de ([192.35.17.28]:23964 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751571Ab1F0N4f (ORCPT ); Mon, 27 Jun 2011 09:56:35 -0400 In-Reply-To: <1309180927-19003-4-git-send-email-avi@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-06-27 15:21, Avi Kivity wrote: > Simple implementations of memory routers, for example the Cirrus VGA memory banks > or the 440FX PAM registers can generate adjacent memory regions which are contiguous. > Detect these and merge them; this saves kvm memory slots and shortens lookup times. That reminds me of KVM_CAP_JOIN_MEMORY_REGIONS_WORKS. Have you checked if things still work in the absence of the feature or if we need to lift our requirements on the host kernel (would be 2.6.30, not that problematic)? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux