From: Sean Christopherson <seanjc@google.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, david@kernel.org, seiden@linux.ibm.com,
nrb@linux.ibm.com, schlameuss@linux.ibm.com, gra@linux.ibm.com,
pbonzini@redhat.com, yan.y.zhao@intel.com,
isaku.yamahata@intel.com
Subject: Re: [PATCH v2 4/5] KVM: selftests: Fix pre_fault_memory_test to run on s390
Date: Thu, 21 May 2026 06:22:31 -0700 [thread overview]
Message-ID: <ag8HF_49XPdmD7zh@google.com> (raw)
In-Reply-To: <20260521130533.156491-5-imbrenda@linux.ibm.com>
On Thu, May 21, 2026, Claudio Imbrenda wrote:
> Add a missing #include <ucall_common.h> which is needed and otherwise
> not included on s390.
>
> Remove the assertion vcpu->run->exit_reason == KVM_EXIT_IO since it
> is x86-specific and redundant anyway.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
Acked-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2026-05-21 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:05 [PATCH v2 0/5] KVM: s390: Implement KVM_PRE_FAULT_MEMORY Claudio Imbrenda
2026-05-21 13:05 ` [PATCH v2 1/5] KVM: s390: Track page size in struct guest_fault Claudio Imbrenda
2026-05-21 13:05 ` [PATCH v2 2/5] KVM: s390: Implement KVM_PRE_FAULT_MEMORY Claudio Imbrenda
2026-05-21 13:05 ` [PATCH v2 3/5] KVM: s390: Update KVM_PRE_FAULT_MEMORY API documentation Claudio Imbrenda
2026-05-21 13:05 ` [PATCH v2 4/5] KVM: selftests: Fix pre_fault_memory_test to run on s390 Claudio Imbrenda
2026-05-21 13:22 ` Sean Christopherson [this message]
2026-05-21 13:05 ` [PATCH v2 5/5] KVM: selftests: Enable pre_fault_memory_test for s390 Claudio Imbrenda
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=ag8HF_49XPdmD7zh@google.com \
--to=seanjc@google.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=schlameuss@linux.ibm.com \
--cc=seiden@linux.ibm.com \
--cc=yan.y.zhao@intel.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.