From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v12 00/13] KVM: Dirty ring interface
Date: Wed, 30 Sep 2020 20:42:18 -0400 [thread overview]
Message-ID: <20201001004218.GA6063@xz-x1> (raw)
In-Reply-To: <20200930214948.47225-1-peterx@redhat.com>
On Wed, Sep 30, 2020 at 05:49:35PM -0400, Peter Xu wrote:
> - rebase
I made the same mistake again on rebasing to 5.9-rc7 rather than kvm/queue.
Doing it again. Sorry for the noise.
--
Peter Xu
prev parent reply other threads:[~2020-10-01 0:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 21:49 [PATCH v12 00/13] KVM: Dirty ring interface Peter Xu
2020-09-30 21:49 ` [PATCH v12 01/13] KVM: Cache as_id in kvm_memory_slot Peter Xu
2020-09-30 21:54 ` [PATCH v12 02/13] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2020-09-30 21:54 ` [PATCH v12 03/13] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2020-09-30 21:54 ` [PATCH v12 04/13] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2020-09-30 21:54 ` [PATCH v12 05/13] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2020-09-30 21:54 ` [PATCH v12 06/13] KVM: Don't allocate dirty bitmap if dirty ring is enabled Peter Xu
2020-09-30 21:54 ` [PATCH v12 07/13] KVM: selftests: Always clear dirty bitmap after iteration Peter Xu
2020-09-30 21:54 ` [PATCH v12 08/13] KVM: selftests: Sync uapi/linux/kvm.h to tools/ Peter Xu
2020-09-30 21:54 ` [PATCH v12 09/13] KVM: selftests: Use a single binary for dirty/clear log test Peter Xu
2020-09-30 21:54 ` [PATCH v12 10/13] KVM: selftests: Introduce after_vcpu_run hook for dirty " Peter Xu
2020-09-30 21:54 ` [PATCH v12 11/13] KVM: selftests: Add dirty ring buffer test Peter Xu
2020-09-30 21:54 ` [PATCH v12 12/13] KVM: selftests: Let dirty_log_test async for dirty ring test Peter Xu
2020-10-04 13:26 ` [KVM] 11e2633982: kernel-selftests.kvm.dirty_log_test.fail kernel test robot
2020-10-07 20:45 ` Peter Xu
2020-09-30 21:54 ` [PATCH v12 13/13] KVM: selftests: Add "-c" parameter to dirty log test Peter Xu
2020-10-01 0:42 ` Peter Xu [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=20201001004218.GA6063@xz-x1 \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@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 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).