From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756950Ab3CDLAa (ORCPT ); Mon, 4 Mar 2013 06:00:30 -0500 Received: from mx1.redhat.com ([209.132.183.28]:28233 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756222Ab3CDLA3 (ORCPT ); Mon, 4 Mar 2013 06:00:29 -0500 Date: Mon, 4 Mar 2013 12:59:28 +0200 From: Gleb Natapov To: Paolo Bonzini Cc: Hu Tao , kvm list , qemu-devel , "linux-kernel@vger.kernel.org" , "Daniel P. Berrange" , KAMEZAWA Hiroyuki , Jan Kiszka , Blue Swirl , Eric Blake , Andrew Jones , Marcelo Tosatti , Sasha Levin , Luiz Capitulino , Anthony Liguori , Markus Armbruster , Stefan Hajnoczi , Juan Quintela , Orit Wasserman , Kevin Wolf , Wen Congyang , "Michael S. Tsirkin" , Alexander Graf , Alex Williamson , Peter Maydell Subject: Re: [PATCH v13 0/8] pv event interface between host and guest Message-ID: <20130304105928.GM23616@redhat.com> References: <20130303091738.GB23616@redhat.com> <513471F1.5020702@redhat.com> <20130304102131.GK23616@redhat.com> <51347735.9090204@redhat.com> <20130304104301.GL23616@redhat.com> <51347C23.8080802@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51347C23.8080802@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 04, 2013 at 11:49:07AM +0100, Paolo Bonzini wrote: > Il 04/03/2013 11:43, Gleb Natapov ha scritto: > > > Anyhow, this does not apply to the next submission of this series. I > > > think we can agree to the compromise of using ACPI but still read the > > > port in _STA. > > > > If you want to make ioport configurable I do not see how can we avoid > > patching. > > I want to make the ioport configurable in the device, but the PIIX and > ICH9 (which are what the DSDT is written for) will always use port 0x505. > But the device is not part of PIIX or ICH9. It is additional device that may or may not be present depending on a command line. So what if someone configures debugcon or debugexit to use this port? We can always blame the users, but I fill that we are making unnecessary compromises. > You can configure a different iobase for your serial ports, the guest > can still use them but not discover them via ACPI. This is the same thing. > Probably we should patch DSDT too when it will be in QEMU :) of force iobase to spec values if device is used as part of a chipset. -- Gleb.