From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: VMX: Move private memory slot position Date: Sat, 13 Sep 2008 08:01:41 +0300 Message-ID: <48CB4935.5090505@qumranet.com> References: <200809041130.20249.sheng.yang@intel.com> <200809111726.52202.sheng.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: "Yang, Sheng" Return-path: Received: from il.qumranet.com ([212.179.150.194]:22089 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751555AbYIMFEI (ORCPT ); Sat, 13 Sep 2008 01:04:08 -0400 In-Reply-To: <200809111726.52202.sheng.yang@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Yang, Sheng wrote: > On Thursday 04 September 2008 11:30:20 Yang, Sheng wrote: > >> From ebe4ea311305d2910dcdcff2510662da0dc2c742 Mon Sep 17 00:00:00 2001 >> From: Sheng Yang >> Date: Thu, 4 Sep 2008 03:11:48 +0800 >> Subject: [PATCH] KVM: VMX: Move private memory slot position >> >> PCI device assignment would map guest MMIO spaces as separate slot, so it >> is possible that the device has more than 2 MMIO spaces and overwrite >> current private memslot. >> >> The patch move private memory slot to the top of userspace visible memory >> slots. >> >> > > Avi, these two? > Thanks, applied both. Note that kvm now exports the number of slots using KVM_CAP_NR_MEMSLOTS, so userspace could be made dynamic. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.