From: "Jason J. Herne" <jjherne@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org, cohuck@redhat.com,
pasic@linux.ibm.com, alifm@linux.ibm.com, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v3 08/16] s390-bios: Map low core memory
Date: Wed, 6 Mar 2019 14:42:03 -0500 [thread overview]
Message-ID: <fc91716f-290c-3531-2a08-76424b4e06bb@linux.ibm.com> (raw)
In-Reply-To: <5d26b514-7d19-9323-c727-696ee5ed4f84@redhat.com>
On 3/5/19 1:27 AM, Thomas Huth wrote:
> On 01/03/2019 19.59, Jason J. Herne wrote:
>> Create a new header for basic architecture specific definitions and add a
>> mapping of low core memory. This mapping will be used by the real dasd boot
>> process.
>>
>> Signed-off-by: Jason J. Herne <jjherne@linux.ibm.com>
>> ---
>> pc-bios/s390-ccw/main.c | 2 +
>> pc-bios/s390-ccw/s390-arch.h | 102 +++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 104 insertions(+)
>> create mode 100644 pc-bios/s390-ccw/s390-arch.h
>>
>> diff --git a/pc-bios/s390-ccw/main.c b/pc-bios/s390-ccw/main.c
>> index 2d912cb..0670c14 100644
>> --- a/pc-bios/s390-ccw/main.c
>> +++ b/pc-bios/s390-ccw/main.c
>> @@ -9,6 +9,7 @@
>> */
>>
>> #include "libc.h"
>> +#include "s390-arch.h"
>> #include "s390-ccw.h"
>> #include "cio.h"
>> #include "virtio.h"
>> @@ -19,6 +20,7 @@ static char loadparm_str[LOADPARM_LEN + 1] = { 0, 0, 0, 0, 0, 0, 0, 0, 0 };
>> QemuIplParameters qipl;
>> IplParameterBlock iplb __attribute__((__aligned__(PAGE_SIZE)));
>> static bool have_iplb;
>> +const LowCore *lowcore; /* Yes, this *is* a pointer to address 0 */
>
> Shouldn't that rather be "LowCore const *lowcore" instead?
>
Yep, will fix this in both places.
...
>> +/* Low core mapping */
>> +typedef struct LowCore {
>> + /* prefix area: defined by architecture */
>> + PSWLegacy ipl_psw; /* 0x000 */
>
> Maybe remove some white space between the variable type and name
> everywhere in this struct?
>
I'd argue to leave this as-is for two reasons. 1) This is how it looks in the original
(target/s390x/internal.h). 2) I prefer the alignment, I think it makes it easier to find
what you're looking for, given the size of this struct.
>> + uint32_t ccw1[2]; /* 0x008 */
>> + uint32_t ccw2[2]; /* 0x010 */
>> + uint8_t pad1[0x80 - 0x18]; /* 0x018 */
>> + uint32_t ext_params; /* 0x080 */
>> + uint16_t cpu_addr; /* 0x084 */
>> + uint16_t ext_int_code; /* 0x086 */
>> + uint16_t svc_ilen; /* 0x088 */
>> + uint16_t svc_code; /* 0x08a */
>> + uint16_t pgm_ilen; /* 0x08c */
>> + uint16_t pgm_code; /* 0x08e */
>> + uint32_t data_exc_code; /* 0x090 */
>> + uint16_t mon_class_num; /* 0x094 */
>> + uint16_t per_perc_atmid; /* 0x096 */
>> + uint64_t per_address; /* 0x098 */
>> + uint8_t exc_access_id; /* 0x0a0 */
>> + uint8_t per_access_id; /* 0x0a1 */
>> + uint8_t op_access_id; /* 0x0a2 */
>> + uint8_t ar_access_id; /* 0x0a3 */
>> + uint8_t pad2[0xA8 - 0xA4]; /* 0x0a4 */
>> + uint64_t trans_exc_code; /* 0x0a8 */
>> + uint64_t monitor_code; /* 0x0b0 */
>> + uint16_t subchannel_id; /* 0x0b8 */
>> + uint16_t subchannel_nr; /* 0x0ba */
>> + uint32_t io_int_parm; /* 0x0bc */
>> + uint32_t io_int_word; /* 0x0c0 */
>> + uint8_t pad3[0xc8 - 0xc4]; /* 0x0c4 */
>> + uint32_t stfl_fac_list; /* 0x0c8 */
>> + uint8_t pad4[0xe8 - 0xcc]; /* 0x0cc */
>> + uint64_t mcic; /* 0x0e8 */
>> + uint8_t pad5[0xf4 - 0xf0]; /* 0x0f0 */
>> + uint32_t external_damage_code; /* 0x0f4 */
>> + uint64_t failing_storage_address; /* 0x0f8 */
>> + uint8_t pad6[0x110 - 0x100]; /* 0x100 */
>> + uint64_t per_breaking_event_addr; /* 0x110 */
>> + uint8_t pad7[0x120 - 0x118]; /* 0x118 */
>> + PSW restart_old_psw; /* 0x120 */
>> + PSW external_old_psw; /* 0x130 */
>> + PSW svc_old_psw; /* 0x140 */
>> + PSW program_old_psw; /* 0x150 */
>> + PSW mcck_old_psw; /* 0x160 */
>> + PSW io_old_psw; /* 0x170 */
>> + uint8_t pad8[0x1a0 - 0x180]; /* 0x180 */
>> + PSW restart_new_psw; /* 0x1a0 */
>> + PSW external_new_psw; /* 0x1b0 */
>> + PSW svc_new_psw; /* 0x1c0 */
>> + PSW program_new_psw; /* 0x1d0 */
>> + PSW mcck_new_psw; /* 0x1e0 */
>> + PSW io_new_psw; /* 0x1f0 */
--
-- Jason J. Herne (jjherne@linux.ibm.com)
next prev parent reply other threads:[~2019-03-06 19:42 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 18:59 [Qemu-devel] [PATCH v3 00/16] s390: vfio-ccw dasd ipl support Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 01/16] s390 vfio-ccw: Add bootindex property and IPLB data Jason J. Herne
2019-03-04 13:40 ` Cornelia Huck
2019-03-06 14:55 ` Jason J. Herne
2019-03-06 15:27 ` Cornelia Huck
2019-03-06 16:28 ` Jason J. Herne
2019-03-06 17:31 ` Cornelia Huck
2019-03-04 16:09 ` Farhan Ali
2019-03-06 15:16 ` Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 02/16] s390-bios: decouple cio setup from virtio Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 03/16] s390-bios: decouple common boot logic " Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 04/16] s390-bios: Extend find_dev() for non-virtio devices Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 05/16] s390-bios: Factor finding boot device out of virtio code path Jason J. Herne
2019-03-04 17:07 ` Cornelia Huck
2019-03-04 19:26 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-03-05 8:38 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 06/16] s390-bios: Clean up cio.h Jason J. Herne
2019-03-04 17:23 ` Cornelia Huck
2019-03-05 5:51 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-03-06 18:42 ` Jason J. Herne
2019-03-07 8:08 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 07/16] s390-bios: Decouple channel i/o logic from virtio Jason J. Herne
2019-03-04 17:28 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 08/16] s390-bios: Map low core memory Jason J. Herne
2019-03-04 17:46 ` Cornelia Huck
2019-03-05 6:27 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-03-06 19:28 ` Jason J. Herne
2019-03-07 8:11 ` Cornelia Huck
2019-03-06 19:42 ` Jason J. Herne [this message]
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 09/16] s390-bios: ptr2u32 and u32toptr Jason J. Herne
2019-03-05 7:22 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-03-07 14:11 ` Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 10/16] s390-bios: Support for running format-0/1 channel programs Jason J. Herne
2019-03-04 18:25 ` Cornelia Huck
2019-03-07 19:25 ` Jason J. Herne
2019-03-08 9:19 ` Cornelia Huck
2019-03-05 7:32 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 11/16] s390-bios: cio error handling Jason J. Herne
2019-03-04 18:35 ` Cornelia Huck
2019-03-07 19:31 ` Jason J. Herne
2019-03-08 9:21 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 12/16] s390-bios: Refactor virtio to run channel programs via cio Jason J. Herne
2019-03-05 12:30 ` Cornelia Huck
2019-03-07 15:09 ` Jason J. Herne
2019-03-07 15:37 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 13/16] s390-bios: Use control unit type to determine boot method Jason J. Herne
2019-03-05 12:27 ` Cornelia Huck
2019-03-07 16:27 ` Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 14/16] s390-bios: Add channel command codes/structs needed for dasd-ipl Jason J. Herne
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 15/16] s390-bios: Support booting from real dasd device Jason J. Herne
2019-03-05 13:03 ` Cornelia Huck
2019-03-01 18:59 ` [Qemu-devel] [PATCH v3 16/16] s390-bios: dasd-ipl: Use control unit type to customize error data Jason J. Herne
2019-03-04 17:02 ` [Qemu-devel] [qemu-s390x] " Eric Farman
2019-03-07 14:38 ` Jason J. Herne
2019-03-07 18:15 ` Eric Farman
2019-03-07 18:26 ` Jason J. Herne
2019-03-04 17:51 ` [Qemu-devel] " Cornelia Huck
2019-03-01 21:26 ` [Qemu-devel] [PATCH v3 00/16] s390: vfio-ccw dasd ipl support no-reply
2019-03-01 21:30 ` no-reply
2019-03-01 21:35 ` no-reply
2019-03-01 21:38 ` no-reply
2019-03-01 21:45 ` no-reply
2019-03-01 21:49 ` no-reply
2019-03-04 16:24 ` Cornelia Huck
2019-03-04 17:53 ` Christian Borntraeger
2019-03-04 17:28 ` no-reply
2019-03-04 17:51 ` no-reply
2019-03-05 5:55 ` no-reply
2019-03-05 7:30 ` no-reply
2019-03-05 8:42 ` no-reply
2019-03-05 13:08 ` no-reply
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=fc91716f-290c-3531-2a08-76424b4e06bb@linux.ibm.com \
--to=jjherne@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).