All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Halil Pasic <pasic@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	qemu-devel@nongnu.org
Cc: Eric Farman <farman@linux.ibm.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	qemu-s390x@nongnu.org
Subject: Re: [PATCH] target/s390x/kvm: Simplify the async pfault handling code
Date: Fri, 17 Apr 2026 17:14:05 +0200	[thread overview]
Message-ID: <87zf31ty9u.fsf@redhat.com> (raw)
In-Reply-To: <20260317134531.460141-1-thuth@redhat.com>

On Tue, Mar 17 2026, Thomas Huth <thuth@redhat.com> wrote:

> From: Thomas Huth <thuth@redhat.com>
>
> Since commit 126e7f78036 ("kvm: require KVM_CAP_IOEVENTFD and
> KVM_CAP_IOEVENTFD_ANY_LENGTH") we require at least kernel v4.4 to
> be able to use KVM. KVM_CAP_ASYNC_PF is available in the kernel
> since v3.15 and KVM_SYNC_PFAULT is available since kernel v3.18,
> so we can assume now that they are available in all supported
> kernels. Thus simplify the code a little bit by removing the
> checks for these features.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  I just found this old patch on one of my local branches ... seems like
>  I forgot to send it out after writing it last year...
>
>  target/s390x/kvm/kvm.c | 52 +++++++++---------------------------------
>  1 file changed, 11 insertions(+), 41 deletions(-)

Thanks, queued to s390-next.



      parent reply	other threads:[~2026-04-17 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:45 [PATCH] target/s390x/kvm: Simplify the async pfault handling code Thomas Huth
2026-03-17 14:06 ` Christian Borntraeger
2026-03-17 15:06 ` Matthew Rosato
2026-03-23 17:48 ` Eric Farman
2026-04-17 15:14 ` Cornelia Huck [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=87zf31ty9u.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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 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.