From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au,
mdroth@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v13] migration: spapr: migrate pending_events of spapr state
Date: Mon, 22 May 2017 15:40:38 -0300 [thread overview]
Message-ID: <20170522184039.23877-1-danielhb@linux.vnet.ibm.com> (raw)
v13:
- rebased with dgibson/ppc-for-2.10
- patch 1 removed from the series (already applied at ppc-for-2.10)
- data_size is now being calculated by using the extended_length field inside
rtas_event_log_queue
v12:
- patch 2: added a switch statement to get the proper data_size based on
the log_type
v11:
- patch 1 (new): cleanup of spapr_events.c:
* removed the 'exception' boolean from the sPAPREventLogEntry
* simplified the 'event_scan' function
- patch 2:
* data_size is now calculated inside rtas_event_log_queue()
* using VBUFFER instead of VARRAY to avoid casts
* log_type changed to int32_t
v10: detached from DRC patch set
v9: no changes
v8: no changes
v7: no changes
v6: - Rebased with QEMU master after 6+ months.
class and minor improvements.
- Added clarifications from the previous v5 discussions in the commit messages.
v5: - Rebased on David's ppc-for-2.8.
v4: - Rebased on David's ppc-for-2.7.
v3: - Simplify overall design followng discussion with Paolo. No longer need
metadata to migrate QTAILQ.
- Extend VMStateInfo instead of adding similar fields to VMStateField.
v2: - Put the newly added migrating fields in subsections so that backward
migration is not broken.
(link: https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg04188.html)
v1: - Inital version.
(link: https://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02601.html)
This patch was detached from the patchset:
"[PATCH v9 0/6] migration/ppc: migrating DRC, ccs_list and pending_events"
Because it is independent and has use outside of the scope of the
pseries DRC migration patchset.
Jianjun Duan (1):
migration: spapr: migrate pending_events of spapr state
hw/ppc/spapr.c | 32 ++++++++++++++++++++++++++++++++
hw/ppc/spapr_events.c | 19 +++++++++++++++++++
include/hw/ppc/spapr.h | 3 ++-
3 files changed, 53 insertions(+), 1 deletion(-)
--
2.9.4
next reply other threads:[~2017-05-22 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 18:40 Daniel Henrique Barboza [this message]
2017-05-22 18:40 ` [Qemu-devel] [PATCH v13] migration: spapr: migrate pending_events of spapr state Daniel Henrique Barboza
2017-05-23 4:07 ` David Gibson
2017-05-23 14:54 ` [Qemu-devel] [Qemu-ppc] " Daniel Henrique Barboza
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=20170522184039.23877-1-danielhb@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).