From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:36229)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SW7rK-00052g-FR
	for qemu-devel@nongnu.org; Sun, 20 May 2012 11:15:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SW7rI-0004XW-Kq
	for qemu-devel@nongnu.org; Sun, 20 May 2012 11:15:50 -0400
Received: from mx1.redhat.com ([209.132.183.28]:38958)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1SW7rI-0004XF-Ac
	for qemu-devel@nongnu.org; Sun, 20 May 2012 11:15:48 -0400
Date: Sun, 20 May 2012 18:15:44 +0300
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20120520151544.GP10209@redhat.com>
References: <20120520121539.GJ10209@redhat.com> <4FB8E3FA.2040408@redhat.com>
	<20120520123633.GL10209@redhat.com> <4FB8E7C6.5090000@redhat.com>
	<20120520125936.GM10209@redhat.com> <4FB8F3F5.6010903@redhat.com>
	<20120520135733.GN10209@redhat.com> <4FB90110.1000003@redhat.com>
	<20120520144338.GO10209@redhat.com> <4FB903D6.5090205@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FB903D6.5090205@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] Get system state configuration from
 QEMU and patch DSDT with it.
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org

On Sun, May 20, 2012 at 05:46:46PM +0300, Avi Kivity wrote:
> On 05/20/2012 05:43 PM, Gleb Natapov wrote:
> > > 
> > > Or it can be a fixed address in low memory, or a scratch register in
> > > hardware.
> > > 
> > Both will work (fixed addresses are better be avoided and who needs
> > another PV device), but I do not see how either of them is better then
> > patching. What is your concern?
> >
> 
> Patching is harder to maintain.  Unfortunately it's unavoidable.
> 
Here we in agreement, and I was against patching till it was unavoidable,
but than pci hotplug started using it, and afterwards processor
definitions, so no point in avoiding it now by using inferior methods.
 
--
			Gleb.