qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [RFC PATCH 0/4] ppc: Improve multisocket support
Date: Tue, 4 Jul 2023 18:20:48 +0200	[thread overview]
Message-ID: <25be9d1c-08bb-94ff-50e2-8e5e317ef997@linux.ibm.com> (raw)
In-Reply-To: <20230704134921.2626692-1-clg@kaod.org>



On 04/07/2023 15:49, Cédric Le Goater wrote:
> Hello,
> 
> Here are changes improving multisocket support of the XIVE models
> (POWER9 only). When a source has an END target on another chip, the
> XIVE IC will use an MMIO store to forward the notification to the
> remote chip. The long term plan is to get rid of pnv_xive_get_remote()
> whic is a modeling shortcut. I have had them for while, they compile,
> they seem to still work but this is not for merge yet. If someone
> could take over, that would be nice.
> 
> The best way to test is to start a 2 sockets * 1 cpu system with devices
> attached to the PCI buses of chip 0 and to offline CPU 0. All sources
> should be configured to be served by CPU 1 on socket 1 and trigger
> notifications on chip 0 should be forwarded to chip 1.
> 
> Last patch adds support for degenerative interrupts. This is used by
> the lowest level FW of POWER systems. Difficult to test.
> 


Thanks for the series! My crystal ball tells me the PC MMIO patch will 
come handy soon (to be adapted for P10 and groups). And the remote 
routing looks pretty interesting too.
The last patch (LSI) may rot a bit longer though :)

   Fred


> Thanks,
> 
> C.
> 
> Cédric Le Goater (4):
>    ppc/xive: introduce a new XiveRouter end_notify() handler
>    ppc/pnv: handle END triggers between chips with MMIOs
>    ppc/pnv: add support for the PC MMIOs
>    ppc/pnv: Add support for degenerative interrupts (POWER LSI)
> 
>   hw/intc/pnv_xive_regs.h   |   1 +
>   include/hw/ppc/pnv_xive.h |  15 +++
>   include/hw/ppc/xive.h     |   3 +
>   hw/intc/pnv_xive.c        | 262 +++++++++++++++++++++++++++++++-------
>   hw/intc/xive.c            |  50 ++++++--
>   5 files changed, 278 insertions(+), 53 deletions(-)
> 


  parent reply	other threads:[~2023-07-04 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 13:49 [RFC PATCH 0/4] ppc: Improve multisocket support Cédric Le Goater
2023-07-04 13:49 ` [RFC PATCH 1/4] ppc/xive: introduce a new XiveRouter end_notify() handler Cédric Le Goater
2023-07-04 13:49 ` [RFC PATCH 2/4] ppc/pnv: handle END triggers between chips with MMIOs Cédric Le Goater
2023-07-04 13:49 ` [RFC PATCH 3/4] ppc/pnv: add support for the PC MMIOs Cédric Le Goater
2023-07-04 13:49 ` [RFC PATCH 4/4] ppc/pnv: Add support for degenerative interrupts (POWER LSI) Cédric Le Goater
2023-07-04 16:20 ` Frederic Barrat [this message]
2023-07-04 16:57   ` [RFC PATCH 0/4] ppc: Improve multisocket support Cédric Le Goater

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=25be9d1c-08bb-94ff-50e2-8e5e317ef997@linux.ibm.com \
    --to=fbarrat@linux.ibm.com \
    --cc=clg@kaod.org \
    --cc=npiggin@gmail.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).