From: Thomas Huth <thuth@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: qemu-devel@nongnu.org, Frederic Barrat <fbarrat@linux.ibm.com>,
Alexander Bulekov <alxndr@bu.edu>
Subject: Re: [PATCH] pnv_lpc: disable reentrancy detection for lpc-hc
Date: Fri, 26 May 2023 10:07:09 +0200 [thread overview]
Message-ID: <9b2b8178-5567-a9f3-ade1-a6b2e55ea133@redhat.com> (raw)
In-Reply-To: <20230526073850.2772197-1-clg@kaod.org>
On 26/05/2023 09.38, Cédric Le Goater wrote:
> From: Alexander Bulekov <alxndr@bu.edu>
>
> As lpc-hc is designed for re-entrant calls from xscom, mark it
> re-entrancy safe.
>
> Reported-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> [clg: mark opb_master_regs as re-entrancy safe also ]
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---
> hw/ppc/pnv_lpc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/hw/ppc/pnv_lpc.c b/hw/ppc/pnv_lpc.c
> index 01f44c19ebba..605d3908617a 100644
> --- a/hw/ppc/pnv_lpc.c
> +++ b/hw/ppc/pnv_lpc.c
> @@ -734,10 +734,13 @@ static void pnv_lpc_realize(DeviceState *dev, Error **errp)
> /* Create MMIO regions for LPC HC and OPB registers */
> memory_region_init_io(&lpc->opb_master_regs, OBJECT(dev), &opb_master_ops,
> lpc, "lpc-opb-master", LPC_OPB_REGS_OPB_SIZE);
> + lpc->opb_master_regs.disable_reentrancy_guard = true;
> memory_region_add_subregion(&lpc->opb_mr, LPC_OPB_REGS_OPB_ADDR,
> &lpc->opb_master_regs);
> memory_region_init_io(&lpc->lpc_hc_regs, OBJECT(dev), &lpc_hc_ops, lpc,
> "lpc-hc", LPC_HC_REGS_OPB_SIZE);
> + /* xscom writes to lpc-hc. As such mark lpc-hc re-entrancy safe */
> + lpc->lpc_hc_regs.disable_reentrancy_guard = true;
> memory_region_add_subregion(&lpc->opb_mr, LPC_HC_REGS_OPB_ADDR,
> &lpc->lpc_hc_regs);
>
Tested-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-05-26 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 7:38 [PATCH] pnv_lpc: disable reentrancy detection for lpc-hc Cédric Le Goater
2023-05-26 7:55 ` Frederic Barrat
2023-05-26 8:07 ` Thomas Huth [this message]
2023-05-27 18:01 ` Daniel Henrique Barboza
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 8:53 Alexander Bulekov
2023-05-11 9:04 ` Cédric Le Goater
2023-05-11 9:15 ` Alexander Bulekov
2023-05-11 9:36 ` Cédric Le Goater
2023-05-15 12:48 ` Frederic Barrat
2023-05-26 7:06 ` Thomas Huth
2023-05-26 7:37 ` 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=9b2b8178-5567-a9f3-ade1-a6b2e55ea133@redhat.com \
--to=thuth@redhat.com \
--cc=alxndr@bu.edu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=fbarrat@linux.ibm.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).