From: Aditya Gupta <adityag@linux.ibm.com>
To: Caleb Schlossin <calebs@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, npiggin@gmail.com, milesg@linux.ibm.com,
rathc@linux.ibm.com, chalapathi.v@linux.ibm.com
Subject: Re: [PATCH] ppc/pnv: Add dummy MMIO support for OCMB chips
Date: Thu, 1 Jan 2026 12:15:42 +0530 [thread overview]
Message-ID: <41ece6d5-e211-4b32-ab87-d1fe5f359228@linux.ibm.com> (raw)
In-Reply-To: <20251224142249.1356424-1-calebs@linux.ibm.com>
On 24/12/25 19:52, Caleb Schlossin wrote:
> The Power Hypervisor for P10 expects to be able to access certain
> Open CAPI Memory Buffer (OCMB) chip registers. Since QEMU does not
> currently support these registers, several access errors are being
> posted. The hypervisor is able to progress despite these errors,
> but it does create unwanted noise on the console. Adding some
> dummy MMIO support for this IO region in order to suppress the
> error messages.
Hi Caleb,
If there any public document/spec available that documents these
registers ? Can you please point me to it.
I don't find any 'ocmb' mention in any docs here:
https://computeexpresslink.org/resource/opencapi-specification-archive/
Since a new TODO is getting introduced here to implement those register
accesses, it can only be done if some public information is available.
Thanks,
- Aditya G
> Signed-off-by: Glenn Miles <milesg@linux.ibm.com>
> Signed-off-by: Caleb Schlossin <calebs@linux.ibm.com>
> ---
> hw/ppc/meson.build | 1 +
> hw/ppc/pnv.c | 10 ++++
> hw/ppc/pnv_ocmb.c | 103 ++++++++++++++++++++++++++++++++++++++
> include/hw/ppc/pnv.h | 3 ++
> include/hw/ppc/pnv_chip.h | 2 +
> include/hw/ppc/pnv_ocmb.h | 38 ++++++++++++++
> 6 files changed, 157 insertions(+)
> create mode 100644 hw/ppc/pnv_ocmb.c
> create mode 100644 include/hw/ppc/pnv_ocmb.h
>
next prev parent reply other threads:[~2026-01-01 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:22 [PATCH] ppc/pnv: Add dummy MMIO support for OCMB chips Caleb Schlossin
2026-01-01 6:45 ` Aditya Gupta [this message]
2026-01-02 16:01 ` Caleb Schlossin
2026-01-05 9:25 ` Aditya Gupta
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=41ece6d5-e211-4b32-ab87-d1fe5f359228@linux.ibm.com \
--to=adityag@linux.ibm.com \
--cc=calebs@linux.ibm.com \
--cc=chalapathi.v@linux.ibm.com \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.