From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 00/30] My patch queue
Date: Mon, 7 Feb 2022 21:36:13 +0000 [thread overview]
Message-ID: <YgGQzVMdjHfcDGCQ@google.com> (raw)
In-Reply-To: <20220207152847.836777-1-mlevitsk@redhat.com>
On Mon, Feb 07, 2022, Maxim Levitsky wrote:
> This is set of various patches that are stuck in my patch queue.
>
> KVM_REQ_GET_NESTED_STATE_PAGES patch is mostly RFC, but it does seem
> to work for me.
>
> Read-only APIC ID is also somewhat RFC.
>
> Some of these patches are preparation for support for nested AVIC
> which I almost done developing, and will start testing very soon.
Please split this up into smaller series and/or standalone patches. At a glance,
this has 10+ different unrealted series/patches rolled into one, which makes
everything far more difficult to review.
next parent reply other threads:[~2022-02-07 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220207152847.836777-1-mlevitsk@redhat.com>
2022-02-07 21:36 ` Sean Christopherson [this message]
2022-02-08 6:22 ` [PATCH 00/30] My patch queue Maxim Levitsky
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=YgGQzVMdjHfcDGCQ@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=mlevitsk@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