From: "Cédric Le Goater" <clg@kaod.org>
To: Michael Neuling <mikey@neuling.org>, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, Cameron Kaiser <spectre@floodgap.com>
Subject: Re: [PATCH v2] powerpc: Add force enable of DAWR on P9 option
Date: Mon, 10 Jun 2019 19:31:28 +0200 [thread overview]
Message-ID: <68f4f99d-4bb7-7d25-1e68-96c65dfbfbe9@kaod.org> (raw)
In-Reply-To: <20190401060312.22670-1-mikey@neuling.org>
Hello Michael,
> --- a/arch/powerpc/kvm/book3s_hv_rmhandlers.S
> +++ b/arch/powerpc/kvm/book3s_hv_rmhandlers.S
> @@ -822,18 +822,21 @@ END_FTR_SECTION_IFCLR(CPU_FTR_ARCH_207S)
> mtspr SPRN_IAMR, r5
> mtspr SPRN_PSPB, r6
> mtspr SPRN_FSCR, r7
> - ld r5, VCPU_DAWR(r4)
> - ld r6, VCPU_DAWRX(r4)
> - ld r7, VCPU_CIABR(r4)
> - ld r8, VCPU_TAR(r4)
> /*
> * Handle broken DAWR case by not writing it. This means we
> * can still store the DAWR register for migration.
> */
> -BEGIN_FTR_SECTION
> + LOAD_REG_ADDR(r5, dawr_force_enable)
> + lbz r5, 0(r5)
> + cmpdi r5, 0
> + beq 1f
> + ld r5, VCPU_DAWR(r4)
> + ld r6, VCPU_DAWRX(r4)
> mtspr SPRN_DAWR, r5
> mtspr SPRN_DAWRX, r6
> -END_FTR_SECTION_IFSET(CPU_FTR_DAWR)
> +1:
> + ld r7, VCPU_CIABR(r4)
> + ld r8, VCPU_TAR(r4)
> mtspr SPRN_CIABR, r7
> mtspr SPRN_TAR, r8
> ld r5, VCPU_IC(r4)
> @@ -2513,11 +2516,11 @@ END_FTR_SECTION_IFSET(CPU_FTR_ARCH_207S)
> blr
>
> 2:
> -BEGIN_FTR_SECTION
> - /* POWER9 with disabled DAWR */
> + LOAD_REG_ADDR(r11, dawr_force_enable)
> + lbz r11, 0(r11)
> + cmpdi r11, 0
> li r3, H_HARDWARE
> - blr
> -END_FTR_SECTION_IFCLR(CPU_FTR_DAWR)
> + beqlr
Why is this a 'beqlr' ? Shouldn't it be a blr ?
C.
> /* Emulate H_SET_DABR/X on P8 for the sake of compat mode guests */
> rlwimi r5, r4, 5, DAWRX_DR | DAWRX_DW
> rlwimi r5, r4, 2, DAWRX_WT
>
next prev parent reply other threads:[~2019-06-11 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 6:03 [PATCH v2] powerpc: Add force enable of DAWR on P9 option Michael Neuling
2019-05-03 6:50 ` Michael Ellerman
2019-06-10 17:31 ` Cédric Le Goater [this message]
2019-06-11 6:44 ` Michael Neuling
2019-06-11 6:48 ` Cédric Le Goater
2019-06-11 7:24 ` Michael Neuling
2019-06-11 7:51 ` Christophe Leroy
2019-06-11 9:37 ` Michael Neuling
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=68f4f99d-4bb7-7d25-1e68-96c65dfbfbe9@kaod.org \
--to=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=spectre@floodgap.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).