From: Eduardo Habkost <ehabkost@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/2] i386: Fix interrupt based Async PF enablement
Date: Tue, 20 Apr 2021 13:35:41 -0400 [thread overview]
Message-ID: <20210420173541.24kxarhw75h2rqxa@habkost.net> (raw)
In-Reply-To: <YHiQlkIOHDClFfXS@work-vm>
On Thu, Apr 15, 2021 at 08:14:30PM +0100, Dr. David Alan Gilbert wrote:
> * Paolo Bonzini (pbonzini@redhat.com) wrote:
> > On 06/04/21 13:42, Vitaly Kuznetsov wrote:
> > > older machine types are still available (I disable it for <= 5.1 but we
> > > can consider disabling it for 5.2 too). The feature is upstream since
> > > Linux 5.8, I know that QEMU supports much older kernels but this doesn't
> > > probably mean that we can't enable new KVM PV features unless all
> > > supported kernels have it, we'd have to wait many years otherwise.
> >
> > Yes, this is a known problem in fact. :( In 6.0 we even support RHEL 7,
> > though that will go away in 6.1.
> >
> > We should take the occasion of dropping RHEL7 to be clearer about which
> > kernels are supported.
>
> It would be nice to be able to define sets of KVM functonality that we
> can either start given machine types with, or provide a separate switch
> to limit kvm functionality back to some defined point. We do trip over
> the same things pretty regularly when accidentally turning on new
> features.
The same idea can apply to the hyperv=on stuff Vitaly is working
on. Maybe we should consider making a generic version of the
s390x FeatGroup code, use it to define convenient sets of KVM and
hyperv features.
--
Eduardo
next prev parent reply other threads:[~2021-04-20 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 15:19 [PATCH 0/2] i386: Fix interrupt based Async PF enablement Vitaly Kuznetsov
2021-04-01 15:19 ` [PATCH 1/2] i386: Add 'kvm-asyncpf-int' to kvm_default_props array Vitaly Kuznetsov
2021-04-01 15:19 ` [PATCH 2/2] i386: Disable 'kvm-asyncpf-int' feature for machine types <= 5.1 Vitaly Kuznetsov
2021-04-01 15:57 ` [PATCH 0/2] i386: Fix interrupt based Async PF enablement Paolo Bonzini
2021-04-06 11:42 ` Vitaly Kuznetsov
2021-04-08 12:46 ` Paolo Bonzini
2021-04-15 19:14 ` Dr. David Alan Gilbert
2021-04-20 17:35 ` Eduardo Habkost [this message]
2021-04-21 8:38 ` Vitaly Kuznetsov
2021-04-21 8:50 ` Daniel P. Berrangé
2021-04-21 9:23 ` Dr. David Alan Gilbert
2021-04-21 9:29 ` Vitaly Kuznetsov
2021-04-21 9:34 ` Dr. David Alan Gilbert
2021-04-21 9:37 ` Daniel P. Berrangé
2021-04-21 9:48 ` Vitaly Kuznetsov
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=20210420173541.24kxarhw75h2rqxa@habkost.net \
--to=ehabkost@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vkuznets@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).