From: Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, jan.kiszka@siemens.com,
jbarnes@virtuousgeek.org
Subject: Re: [PATCH v3 0/3] Store and load PCI device saved state across function resets
Date: Thu, 21 Apr 2011 11:32:29 +0300 [thread overview]
Message-ID: <4DAFEB9D.4040402@redhat.com> (raw)
In-Reply-To: <20110420202523.3189.31306.stgit@s20.home>
On 04/20/2011 11:31 PM, Alex Williamson wrote:
> v2 -> v3:
> Saved structure has variable contents.
>
> Avi, see if this adds any credibility to the pci-core allocated
> opaque buffer. It was wrong in the previous versions to distill
> the variable device capability save list into a fixed struct.
> This should also eliminate any future maintenance specific to
> this storing and loading of state as capability save changes.
>
Haha, nice trick. Yes, it does.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-21 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 20:31 [PATCH v3 0/3] Store and load PCI device saved state across function resets Alex Williamson
2011-04-20 20:31 ` [PATCH v3 1/3] PCI: Track the size of each saved capability data area Alex Williamson
2011-05-09 20:43 ` Jesse Barnes
2011-04-20 20:31 ` [PATCH v3 2/3] PCI: Add interfaces to store and load the device saved state Alex Williamson
2011-04-20 20:31 ` [PATCH v3 3/3] KVM: Use pci_store/load_saved_state() around VM device usage Alex Williamson
2011-04-21 8:32 ` Avi Kivity
2011-04-21 8:32 ` Avi Kivity [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=4DAFEB9D.4040402@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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.