From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michael S . Tsirkin" <mst@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Christophe de Dinechin <dinechin@redhat.com>
Subject: Re: [PATCH v2 00/17] KVM: Dirty ring interface
Date: Fri, 20 Dec 2019 13:43:54 -0800 [thread overview]
Message-ID: <20191220214354.GE20453@linux.intel.com> (raw)
In-Reply-To: <20191220213803.GA51391@xz-x1>
On Fri, Dec 20, 2019 at 04:38:03PM -0500, Peter Xu wrote:
> If you see three identical half-posted series which only contains
> patches 00-09... I am very sorry for ruining your inbox... I think my
> mail server is not happy to continue sending the rest of the patches,
> and I'll get this during sending the patch 10:
>
> 4.3.0 Temporary System Problem. Try again later (10). d25sm3385231qtq.11 - gsmtp
>
> So far I don't see what's wrong with patch 10, either.
>
> I'll try to fix it up before I send 4th time (or anyone knows please
> hint me)... Please ignore the previous three in-complete versions.
Please add RESEND in the subject when resending an idential patch (set),
it gives recipients a heads up that the two (or four :-)) sets are the
same, e.g. previous versions can be ignored if he/she received both the
original and RESEND version(s).
[PATCH RESEND v2 00/17] KVM: Dirty ring interface
next prev parent reply other threads:[~2019-12-20 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 21:16 [PATCH v2 00/17] KVM: Dirty ring interface Peter Xu
2019-12-20 21:16 ` [PATCH v2 01/17] KVM: Remove kvm_read_guest_atomic() Peter Xu
2019-12-20 21:16 ` [PATCH v2 02/17] KVM: X86: Change parameter for fast_page_fault tracepoint Peter Xu
2019-12-20 21:16 ` [PATCH v2 03/17] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2019-12-20 21:16 ` [PATCH v2 04/17] KVM: Cache as_id in kvm_memory_slot Peter Xu
2019-12-20 21:16 ` [PATCH v2 05/17] KVM: Add build-time error check on kvm_run size Peter Xu
2019-12-20 21:16 ` [PATCH v2 06/17] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2019-12-20 21:16 ` [PATCH v2 07/17] KVM: Move running VCPU from ARM to common code Peter Xu
2019-12-20 21:16 ` [PATCH v2 08/17] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2019-12-20 21:16 ` [PATCH v2 09/17] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2019-12-20 21:38 ` [PATCH v2 00/17] KVM: Dirty ring interface Peter Xu
2019-12-20 21:43 ` Sean Christopherson [this message]
2019-12-21 2:11 ` Peter Xu
-- strict thread matches above, loose matches on Subject: below --
2019-12-20 21:03 Peter Xu
2019-12-20 21:01 Peter Xu
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=20191220214354.GE20453@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=dgilbert@redhat.com \
--cc=dinechin@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--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 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.