Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Laurent Vivier <lvivier@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Sam Bobroff <sbobroff@redhat.com>
Subject: Re: [RFC kvm-unit-tests PATCH] powerpc: add tests for XICS
Date: Thu, 23 Nov 2017 04:52:00 +0000	[thread overview]
Message-ID: <1511412720.2466.41.camel@au1.ibm.com> (raw)
In-Reply-To: <b050a042-b55b-004c-bfcb-69f192e68eea@redhat.com>

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.


  reply	other threads:[~2017-11-23  4:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  8:07 [RFC PATCH] powerpc: add tests for XICS Laurent Vivier
2017-10-13  9:45 ` [RFC kvm-unit-tests " Thomas Huth
2017-10-16 12:34   ` Laurent Vivier
2017-11-22 12:39     ` Laurent Vivier
2017-11-23  4:52       ` Benjamin Herrenschmidt [this message]
2017-10-16 17:08   ` Laurent Vivier
2017-10-18  8:11     ` Andrew Jones

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=1511412720.2466.41.camel@au1.ibm.com \
    --to=benh@au1.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=sbobroff@redhat.com \
    --cc=thuth@redhat.com \
    /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