From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Ram Pai <linuxram@us.ibm.com>,
kvm-ppc@vger.kernel.org
Cc: aik@ozlabs.ru, andmike@linux.ibm.com, groug@kaod.org,
clg@fr.ibm.com, sukadev@linux.vnet.ibm.com,
bauerman@linux.ibm.com, david@gibson.dropbear.id.au
Subject: Re: [PATCH v3] powerpc/XIVE: SVM: share the event-queue page with the Hypervisor.
Date: Tue, 9 Jun 2020 15:29:06 +1000 (AEST) [thread overview]
Message-ID: <159168034199.1381411.13122286705469530819.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200426020518.GC5853@oc0525413822.ibm.com>
On Sat, 25 Apr 2020 19:05:18 -0700, Ram Pai wrote:
> >From 10ea2eaf492ca3f22f67a5a63a2b7865e45299ad Mon Sep 17 00:00:00 2001
> From: Ram Pai <linuxram@us.ibm.com>
> Date: Mon, 24 Feb 2020 01:09:48 -0500
> Subject: [PATCH v3] powerpc/XIVE: SVM: share the event-queue page with the
> Hypervisor.
>
> XIVE interrupt controller uses an Event Queue (EQ) to enqueue event
> notifications when an exception occurs. The EQ is a single memory page
> provided by the O/S defining a circular buffer, one per server and
> priority couple.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/xive: Share the event-queue page with the Hypervisor.
https://git.kernel.org/powerpc/c/094235222d41d68d35de18170058d94a96a82628
cheers
prev parent reply other threads:[~2020-06-09 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:38 [PATCH v2] powerpc/XIVE: SVM: share the event-queue page with the Hypervisor Ram Pai
2020-03-26 8:45 ` Cédric Le Goater
2020-03-26 10:04 ` Greg Kurz
2020-03-31 23:53 ` Thiago Jung Bauermann
2020-04-01 5:32 ` Ram Pai
2020-04-03 18:24 ` Thiago Jung Bauermann
2020-04-26 2:05 ` [PATCH v3] " Ram Pai
2020-04-26 7:27 ` Ram Pai
2020-05-27 3:48 ` Michael Ellerman
2020-06-09 5:29 ` Michael Ellerman [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=159168034199.1381411.13122286705469530819.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=andmike@linux.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=clg@fr.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=sukadev@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).