From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org
Subject: Re: [PATCH v4 0/7] s390x/mmu: DAT translation rewrite
Date: Wed, 9 Oct 2019 12:31:12 +0200 [thread overview]
Message-ID: <9d5a3bd5-dfb2-6af3-d114-3075b6e1b199@redhat.com> (raw)
In-Reply-To: <20191004105102.15821-1-david@redhat.com>
On 04.10.19 12:50, David Hildenbrand wrote:
> This is a split-up of:
> [PATCH-for-4.2 v1 3/9] s390x/mmu: DAT translation rewrite
> Rebased on latest upstream changes.
>
> v3 -> v4:
> - "s390x/mmu: Inject PGM_ADDRESSING on bogus table addresses"
> -- s/goguous/bogus/
> - "s390x/mmu: DAT table definition overhaul"
> -- Fix SEGMENT_ENTRY_SFAA
> -- Drop three unnecessary defines
> - "s390x/mmu: Convert to non-recursive page table walk"
> -- Reorder "REGION_ENTRY_P" checks
> -- Drop default cases that cannot be reached
>
> v2 -> v3:
> - "s390x/mmu: Inject PGM_ADDRESSING on boguous table addresses"
> -- Keep using cs->as
> -- Make read_table_entry() return true/false
> - "s390x/mmu: DAT table definition overhaul"
> -- Added a comment where to find details about s390x and used definitions
>
> v1 -> v2:
> - Cleanup old code first, before switching to non-recursive handling
> - Fix EDAT1 translation: I was missing the vaddr offset within the 1MB
> page.
>
> David Hildenbrand (7):
> s390x/mmu: Drop debug logging from MMU code
> s390x/mmu: Move DAT protection handling out of mmu_translate_asce()
> s390x/mmu: Inject DAT exceptions from a single place
> s390x/mmu: Inject PGM_ADDRESSING on bogus table addresses
> s390x/mmu: Use TARGET_PAGE_MASK in mmu_translate_pte()
> s390x/mmu: DAT table definition overhaul
> s390x/mmu: Convert to non-recursive page table walk
>
> target/s390x/cpu.h | 78 +++++---
> target/s390x/mem_helper.c | 12 +-
> target/s390x/mmu_helper.c | 365 ++++++++++++++++----------------------
> 3 files changed, 220 insertions(+), 235 deletions(-)
>
I'll queue and send this soon.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-10-09 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 10:50 [PATCH v4 0/7] s390x/mmu: DAT translation rewrite David Hildenbrand
2019-10-04 10:50 ` [PATCH v4 1/7] s390x/mmu: Drop debug logging from MMU code David Hildenbrand
2019-10-04 10:50 ` [PATCH v4 2/7] s390x/mmu: Move DAT protection handling out of mmu_translate_asce() David Hildenbrand
2019-10-04 10:50 ` [PATCH v4 3/7] s390x/mmu: Inject DAT exceptions from a single place David Hildenbrand
2019-10-04 10:50 ` [PATCH v4 4/7] s390x/mmu: Inject PGM_ADDRESSING on bogus table addresses David Hildenbrand
2019-10-04 10:51 ` [PATCH v4 5/7] s390x/mmu: Use TARGET_PAGE_MASK in mmu_translate_pte() David Hildenbrand
2019-10-04 10:51 ` [PATCH v4 6/7] s390x/mmu: DAT table definition overhaul David Hildenbrand
2019-10-08 14:20 ` Thomas Huth
2019-10-09 10:45 ` Cornelia Huck
2019-10-09 10:47 ` David Hildenbrand
2019-10-04 10:51 ` [PATCH v4 7/7] s390x/mmu: Convert to non-recursive page table walk David Hildenbrand
2019-10-08 14:24 ` Thomas Huth
2019-10-09 10:31 ` David Hildenbrand [this message]
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=9d5a3bd5-dfb2-6af3-d114-3075b6e1b199@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).