qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: blauwirbel@gmail.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 13:14:24 -0600	[thread overview]
Message-ID: <1276715664.12015.974.camel@x201> (raw)
In-Reply-To: <m3iq5istqw.fsf@trasno.mitica>

On Wed, 2010-06-16 at 20:43 +0200, Juan Quintela wrote:
> Alex Williamson <alex.williamson@redhat.com> wrote:
> > On Wed, 2010-06-16 at 17:47 +0200, Juan Quintela wrote:
> >> 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.
> >
> > 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.

The gpe.en bits back an ioport range that's poked by the guest via ACPI.
So the guest is the one telling ACPI "I enable you to send me this gpe".
When a hotplug event happens, we figure out which gpe line it would
toggle, set the matching gpe.sts bit, then if the OS has told us to
enable that bit, we send an interrupt.  The OS then masks gpe.en, checks
gpe.sts, preforms actions and clears the respective gpe.sts bits, then
re-enables gpe.en.  So, qemu never sets the bits, but if we decide to
clear (or set) them, we're interfering with how the OS expects them to
work.  I think we're screwed, we need to bump the rev.

Alex

  parent reply	other threads:[~2010-06-16 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 20:28 [Qemu-devel] [RESEND PATCH] acpi_piix4: save gpe and pci hotplug slot status Alex Williamson
2010-06-14 20:58 ` Anthony Liguori
2010-06-14 21:27   ` Alexander Graf
2010-06-16 15:47   ` [Qemu-devel] " Juan Quintela
2010-06-16 16:28     ` Alex Williamson
2010-06-16 18:43       ` Juan Quintela
2010-06-16 18:46         ` Anthony Liguori
2010-06-16 19:14         ` Alex Williamson [this message]
2010-06-16 23:05           ` 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=1276715664.12015.974.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).