From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Remove qemu_alloc_physram() Date: Fri, 29 May 2009 11:35:13 +0300 Message-ID: <4A1F9E41.50503@redhat.com> References: <2803e73b0905270308l70cf562jaca72bf67d1aafff@mail.gmail.com> <4A1D3711.2070603@redhat.com> <2803e73b0905270630t5579f141lcb1013ae9aa146a9@mail.gmail.com> <2803e73b0905270640n56d9bfa3x15c0ecabd0b4676f@mail.gmail.com> <4A1D4739.4070208@redhat.com> <4A1D68AC.3050300@redhat.com> <20090528215352.GG11675@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: nicolas prochazka , kvm@vger.kernel.org To: Ryan Harper Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43244 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754903AbZE2IfI (ORCPT ); Fri, 29 May 2009 04:35:08 -0400 In-Reply-To: <20090528215352.GG11675@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Ryan Harper wrote: > This patch restores -mempath working for me on latest qemu-kvm.git. > Thanks for confirming. > btw, why'd we go from -mem-path (kvm-84/stable) to -mempath (kvm-85 and > newer)? Changing these breaks existing scripts. Not a big deal, but > wondering what was the motivation for the change. > It was accidental. Upstream moved the command line options definitions to a different file, and when I merged I didn't move over this option correctly. Code written during a merge is often of substandard quality. I'll fix it up. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.