From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RESEND PATCH] acpi_piix4: save gpe and pci hotplug slot status Date: Wed, 16 Jun 2010 13:46:03 -0500 Message-ID: <4C191BEB.4020207@codemonkey.ws> References: <20100614202803.5259.85808.stgit@localhost.localdomain> <4C1697F3.3090107@codemonkey.ws> <1276705730.12015.964.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alex Williamson , qemu-devel@nongnu.org, blauwirbel@gmail.com, kvm@vger.kernel.org To: Juan Quintela Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:50370 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932119Ab0FPSqG (ORCPT ); Wed, 16 Jun 2010 14:46:06 -0400 Received: by iwn9 with SMTP id 9so5958804iwn.19 for ; Wed, 16 Jun 2010 11:46:06 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 06/16/2010 01:43 PM, Juan Quintela wrote: > Alex Williamson wrote: > >> On Wed, 2010-06-16 at 17:47 +0200, Juan Quintela wrote: >> >>> Anthony Liguori wrote: >>> >>>> On 06/14/2010 03:28 PM, Alex Williamson wrote: >>>> >>>>> PCI hotplug currently doesn't work after a migration because >>>>> we don't migrate the enable bits of the GPE state. Pull hotplug >>>>> structs into vmstate. >>>>> >>>>> Signed-off-by: Alex Williamson >>>>> >>>>> >>>> Applied. Thanks. >>>> >>>> Regards, >>>> >>>> Anthony Liguori >>>> >>> I think this is better implemented as a subsection. We didin't need >>> this until hotplug arrived, I think that checking if any up/down are >>> != 0 and then send it as subsections is a best way to do it. >>> >>> This way it could also be backported to stable. >>> >> The slots aren't really the issue, they were mostly for completeness. >> The key is gpe.en, which is likely always going to be all 1s for an ACPI >> aware OS. So if we test != 0, we're going to need that subsection in >> 99% of the cases. Maybe we can assume gpe.en is all set on the target, >> but I don't really look forward to finding out the ways that might >> break. Thanks, >> > We have never sent it before. That means that the default value (for > whatever value is it) should be working quite well. > > But it is not my call. > This sounds like a case where we're sending broken state so we need to bump the version number. Subsections don't eliminate the need to bump version numbers when we fundamentally screw up. Regards, Anthony Liguori > Later, Juan. >