qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Corey Minyard <cminyard@mvista.com>
Cc: minyard@acm.org, qemu-devel@nongnu.org,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pc:piix4: Update smbus I/O space after a migration
Date: Thu, 29 Nov 2018 10:49:42 -0500	[thread overview]
Message-ID: <20181129104930-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d7a7cb4a-a55d-ec84-4bd8-89ef3fad7ebf@mvista.com>

On Thu, Nov 29, 2018 at 09:45:17AM -0600, Corey Minyard wrote:
> On 11/26/18 12:28 PM, minyard@acm.org wrote:
> > From: Corey Minyard <cminyard@mvista.com>
> > 
> > Otherwise it won't be set up correctly and won't work after
> > miigration.
> 
> Any opinions on this?  I think this would be good for 3.1. Without
> this when a migration occurs on piix4 the SMBus address space
> appears in the wrong place.  I'm not sure how bad that is, but
> SMBus certainly ceases to work.
> 
> -corey


I have this queued. Thanks!

> 
> > Signed-off-by: Corey Minyard <cminyard@mvista.com>
> > Cc: Michael S. Tsirkin <mst@redhat.com>
> > Cc: Igor Mammedov <imammedo@redhat.com>
> > ---
> >   hw/acpi/piix4.c | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > A rather obvious fix, in hindsight :).
> > 
> > diff --git a/hw/acpi/piix4.c b/hw/acpi/piix4.c
> > index e330f24c71..2f4dd03b83 100644
> > --- a/hw/acpi/piix4.c
> > +++ b/hw/acpi/piix4.c
> > @@ -173,6 +173,7 @@ static int vmstate_acpi_post_load(void *opaque, int version_id)
> >       PIIX4PMState *s = opaque;
> >       pm_io_space_update(s);
> > +    smbus_io_space_update(s);
> >       return 0;
> >   }
> 

  reply	other threads:[~2018-11-29 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 18:28 [Qemu-devel] [PATCH] pc:piix4: Update smbus I/O space after a migration minyard
2018-11-29 15:45 ` Corey Minyard
2018-11-29 15:49   ` Michael S. Tsirkin [this message]
2018-11-29 16:43     ` [Qemu-devel] [PATCH for-3.1?] " Eric Blake
2018-12-03 15:14       ` Peter Maydell

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=20181129104930-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cminyard@mvista.com \
    --cc=imammedo@redhat.com \
    --cc=minyard@acm.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 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).