qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH RFC] pcie: clean up hot plug notification
Date: Mon, 25 Oct 2010 12:55:36 +0200	[thread overview]
Message-ID: <20101025105536.GA16526@redhat.com> (raw)
In-Reply-To: <20101025064638.GA4211@redhat.com>

On Mon, Oct 25, 2010 at 08:46:38AM +0200, Michael S. Tsirkin wrote:
> > > --- a/hw/pcie.h
> > > +++ b/hw/pcie.h
> > > @@ -74,6 +74,11 @@ struct PCIExpressDevice {
> > >                                   * also initialize it when loaded as
> > >                                   * appropreately.
> > >                                   */
> > > +    bool hpev_notified; /* Logical AND of conditions for hot plug event.
> > > +                         Following 6.7.3.4:
> > > +                         Software Notification of Hot-Plug Events, an interrupt
> > > +                         is sent whenever the logical and of these conditions
> > > +                         transitions from false to true. */
> > >  };
> > 
> > This breaks save/load.
> 
> Right. We'll need to restore this on load.
> Take a subfunction of hotplug_event_notify
> and put it in the appropriate _load function.

Or just call the notify - worst case we get an extra msi interrupt ...
Not sure whether this is required but this seems to be what we
do in virtio-pci. Up to you really ...

-- 
MST

      parent reply	other threads:[~2010-10-25 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25  5:49 [Qemu-devel] [PATCH RFC] pcie: clean up hot plug notification Michael S. Tsirkin
2010-10-25  6:08 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-25  6:44 ` Isaku Yamahata
2010-10-25  6:46   ` Michael S. Tsirkin
2010-10-25  7:04     ` Isaku Yamahata
2010-10-25  8:05       ` Michael S. Tsirkin
2010-10-25 10:55     ` Michael S. Tsirkin [this message]

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=20101025105536.GA16526@redhat.com \
    --to=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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).