qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	mdroth@linux.vnet.ibm.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos
Date: Mon, 30 Oct 2017 21:12:13 +0100	[thread overview]
Message-ID: <20171030201213.GA2911@umbus> (raw)
In-Reply-To: <20171026202250.6118-1-danielhb@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote:
> 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.

Unfortunately, these changes break the Travis build on MacOS.
> 
> 
> Daniel Henrique Barboza (3):
>   tests: adding 'check_exception' RTAS implementation
>   tests: adding 'set_indicator' RTAS call
>   tests: ibm,configure-connector RTAS call implementation
> 
>  tests/libqos/rtas.c | 105 +++++++++++++++++++++++++
>  tests/libqos/rtas.h |   5 ++
>  tests/rtas-test.c   | 218 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 328 insertions(+)
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-10-30 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 20:22 [Qemu-devel] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos Daniel Henrique Barboza
2017-10-26 20:22 ` [Qemu-devel] [PATCH v1 1/3] tests: adding 'check_exception' RTAS implementation Daniel Henrique Barboza
2017-10-26 20:22 ` [Qemu-devel] [PATCH v1 2/3] tests: adding 'set_indicator' RTAS call Daniel Henrique Barboza
2017-10-26 20:22 ` [Qemu-devel] [PATCH v1 3/3] tests: ibm, configure-connector RTAS call implementation Daniel Henrique Barboza
2017-10-30 20:12 ` David Gibson [this message]
2017-10-30 20:29   ` [Qemu-devel] [Qemu-ppc] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos Daniel Henrique Barboza
2017-10-30 23:21     ` 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=20171030201213.GA2911@umbus \
    --to=david@gibson.dropbear.id.au \
    --cc=danielhb@linux.vnet.ibm.com \
    --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).