From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, seiden@linux.ibm.com, nrb@linux.ibm.com,
scgl@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 0/6] s390x: PV fixups
Date: Fri, 21 Oct 2022 10:41:35 +0200 [thread overview]
Message-ID: <999c3833-d10c-18da-4319-ed150e9c71fa@linux.ibm.com> (raw)
In-Reply-To: <20221021094628.79239c86@p-imbrenda>
On 10/21/22 09:46, Claudio Imbrenda wrote:
> On Fri, 21 Oct 2022 06:38:56 +0000
> Janosch Frank <frankja@linux.ibm.com> wrote:
>
>> A small set of patches that clean up the PV snippet handling.
>>
>> v3:
>> * Dropped asm snippet linker script patch for now
>
> shame, I really liked that patch (modulo the nits)
You'll see it again soonish with another fix series.
There are still a lot of patches that I need to upstream. :)
>
>> * Replaced memalign_pages_flags() with memalign_pages()
>> * PV ASCEs will now recieve DT and TL fields from the main test ASCE
>>
>> v2:
>> * Macro uses 64bit PSW mask
>> * SBLK reset on PV destroy and uv_init() early return have been split off
>>
>>
>> Janosch Frank (6):
>> s390x: snippets: asm: Add a macro to write an exception PSW
>> s390x: MAKEFILE: Use $< instead of pathsubst
>> lib: s390x: sie: Improve validity handling and make it vm specific
>> lib: s390x: Use a new asce for each PV guest
>> lib: s390x: Enable reusability of VMs that were in PV mode
>> lib: s390x: sie: Properly populate SCA
>>
>> lib/s390x/asm-offsets.c | 2 ++
>> lib/s390x/sie.c | 37 +++++++++++++-------
>> lib/s390x/sie.h | 43 ++++++++++++++++++++++--
>> lib/s390x/uv.c | 35 +++++++++++++++++--
>> lib/s390x/uv.h | 5 ++-
>> s390x/Makefile | 2 +-
>> s390x/cpu.S | 6 ++++
>> s390x/snippets/asm/macros.S | 28 +++++++++++++++
>> s390x/snippets/asm/snippet-pv-diag-288.S | 4 +--
>> s390x/snippets/asm/snippet-pv-diag-500.S | 6 ++--
>> 10 files changed, 140 insertions(+), 28 deletions(-)
>> create mode 100644 s390x/snippets/asm/macros.S
>>
>
prev parent reply other threads:[~2022-10-21 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 6:38 [kvm-unit-tests PATCH v3 0/6] s390x: PV fixups Janosch Frank
2022-10-21 6:38 ` [kvm-unit-tests PATCH v3 1/6] s390x: snippets: asm: Add a macro to write an exception PSW Janosch Frank
2022-10-21 6:38 ` [kvm-unit-tests PATCH v3 2/6] s390x: MAKEFILE: Use $< instead of pathsubst Janosch Frank
2022-10-21 6:38 ` [kvm-unit-tests PATCH v3 3/6] lib: s390x: sie: Improve validity handling and make it vm specific Janosch Frank
2022-10-21 6:39 ` [kvm-unit-tests PATCH v3 4/6] lib: s390x: Use a new asce for each PV guest Janosch Frank
2022-10-21 7:03 ` Claudio Imbrenda
2022-10-21 6:39 ` [kvm-unit-tests PATCH v3 5/6] lib: s390x: Enable reusability of VMs that were in PV mode Janosch Frank
2022-10-21 9:40 ` Steffen Eiden
2022-10-21 6:39 ` [kvm-unit-tests PATCH v3 6/6] lib: s390x: sie: Properly populate SCA Janosch Frank
2022-10-21 7:46 ` [kvm-unit-tests PATCH v3 0/6] s390x: PV fixups Claudio Imbrenda
2022-10-21 8:41 ` Janosch Frank [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=999c3833-d10c-18da-4319-ed150e9c71fa@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@linux.ibm.com \
--cc=seiden@linux.ibm.com \
--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