From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, thuth@redhat.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RFC 0/3] s390x/tcg: LAP support using immediate TLB invalidation
Date: Fri, 29 Sep 2017 13:49:38 +0200 [thread overview]
Message-ID: <20170929134938.18fae231.cohuck@redhat.com> (raw)
In-Reply-To: <20170927170027.8539-1-david@redhat.com>
On Wed, 27 Sep 2017 19:00:24 +0200
David Hildenbrand <david@redhat.com> wrote:
> Details about Low-Address Protection can be found in description of
> patch 1 and 2. It is basically a subpage protection of the first two
> pages of every address space (for which it is enabled).
>
> We can achieve this by simply directly invalidating the TLB entry and
> therefore forcing every write accesses onto these two pages into the slow
> path.
>
> With this patch, I can boot Linux just fine (which uses LAP). This also
> makes all related kvm-unit-tests that we have pass.
>
> The checks are working that good, that I discovered a STFL bug. STFL
> stores into the low addresses but low-address protection does explicitly
> not apply. The Linux kernel calls STFL while LAP is active. So without
> patch nr 3, booting Linux will fail. (this change is also part of a patch
> of my SMP series).
I fear I have lost track a bit with all those patches floating around.
IIUC, patch 3 fixes a real bug that is only exposed by your LAP
changes. It used to be part of the stfl changes in v1 of your smp
series but is no longer in v2. So, is this a patch that can be applied
to current s390-next?
>
> Based on: https://github.com/cohuck/qemu.git s390-next
> Available on: https://github.com/dhildenb/qemu.git s390x_lap
>
>
> David Hildenbrand (3):
> accel/tcg: allow to invalidate a write TLB entry immediately
> s390x/tcg: low-address protection support
> s390x/tcg: make STFL store into the lowcore
>
> accel/tcg/cputlb.c | 5 ++-
> accel/tcg/softmmu_template.h | 4 +-
> include/exec/cpu-all.h | 3 ++
> target/s390x/excp_helper.c | 3 +-
> target/s390x/helper.h | 2 +-
> target/s390x/mem_helper.c | 8 ----
> target/s390x/misc_helper.c | 7 +++-
> target/s390x/mmu_helper.c | 96 ++++++++++++++++++++++++++++----------------
> 8 files changed, 78 insertions(+), 50 deletions(-)
>
next prev parent reply other threads:[~2017-09-29 11:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 17:00 [Qemu-devel] [PATCH RFC 0/3] s390x/tcg: LAP support using immediate TLB invalidation David Hildenbrand
2017-09-27 17:00 ` [Qemu-devel] [PATCH RFC 1/3] accel/tcg: allow to invalidate a write TLB entry immediately David Hildenbrand
2017-09-27 17:48 ` Richard Henderson
2017-09-27 18:50 ` David Hildenbrand
2017-10-16 7:24 ` David Hildenbrand
2017-10-16 18:06 ` Richard Henderson
2017-09-27 17:00 ` [Qemu-devel] [PATCH RFC 2/3] s390x/tcg: low-address protection support David Hildenbrand
2017-09-27 17:51 ` Richard Henderson
2017-09-28 4:50 ` Thomas Huth
2017-09-28 13:08 ` David Hildenbrand
2017-09-29 11:27 ` Cornelia Huck
2017-10-12 8:41 ` Thomas Huth
2017-10-16 7:20 ` David Hildenbrand
2017-09-27 17:00 ` [Qemu-devel] [PATCH RFC 3/3] s390x/tcg: make STFL store into the lowcore David Hildenbrand
2017-09-27 17:52 ` Richard Henderson
2017-09-27 18:46 ` David Hildenbrand
2017-09-28 4:23 ` Thomas Huth
2017-09-29 12:43 ` Cornelia Huck
2017-09-29 11:49 ` Cornelia Huck [this message]
2017-09-29 12:09 ` [Qemu-devel] [PATCH RFC 0/3] s390x/tcg: LAP support using immediate TLB invalidation David Hildenbrand
2017-09-29 12:13 ` Cornelia Huck
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=20170929134938.18fae231.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).