mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] KVM: s390: use defines for execution controls
Date: Tue, 14 Mar 2017 14:51:50 +0100	[thread overview]
Message-ID: <5ec9b559-40c5-8f64-c2e8-dc8cabd478d4@de.ibm.com> (raw)
In-Reply-To: <20170313104828.13362-1-david@redhat.com>

On 03/13/2017 11:48 AM, David Hildenbrand wrote:
> Let's replace the bitmasks by defines. Reconstructed from code, comments
> and commit messages.
> 
> Tried to keep the defines short and map them to feature names. In case
> they don't completely map to features, keep them in the stye of ICTL
> defines.
> 
> This effectively drops all "U" from the existing numbers. I think this
> should be fine (as similarly done for e.g. ICTL defines).

The patch does change the binary result and this seems to be related to the
U removal. But as far as I can tell this is fine, its just some subtle 
undefined behaviour change between unsigned/signed which we do not care
about.


> 
> I am not 100% sure about the ECA_MVPGI and ECA_PROTEXCI bits as they are
> always used in pairs.

Just historic baggage, e.g. in 3.10 we set eca to 0xC1002001 and over
time we split those out piece by piece. Those two are just the last men 
standing.

I think I am going to apply this with some minor changes (EC* names). Ok
when I do the changes?

  reply	other threads:[~2017-03-14 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 10:48 David Hildenbrand
2017-03-14 13:51 ` Christian Borntraeger [this message]
2017-03-14 13:54   ` David Hildenbrand

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=5ec9b559-40c5-8f64-c2e8-dc8cabd478d4@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®