From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts Date: Tue, 25 Jan 2011 17:35:40 +0100 Message-ID: <4D3EFBDC.201@web.de> References: <20110121233040.22262.68117.stgit@s20.home> <20110124093241.GA28654@amt.cnet> <4D3D89B1.30300@siemens.com> <1295883899.3230.9.camel@x201> <1295933876.3230.46.camel@x201> <4D3E7D74.1030100@web.de> <1295966492.3230.55.camel@x201> <4D3EE3F8.3020603@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD7FBA8D18E0847F8AB4ED6E8" Cc: Alex Williamson , Marcelo Tosatti , "kvm@vger.kernel.org" , "ddutile@redhat.com" , "mst@redhat.com" , "chrisw@redhat.com" To: Avi Kivity Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:36908 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301Ab1AYQfq (ORCPT ); Tue, 25 Jan 2011 11:35:46 -0500 In-Reply-To: <4D3EE3F8.3020603@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD7FBA8D18E0847F8AB4ED6E8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2011-01-25 15:53, Avi Kivity wrote: > On 01/25/2011 04:41 PM, Alex Williamson wrote: >> > > >> > > >> > > kvm: Allow memory slot array to grow on demand >> > > >> > > Remove fixed KVM_MEMORY_SLOTS limit, allowing the slot array >> > > to grow on demand. Private slots are now allocated at the >> > > front instead of the end. Only x86 seems to use private slots, >> > >> > Hmm, doesn't current user space expect slots 8..11 to be the privat= e >> > ones and wouldn't it cause troubles if slots 0..3 are suddenly >> reserved? >> >> The private slots aren't currently visible to userspace, they're >> actually slots 32..35. The patch automatically increments user passed= >> slot ids so userspace has it's own zero-based view of the array. >> Frankly, I don't understand why userspace reserves slots 8..11, is thi= s >> compatibility with older kernel implementations? >=20 > I think so. I believe these kernel versions are too old now to matter,= > but of course I can't be sure. Will check and enable those 4 additional slots for user space if we no longer need to exclude them. Jan --------------enigD7FBA8D18E0847F8AB4ED6E8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk0++98ACgkQitSsb3rl5xTteQCgpYJEFndE4ATCBJeWkMzBLEz4 9mcAnj7qvoBpDQkooHv76yePG0YhARKv =DKfo -----END PGP SIGNATURE----- --------------enigD7FBA8D18E0847F8AB4ED6E8--