From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Date: Thu, 23 Nov 2017 04:52:00 +0000 Subject: Re: [RFC kvm-unit-tests PATCH] powerpc: add tests for XICS Message-Id: <1511412720.2466.41.camel@au1.ibm.com> List-Id: References: <20171012080704.31037-1-lvivier@redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Laurent Vivier , Thomas Huth , kvm-ppc@vger.kernel.org Cc: kvm@vger.kernel.org, Paolo Bonzini , Sam Bobroff On Wed, 2017-11-22 at 13:39 +0100, Laurent Vivier wrote: > These errors can be fixed by two different ways: > > A- don't allow set-xive to set the priority to 255 (the MASKED value) > and return an error value, and get-xive return an error value if > priority is the MASKED value > > B- store the server in set-xive even it the value is the MASKED one, so > we can get it with get-xive and use it with int-on (with the saved > priority value) > > (A) follows the specs: > > Linux on Power Architecture Platform Reference, v1.1 > R1–7.3.10.2–5. For the PowerPC External Interrupt option: The > ibm,set-xive call must return the Status of -3 > (Argument Error) for an unimplemented Interrupt number. > > (B) would behave like XICS with P8 and TCG. > > Any ideas? I don't see much point in supporting an unbalance where somebody masks with set_xive and unmasks with int_on... These PAPR APIs originates from pre-historical times, it's a bit of a mess. set_xive should be able to set a priority of 255, that's a requirement, but we could fix the emulation to store the server in that case I suppose. Ben.