From: Alexander Graf <agraf@suse.de>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 3/4] spapr: Fix RTAS sysparm DIAGNOSTICS_RUN_MODE
Date: Tue, 24 Jun 2014 14:02:51 +0200 [thread overview]
Message-ID: <53A968EB.7030003@suse.de> (raw)
In-Reply-To: <53A967F9.1050004@suse.de>
On 24.06.14 13:58, Alexander Graf wrote:
>
> On 24.06.14 02:22, Sam Bobroff wrote:
>> This allows the ibm,get-system-parameter RTAS call to succeed for the
>> DIAGNOSTICS_RUN_MODE system parameter.
>>
>> The problem can be seen with "ppc64_cpu --run-mode" from the
>> powerpc-utils package which fails before this patch with "Machine does
>> not support diagnostic run mode".
>>
>> This is corrected by using the rtas_st_buffer() function to write to
>> the buffer.
>>
>> The function return value code is also slightly simplified.
>>
>> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
>> ---
>> hw/ppc/spapr_rtas.c | 11 +++++------
>> 1 file changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
>> index 4f87673..8d94845 100644
>> --- a/hw/ppc/spapr_rtas.c
>> +++ b/hw/ppc/spapr_rtas.c
>> @@ -236,19 +236,18 @@ static void
>> rtas_ibm_get_system_parameter(PowerPCCPU *cpu,
>> target_ulong parameter = rtas_ld(args, 0);
>> target_ulong buffer = rtas_ld(args, 1);
>> target_ulong length = rtas_ld(args, 2);
>> - target_ulong ret = RTAS_OUT_NOT_SUPPORTED;
>> + target_ulong ret = RTAS_OUT_SUCCESS;
>> + uint8_t zero = 0;
>> switch (parameter) {
>> case DIAGNOSTICS_RUN_MODE:
>> - if (length == 1) {
>> - rtas_st(buffer, 0, 0);
>> - ret = RTAS_OUT_SUCCESS;
>> - }
>> + rtas_st_buffer(buffer, length, &zero, sizeof zero);
>
> Please use sizeof(zero) here :).
Also while at it, please make the code slightly more readable. We don't
pass in "zero", we pass in DIAGNOSTICS_RUN_MODE_DISABLED, no? Please
define the possible values in a header file and set it accordingly here.
Since it's limited to DIAGNOSTICS_RUN_MODE, please also make the
variable limited to that scope then.
Alex
next prev parent reply other threads:[~2014-06-24 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1403569210.git.sam.bobroff@au1.ibm.com>
2014-06-24 0:22 ` [Qemu-devel] [PATCH 1/4] spapr: Add rtas_st_buffer utility function Sam Bobroff
2014-06-24 11:51 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-06-24 0:22 ` [Qemu-devel] [PATCH 2/4] spapr: Add RTAS sysparm UUID Sam Bobroff
2014-06-24 0:22 ` [Qemu-devel] [PATCH 3/4] spapr: Fix RTAS sysparm DIAGNOSTICS_RUN_MODE Sam Bobroff
2014-06-24 11:58 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-06-24 12:02 ` Alexander Graf [this message]
2014-06-24 0:22 ` [Qemu-devel] [PATCH 4/4] spapr: Add RTAS sysparm SPLPAR Characteristics Sam Bobroff
2014-06-24 12:03 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
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=53A968EB.7030003@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.bobroff@au1.ibm.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).