From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "open list:PowerPC" <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>
Subject: [Qemu-devel] [PATCH qom-cpu v3 11/14] target-ppc: Don't overuse ENV_GET_CPU()
Date: Wed, 26 Jun 2013 19:35:40 +0200 [thread overview]
Message-ID: <1372268143-3894-12-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1372268143-3894-1-git-send-email-afaerber@suse.de>
Commit b632a148b677b773ff155f9de840b37a653567b9 (target-ppc: QOM method
dispatch for MMU fault handling) introduced a use of ENV_GET_CPU()
inside target-ppc/ code. Use ppc_env_get_cpu() instead.
Purely cosmetic, non-functional change to aid in locating and removing
ENV_GET_CPU() usages.
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
target-ppc/mmu_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-ppc/mmu_helper.c b/target-ppc/mmu_helper.c
index 68d5415..53deba5 100644
--- a/target-ppc/mmu_helper.c
+++ b/target-ppc/mmu_helper.c
@@ -2790,7 +2790,7 @@ void helper_booke206_tlbflush(CPUPPCState *env, uint32_t type)
void tlb_fill(CPUPPCState *env, target_ulong addr, int is_write, int mmu_idx,
uintptr_t retaddr)
{
- CPUState *cpu = ENV_GET_CPU(env);
+ CPUState *cpu = CPU(ppc_env_get_cpu(env));
PowerPCCPUClass *pcc = POWERPC_CPU_GET_CLASS(cpu);
int ret;
--
1.8.1.4
next prev parent reply other threads:[~2013-06-26 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 17:35 [Qemu-devel] [PATCH qom-cpu v3 00/14] QOM CPUState, part 10: CPU loops Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 01/14] kvm: Free current_cpu identifier Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 02/14] cpu: Replace cpu_single_env with CPUState current_cpu Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 03/14] kvm: Change kvm_remove_all_breakpoints() argument to CPUState Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 04/14] linux-user: Clean up do_syscall() Coding Style for TARGET_NR_exit Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 05/14] cpu: Make first_cpu and next_cpu CPUState Andreas Färber
2013-07-01 17:37 ` Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 06/14] linux-user: Change thread_env to CPUState Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 07/14] bsd-user: " Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 08/14] intc/arm_gic: Build arm_gic only once Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 09/14] intc/openpic: Build openpic " Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 10/14] timer/arm_mptimer: Build arm_mptimer " Andreas Färber
2013-06-26 17:35 ` Andreas Färber [this message]
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 12/14] target-s390x: Don't overuse ENV_GET_CPU() Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 13/14] target-s390x: Change handle_{hypercall, diag}() argument to S390CPU Andreas Färber
2013-06-26 17:35 ` [Qemu-devel] [PATCH qom-cpu v3 14/14] target-i386: Don't overuse CPUArchState Andreas Färber
2013-07-02 0:31 ` [Qemu-devel] [PATCH qom-cpu v3 00/14] QOM CPUState, part 10: CPU loops Andreas Färber
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=1372268143-3894-12-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--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).