From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
David Hildenbrand <david@redhat.com>,
qemu-s390x@nongnu.org, borntraeger@de.ibm.com,
"Jason J. Herne" <jjherne@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3] target/s390x: Remove non-architected entries from struct LowCore
Date: Tue, 5 Mar 2019 10:55:28 +0100 [thread overview]
Message-ID: <20190305105528.60d4e4c3.cohuck@redhat.com> (raw)
In-Reply-To: <1551775581-27989-1-git-send-email-thuth@redhat.com>
On Tue, 5 Mar 2019 09:46:21 +0100
Thomas Huth <thuth@redhat.com> wrote:
> There are some fields in our struct LowCore which apparently have
> been copied from a very old version of the Linux kernel. These
> fields are not architected in the "Principles of Operation", and
> only used on these memory locations in Linux kernels older than
> 2.6.29. Newer Linux kernels moved the entries to different locations
> or are not using them at all anymore. Thus we should never access
> these fields from the QEMU side, so they should be removed.
>
> While we're at it, also add a QEMU_BUILD_BUG_MSG() statement to
s/QEMU_BUILD_BUG_MSG/QEMU_BUILD_BUG_ON/ :)
(fixed up while applying)
> assert that struct LowCore has the right size.
>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v3: Use QEMU_BUILD_BUG_ON instead of QEMU_BUILD_BUG_MSG
>
> target/s390x/internal.h | 41 ++---------------------------------------
> 1 file changed, 2 insertions(+), 39 deletions(-)
Thanks, applied.
next prev parent reply other threads:[~2019-03-05 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 8:46 [Qemu-devel] [PATCH v3] target/s390x: Remove non-architected entries from struct LowCore Thomas Huth
2019-03-05 9:55 ` Cornelia Huck [this message]
2019-03-05 10:28 ` Christian Borntraeger
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=20190305105528.60d4e4c3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.