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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
