qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] ppc: add support for Directed Privileged Doorbell (non-hypervisor)
Date: Tue, 21 Jan 2020 14:38:00 +1100	[thread overview]
Message-ID: <20200121033800.GA265522@umbus.fritz.box> (raw)
In-Reply-To: <20200120104935.24449-1-clg@kaod.org>

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

On Mon, Jan 20, 2020 at 11:49:33AM +0100, Cédric Le Goater wrote:
> Hello,
> 
> The Processor Control facility for POWER8 processors and later
> provides a mechanism for the hypervisor to send messages to other
> threads in the system (msgsnd instruction) and cause hypervisor-level
> exceptions.
> 
> Privileged non-hypervisor programs can also send messages (msgsndp
> instruction) but are restricted to the threads of the same
> subprocessor and cause privileged-level exceptions. The Directed
> Privileged Doorbell Exception State (DPDES) register reflects the
> state of pending privileged-level doorbell exceptions for all threads
> and can be used to modify that state.
> 
> If the MSGP facility is not in the HFSCR, a hypervisor facility
> unavailable exception is generated when these instructions are used or
> when the DPDES register is accessed by the supervisor.
> 
> Based on previous work from Suraj Jitindar Singh.

Applied to ppc-for-5.0, thanks.

> 
> Thanks,
> 
> C.
> 
> Changes since v1:
> 
>  - removed DBELL_TIRTAG_MASK and simplified helpers as QEMU TCG
>    doesn't support more than on thread per core   
>  - simplified book3s_dbell2irq() and renamed it to dbell_type_server() 
>  - replaced mask LOG_GUEST_ERROR by CPU_LOG_INT to track HV Facility
>    errors
>  
> Cédric Le Goater (2):
>   target/ppc: Add privileged message send facilities
>   target/ppc: add support for Hypervisor Facility Unavailable Exception
> 
>  target/ppc/cpu.h                |  6 +++
>  target/ppc/helper.h             |  4 ++
>  target/ppc/excp_helper.c        | 79 ++++++++++++++++++++++++++-------
>  target/ppc/misc_helper.c        | 63 ++++++++++++++++++++++++++
>  target/ppc/translate.c          | 26 +++++++++++
>  target/ppc/translate_init.inc.c | 20 +++++++--
>  6 files changed, 178 insertions(+), 20 deletions(-)
> 

-- 
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:[~2020-01-21  3:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 10:49 [PATCH v2 0/2] ppc: add support for Directed Privileged Doorbell (non-hypervisor) Cédric Le Goater
2020-01-20 10:49 ` [PATCH v2 1/2] target/ppc: Add privileged message send facilities Cédric Le Goater
2020-01-20 10:49 ` [PATCH v2 2/2] target/ppc: add support for Hypervisor Facility Unavailable Exception Cédric Le Goater
2020-01-21  3:38 ` David Gibson [this message]

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=20200121033800.GA265522@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=groug@kaod.org \
    --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).