From: Pierre Morel <pmorel@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com
Subject: Re: [PATCH v1 2/4] s390x: Define the PSW bits
Date: Thu, 14 Nov 2019 16:25:29 +0100 [thread overview]
Message-ID: <33163b34-247d-71b2-54a3-8a6b476b7157@linux.ibm.com> (raw)
In-Reply-To: <e27023c2-5f9c-884d-e194-4420ec6e3023@linux.ibm.com>
On 2019-11-14 09:53, Janosch Frank wrote:
> On 11/14/19 9:40 AM, Pierre Morel wrote:
>> On 2019-11-13 17:05, Janosch Frank wrote:
>>> On 11/13/19 1:23 PM, Pierre Morel wrote:
>>>> Instead of assigning obfuscated masks to the PSW dedicated to the
>>>> exceptions, let's define the masks explicitely, it will clarify the
>>> s/explicitely/explicitly/
>>> Try to break that up into sentences.
>> OK thx
...snip...
>>>> +
>>>> +#define PSW_EXCEPTION_MASK (PSW_MASK_EA|PSW_MASK_BA)
>>> That's not a bit anymore, shouldn't that be in arch_def.h?
>>> Also please add a comment, that this is 64 bit addressing.
>>
>> Don't we use the 64bit architecture only?
> architecture != addressing
> We can do 24 bit addressing on zArch...
> We mostly use ESAME (zArch), but old machines start up in the old mode
> and then we transition to zArch via a SIGP.
Yes, this is done during the first instructions of cstart.S:
- Setting the architecture to 64bit / ESAME using SIGP
- Set addressing mode to 64bit
After that AFAIK we never change the addressing mode.
The definitions in the file are intended for PSW flags which AFAIK are
always 64bits.
I created arch_bits.h to avoid using arch_def.h which contains C
structures and functions, so preventing to include it in assembler files.
Regards,
Pierre
>
>> Regards,
>>
>> Pierre
>>
>>
>
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2019-11-14 15:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:23 [PATCH v1 0/4] s390x: Testing the Subchannel I/O Pierre Morel
2019-11-13 12:23 ` [PATCH v1 1/4] s390x: saving regs for interrupts Pierre Morel
2019-11-13 16:12 ` Janosch Frank
2019-11-14 10:11 ` Pierre Morel
2019-11-14 10:28 ` David Hildenbrand
2019-11-14 11:57 ` Pierre Morel
2019-11-14 12:11 ` David Hildenbrand
2019-11-14 15:21 ` Pierre Morel
2019-11-14 15:25 ` David Hildenbrand
2019-11-14 16:15 ` Pierre Morel
2019-11-13 12:23 ` [PATCH v1 2/4] s390x: Define the PSW bits Pierre Morel
2019-11-13 16:05 ` Janosch Frank
2019-11-14 8:40 ` Pierre Morel
2019-11-14 8:53 ` Janosch Frank
2019-11-14 15:25 ` Pierre Morel [this message]
2019-11-13 12:23 ` [PATCH v1 3/4] s390x:irq: make IRQ handler weak Pierre Morel
2019-11-15 7:12 ` Thomas Huth
2019-11-18 9:04 ` Pierre Morel
2019-11-13 12:23 ` [PATCH v1 4/4] s390x: Testing the Subchannel I/O read Pierre Morel
2019-11-13 13:05 ` Cornelia Huck
2019-11-14 10:11 ` Pierre Morel
2019-11-21 16:02 ` Cornelia Huck
2019-11-22 9:03 ` Pierre Morel
2019-11-22 10:54 ` Cornelia Huck
2019-11-22 12:48 ` Pierre Morel
2019-11-14 9:15 ` Janosch Frank
2019-11-14 16:38 ` Pierre Morel
2019-11-14 16:51 ` Thomas Huth
2019-11-14 17:50 ` Pierre Morel
2019-11-14 17:09 ` Janosch Frank
2019-11-14 17:55 ` Pierre Morel
2019-11-13 12:35 ` [PATCH v1 0/4] s390x: Testing the Subchannel I/O Thomas Huth
2019-11-13 12:43 ` Pierre Morel
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=33163b34-247d-71b2-54a3-8a6b476b7157@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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