From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [GIT PULL for qemu-pseries REPOST] pseries: Update SLOF firmware image
Date: Tue, 13 Aug 2019 13:00:24 +0530 [thread overview]
Message-ID: <3722a768-c8bb-ed04-e450-b18cba8e6296@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190812100849.GF3947@umbus.fritz.box>
On Monday 12 August 2019 03:38 PM, David Gibson wrote:
> On Mon, Aug 05, 2019 at 02:14:39PM +0530, Aravinda Prasad wrote:
>> Alexey/David,
>>
>> With the SLOF changes, QEMU cannot resize the RTAS blob. Resizing is
>> required for FWNMI support which extends the RTAS blob to include an
>> error log upon a machine check.
>>
>> The check to valid RTAS buffer fails in the guest because the rtas-size
>> updated in QEMU is not reflecting in the guest.
>>
>> Any workaround for this?
>
> Well, we should still be able to do it, it just means fwnmi would need
> a SLOF change. It's an inconvenience, but not really a big deal.
Yes. Alexey and I were discussing about the following changes to SLOf:
diff --git a/lib/libhvcall/hvcall.S b/lib/libhvcall/hvcall.S
index b19f6dbeff2c..880d29a29122 100644
--- a/lib/libhvcall/hvcall.S
+++ b/lib/libhvcall/hvcall.S
@@ -134,6 +134,7 @@ ENTRY(hv_rtas)
ori r3,r3,KVMPPC_H_RTAS@l
HVCALL
blr
+ .space 2048
.globl hv_rtas_size
hv_rtas_size:
.long . - hv_rtas;
But this will statically reserve space for RTAS even when
SPAPR_CAP_FWNMI_MCE is OFF.
Regards,
Aravinda
>
>> The following FWNMI work which is under review modifies the rtas-size to
>> accommodate the error log:
>> https://lists.nongnu.org/archive/html/qemu-ppc/2019-06/msg00142.html
>>
>>
>> Regards,
>> Aravinda
>>
>> On Friday 19 July 2019 08:15 AM, Alexey Kardashevskiy wrote:
>>> I messed up with my local git so reposting.
>>>
>>> The following changes since commit 216965b20b04fbf74e0ce3a3175a9171dba210de:
>>>
>>> ppc/pnv: update skiboot to v6.4 (2019-07-18 16:49:57 +1000)
>>>
>>> are available in the Git repository at:
>>>
>>> git@github.com:aik/qemu.git tags/qemu-slof-20190719
>>>
>>> for you to fetch changes up to 300118db53cc454b049d64418c7b2588165a1c35:
>>>
>>> pseries: Update SLOF firmware image (2019-07-19 12:43:27 +1000)
>>>
>>> ----------------------------------------------------------------
>>> Alexey Kardashevskiy (1):
>>> pseries: Update SLOF firmware image
>>>
>>> pc-bios/README | 2 +-
>>> pc-bios/slof.bin | Bin 926432 -> 926784 bytes
>>> roms/SLOF | 2 +-
>>> 3 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>>
>>> *** Note: this is not for master, this is for pseries
>>>
>>
>
--
Regards,
Aravinda
next prev parent reply other threads:[~2019-08-13 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 2:45 [Qemu-devel] [GIT PULL for qemu-pseries REPOST] pseries: Update SLOF firmware image Alexey Kardashevskiy
2019-07-19 3:19 ` David Gibson
2019-08-05 8:44 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad
2019-08-12 10:08 ` David Gibson
2019-08-13 7:30 ` Aravinda Prasad [this message]
2019-08-13 14:17 ` David Gibson
2019-08-14 4:33 ` Aravinda Prasad
2019-08-23 4:09 ` Alexey Kardashevskiy
2019-08-25 1:03 ` David Gibson
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=3722a768-c8bb-ed04-e450-b18cba8e6296@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--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).