From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, edgar.iglesias@gmail.com,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/4] qom: cpu: Add wrapper to the set-pc hook
Date: Mon, 22 Jun 2015 19:27:56 +0200 [thread overview]
Message-ID: <5588459C.9070103@suse.de> (raw)
In-Reply-To: <b55fdcc919bc5e9fd3c97d4f28f8669ed962dd4d.1434432813.git.crosthwaite.peter@gmail.com>
Hi,
Just "cpu: " please, compare git-log.
Am 16.06.2015 um 07:46 schrieb Peter Crosthwaite:
> Add a wrapper around the CPUClass::set_pc hook. Accepts an error
> pointer to report the case where the hook is not set.
>
> Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
> ---
> include/qom/cpu.h | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
> index 7db310e..97d4edf 100644
> --- a/include/qom/cpu.h
> +++ b/include/qom/cpu.h
> @@ -600,6 +600,27 @@ static inline void cpu_unaligned_access(CPUState *cpu, vaddr addr,
> #endif
>
> /**
> + * cpu_set_pc:
> + * @cpu: The CPU to set the program counter for.
> + * @addr: Program counter value.
> + * @errp: Error pointer to populate in case of error.
> + *
> + * Set the program counter for a CPU. If there is no available implementation
> + * an error is raised.
> + */
> +
Please drop the white line here for consistency.
> +static inline void cpu_set_pc(CPUState *cpu, vaddr addr, Error **errp)
> +{
> + CPUClass *cc = CPU_GET_CLASS(cpu);
> +
> + if (cc->set_pc) {
> + cc->set_pc(cpu, addr);
> + } else {
> + error_setg(errp, "CPU does not implement set PC");
> + }
> +}
> +
> +/**
> * cpu_reset_interrupt:
> * @cpu: The CPU to clear the interrupt on.
> * @mask: The interrupt mask to clear.
Otherwise, modulo Peter M.'s comment, looks okay.
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-22 17:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 5:46 [Qemu-devel] [PATCH v2 0/4] qom-cpu: Wrap set_pc hook and use in bootloaders Peter Crosthwaite
2015-06-16 5:46 ` [Qemu-devel] [PATCH v2 1/4] qom: cpu: Add wrapper to the set-pc hook Peter Crosthwaite
2015-06-16 11:29 ` Peter Maydell
2015-06-22 17:27 ` Andreas Färber [this message]
2015-06-16 5:46 ` [Qemu-devel] [PATCH v2 2/4] gdbstub: Use cpu_set_pc helper Peter Crosthwaite
2015-06-22 17:31 ` Andreas Färber
2015-06-24 2:50 ` Peter Crosthwaite
2015-06-24 10:01 ` Peter Maydell
2015-06-24 17:04 ` Peter Crosthwaite
2015-06-24 17:16 ` Andreas Färber
2015-06-24 17:28 ` Peter Crosthwaite
2015-06-24 19:09 ` Peter Maydell
2015-06-16 5:46 ` [Qemu-devel] [PATCH v2 3/4] arm: boot: Use cpu_set_pc Peter Crosthwaite
2015-06-16 11:32 ` Peter Maydell
2015-06-22 17:33 ` Andreas Färber
2015-06-16 5:46 ` [Qemu-devel] [PATCH v2 4/4] microblaze: " Peter Crosthwaite
2015-06-16 11:33 ` Peter Maydell
2015-06-16 15:38 ` Peter Crosthwaite
2015-06-22 17:36 ` 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=5588459C.9070103@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).