qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, lvivier@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/4] ppc: adding some RTAS calls in tests/libqos
Date: Tue, 31 Oct 2017 18:43:26 -0200	[thread overview]
Message-ID: <20171031204330.14803-1-danielhb@linux.vnet.ibm.com> (raw)

v2:
- added a new patch to fix a Travis build issue with Mac OS

This series implements a few RTAS hypercalls in tests/libqos
that, used together, implement the DRC state transition described
in PAPR 2.7+, 13.4.

This started as an attempt of implementing hot unplug qtests for the
sPAPR machine but I've found a few issues that will require more time
solving:

- CPU hot unplug: for some reason the machine freezes after the
callback is returned.

- LMB hot unplug: not supported by the sPAPR machine if not
set in CAS.

I have a feeling that the CPU hot unplug  issue might be related
with the lack of CAS negotiation step as well, but only way to be
sure is to further understanding how the CAS negotation interfere
with the device hot unplug. If needed we'll have to implement the
client architecture support hypercall as well in the future.

Until then, I believe these hypercalls have a value of their own and
are worth being pushed upstream.


Daniel Henrique Barboza (4):
  tests: adding 'check_exception' RTAS implementation
  tests: adding 'set_indicator' RTAS call
  tests: ibm,configure-connector RTAS call implementation
  tests/rtas-test.c: fix Apple endian.h include

 tests/libqos/rtas.c | 105 ++++++++++++++++++++++++
 tests/libqos/rtas.h |   5 ++
 tests/rtas-test.c   | 229 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 339 insertions(+)

-- 
2.13.6

             reply	other threads:[~2017-10-31 20:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 20:43 Daniel Henrique Barboza [this message]
2017-10-31 20:43 ` [Qemu-devel] [PATCH v2 1/4] tests: adding 'check_exception' RTAS implementation Daniel Henrique Barboza
2017-11-06 15:12   ` Laurent Vivier
2017-11-09 12:02     ` [Qemu-devel] [Qemu-ppc] " Daniel Henrique Barboza
2017-11-29  0:19   ` [Qemu-devel] " Michael Roth
2017-10-31 20:43 ` [Qemu-devel] [PATCH v2 2/4] tests: adding 'set_indicator' RTAS call Daniel Henrique Barboza
2017-11-06 16:54   ` Laurent Vivier
2017-11-09 11:53     ` [Qemu-devel] [Qemu-ppc] " Daniel Henrique Barboza
2017-11-29  1:14   ` [Qemu-devel] " Michael Roth
2017-10-31 20:43 ` [Qemu-devel] [PATCH v2 3/4] tests: ibm, configure-connector RTAS call implementation Daniel Henrique Barboza
2017-11-06 17:46   ` Laurent Vivier
2017-11-09 12:35     ` [Qemu-devel] [Qemu-ppc] " Daniel Henrique Barboza
2017-11-29  0:02       ` Michael Roth
2017-11-29  8:57         ` Daniel Henrique Barboza
2017-11-29 12:21   ` [Qemu-devel] " Michael Roth
2017-10-31 20:43 ` [Qemu-devel] [PATCH v2 4/4] tests/rtas-test.c: fix Apple endian.h include 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=20171031204330.14803-1-danielhb@linux.vnet.ibm.com \
    --to=danielhb@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --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).