From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
edgar.iglesias@gmail.com
Subject: Re: [Qemu-devel] [PATCH qom v3 4/4] microblaze: boot: Use cpu_set_pc()
Date: Wed, 24 Jun 2015 20:29:23 +0200 [thread overview]
Message-ID: <558AF703.4070609@suse.de> (raw)
In-Reply-To: <558AF04F.30908@suse.de>
Am 24.06.2015 um 20:00 schrieb Andreas Färber:
> Am 24.06.2015 um 05:19 schrieb Peter Crosthwaite:
>> Use cpu_set_pc() for setting program counters when bootloading. This
>> removes an instance of system level code having to reach into the CPU
>> env.
>>
>> Reviewed-by: Andreas Färber <afaerber@suse.de>
>> Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
>> ---
>> changed since v2:
>> Add () to function names in commit messages
>> ---
>> dtc | 2 +-
>> hw/microblaze/boot.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/dtc b/dtc
>> index 65cc4d2..bc895d6 160000
>> --- a/dtc
>> +++ b/dtc
>> @@ -1 +1 @@
>> -Subproject commit 65cc4d2748a2c2e6f27f1cf39e07a5dbabd80ebf
>> +Subproject commit bc895d6d09695d05ceb8b52486ffe861d6cfbdde
>
> Submodule strikes again. Preparing to queue.
Will squash the following deduplication:
diff --git a/hw/microblaze/boot.c b/hw/microblaze/boot.c
index 9f4698a..3e8820f 100644
--- a/hw/microblaze/boot.c
+++ b/hw/microblaze/boot.c
@@ -48,13 +48,14 @@ static struct
static void main_cpu_reset(void *opaque)
{
MicroBlazeCPU *cpu = opaque;
+ CPUState *cs = CPU(cpu);
CPUMBState *env = &cpu->env;
- cpu_reset(CPU(cpu));
+ cpu_reset(cs);
env->regs[5] = boot_info.cmdline;
env->regs[6] = boot_info.initrd_start;
env->regs[7] = boot_info.fdt;
- cpu_set_pc(CPU(cpu), boot_info.bootstrap_pc);
+ cpu_set_pc(cs, boot_info.bootstrap_pc);
if (boot_info.machine_cpu_reset) {
boot_info.machine_cpu_reset(cpu);
}
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-06-24 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 3:19 [Qemu-devel] [PATCH qom v3 0/4] qom-cpu: Wrap set_pc hook and use in bootloaders Peter Crosthwaite
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 1/4] cpu: Add wrapper to the set-pc() hook Peter Crosthwaite
2015-06-24 18:09 ` Andreas Färber
2015-06-24 19:11 ` Peter Maydell
2015-06-25 11:12 ` Andreas Färber
2015-06-25 11:21 ` Peter Maydell
2015-06-25 16:21 ` Andreas Färber
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 2/4] gdbstub: Use cpu_set_pc() helper Peter Crosthwaite
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 3/4] arm: boot: Use cpu_set_pc() Peter Crosthwaite
2015-06-24 18:22 ` Andreas Färber
2015-06-24 18:26 ` Peter Crosthwaite
2015-06-24 19:13 ` Peter Maydell
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 4/4] microblaze: " Peter Crosthwaite
2015-06-24 18:00 ` Andreas Färber
2015-06-24 18:29 ` Andreas Färber [this message]
2015-06-25 2:08 ` Peter Crosthwaite
2015-06-24 18:36 ` [Qemu-devel] [PATCH qom v3 0/4] qom-cpu: Wrap set_pc hook and use in bootloaders 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=558AF703.4070609@suse.de \
--to=afaerber@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).