From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: minyard@acm.org
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] ipmi: Fix vmstate transfer
Date: Fri, 2 Mar 2018 20:02:03 +0000 [thread overview]
Message-ID: <20180302200202.GF3154@work-vm> (raw)
In-Reply-To: <1520004397-28521-1-git-send-email-minyard@acm.org>
* minyard@acm.org (minyard@acm.org) wrote:
> I apologize for the resend, I left the list off the previous post.
>
> This is unchanged since the previous post, two weeks ago. I received
> no comments, so I guess it's ok. It's fairly broken now, so I would
> like this fixed.
Sorry, I'll look at it on Monday; I was out last week and hadn't got
around to this set.
Dave
> Changes from v1:
> * Validate the data values in pre_load functions.
> * For KCS, instead of an old function, create a separate vmstate
> structure for the new version. The name on the old vmstate
> structure wasn't specific enough, so a new name was needed,
> The old structure is set up to never be sent, but it can be
> received.
>
> The following changes since commit 427cbc7e4136a061628cb4315cc8182ea36d772f:
>
> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2018-03-01 18:46:41 +0000)
>
> are available in the git repository at:
>
> https://github.com/cminyard/qemu.git tags/ipmi-vmstate-fixes
>
> for you to fetch changes up to 90797371d9a3138657e7b1f7ab4425eb67d6fd0a:
>
> ipmi: Use proper struct reference for BT vmstate (2018-03-02 07:48:39 -0600)
>
> ----------------------------------------------------------------
> Fix the IPMI vmstate code to work correctly in all cases. Heavily
> tested under load.
>
> ----------------------------------------------------------------
> Corey Minyard (2):
> ipmi: Use proper struct reference for KCS vmstate
> ipmi: Use proper struct reference for BT vmstate
>
> hw/ipmi/isa_ipmi_bt.c | 61 ++++++++++++++++++++++++++++++---------
> hw/ipmi/isa_ipmi_kcs.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++++--
> 2 files changed, 123 insertions(+), 15 deletions(-)
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-03-02 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:26 [Qemu-devel] [PATCH v2 0/2] ipmi: Fix vmstate transfer minyard
2018-03-02 15:26 ` [Qemu-devel] [PATCH v2 1/2] ipmi: Use proper struct reference for KCS vmstate minyard
2018-03-05 14:09 ` Dr. David Alan Gilbert
2018-03-05 22:52 ` Corey Minyard
2018-03-06 16:46 ` Corey Minyard
2018-04-24 15:32 ` Dr. David Alan Gilbert
2018-04-24 21:08 ` Corey Minyard
2018-03-02 15:26 ` [Qemu-devel] [PATCH v2 2/2] ipmi: Use proper struct reference for BT vmstate minyard
2018-03-05 12:00 ` Dr. David Alan Gilbert
2018-03-02 20:02 ` Dr. David Alan Gilbert [this message]
2018-03-02 20:09 ` [Qemu-devel] [PATCH v2 0/2] ipmi: Fix vmstate transfer Corey Minyard
2018-03-05 13:29 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 18:23 minyard
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=20180302200202.GF3154@work-vm \
--to=dgilbert@redhat.com \
--cc=minyard@acm.org \
--cc=peter.maydell@linaro.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).