From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, blauwirbel@gmail.com, kvm@vger.kernel.org
Subject: Re: [RESEND PATCH] acpi_piix4: save gpe and pci hotplug slot status
Date: Wed, 16 Jun 2010 17:47:18 +0200 [thread overview]
Message-ID: <m3zkyvx9mh.fsf@trasno.mitica> (raw)
In-Reply-To: <4C1697F3.3090107@codemonkey.ws> (Anthony Liguori's message of "Mon, 14 Jun 2010 15:58:27 -0500")
Anthony Liguori <anthony@codemonkey.ws> 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<alex.williamson@redhat.com>
>>
>
> 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.
Later, Juan.
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: blauwirbel@gmail.com,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [RESEND PATCH] acpi_piix4: save gpe and pci hotplug slot status
Date: Wed, 16 Jun 2010 17:47:18 +0200 [thread overview]
Message-ID: <m3zkyvx9mh.fsf@trasno.mitica> (raw)
In-Reply-To: <4C1697F3.3090107@codemonkey.ws> (Anthony Liguori's message of "Mon, 14 Jun 2010 15:58:27 -0500")
Anthony Liguori <anthony@codemonkey.ws> 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<alex.williamson@redhat.com>
>>
>
> 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.
Later, Juan.
next prev parent reply other threads:[~2010-06-16 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 20:28 [RESEND PATCH] acpi_piix4: save gpe and pci hotplug slot status Alex Williamson
2010-06-14 20:28 ` [Qemu-devel] " Alex Williamson
2010-06-14 20:58 ` Anthony Liguori
2010-06-14 20:58 ` Anthony Liguori
2010-06-14 21:27 ` Alexander Graf
2010-06-14 21:27 ` Alexander Graf
2010-06-16 15:47 ` Juan Quintela [this message]
2010-06-16 15:47 ` [Qemu-devel] " Juan Quintela
2010-06-16 16:28 ` Alex Williamson
2010-06-16 16:28 ` [Qemu-devel] " Alex Williamson
2010-06-16 18:43 ` Juan Quintela
2010-06-16 18:43 ` [Qemu-devel] " Juan Quintela
2010-06-16 18:46 ` Anthony Liguori
2010-06-16 18:46 ` [Qemu-devel] " Anthony Liguori
2010-06-16 19:14 ` Alex Williamson
2010-06-16 19:14 ` [Qemu-devel] " Alex Williamson
2010-06-16 23:05 ` Juan Quintela
2010-06-16 23:05 ` [Qemu-devel] " Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zkyvx9mh.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.