From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "James Hogan" <jhogan@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Marc Zyngier" <maz@kernel.org>,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Wanpeng Li" <wanpengli@tencent.com>,
"Jim Mattson" <jmattson@google.com>,
"Joerg Roedel" <joro@8bytes.org>,
"James Morse" <james.morse@arm.com>,
"Julien Thierry" <julien.thierry.kdev@gmail.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
"Christoffer Dall" <christoffer.dall@arm.com>
Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays
Date: Tue, 17 Dec 2019 09:55:08 -0800 [thread overview]
Message-ID: <20191217175507.GA8052@linux.intel.com> (raw)
In-Reply-To: <ca928a38-4bc0-88cd-dc70-62aec8695c77@de.ibm.com>
On Mon, Dec 16, 2019 at 09:25:24AM +0100, Christian Borntraeger wrote:
>
> On 13.12.19 21:01, Sean Christopherson wrote:
> > Applies cleanly on the current kvm/queue and nothing caught fire in
> > testing (though I only re-tested the series as a whole).
>
> Do you have the latest version somewhere on a branch? The version on the
> list no longer applies cleanly.
Ah, I only tested with my sparse x86-only tree. The result with three-way
merging, i.e. 'git am -3', looks correct at a glance.
Regardless, I need to spin a new version to handle a conflict with an
unrelated in-flight memslots bug fix, I'll get that sent out today.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Wanpeng Li <wanpengli@tencent.com>,
kvm@vger.kernel.org, James Hogan <jhogan@kernel.org>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@ozlabs.org>,
kvmarm@lists.cs.columbia.edu,
Janosch Frank <frankja@linux.ibm.com>,
Marc Zyngier <maz@kernel.org>, Joerg Roedel <joro@8bytes.org>,
David Hildenbrand <david@redhat.com>,
kvm-ppc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Jim Mattson <jmattson@google.com>,
Cornelia Huck <cohuck@redhat.com>,
linux-mips@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays
Date: Tue, 17 Dec 2019 09:55:08 -0800 [thread overview]
Message-ID: <20191217175507.GA8052@linux.intel.com> (raw)
In-Reply-To: <ca928a38-4bc0-88cd-dc70-62aec8695c77@de.ibm.com>
On Mon, Dec 16, 2019 at 09:25:24AM +0100, Christian Borntraeger wrote:
>
> On 13.12.19 21:01, Sean Christopherson wrote:
> > Applies cleanly on the current kvm/queue and nothing caught fire in
> > testing (though I only re-tested the series as a whole).
>
> Do you have the latest version somewhere on a branch? The version on the
> list no longer applies cleanly.
Ah, I only tested with my sparse x86-only tree. The result with three-way
merging, i.e. 'git am -3', looks correct at a glance.
Regardless, I need to spin a new version to handle a conflict with an
unrelated in-flight memslots bug fix, I'll get that sent out today.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Wanpeng Li" <wanpengli@tencent.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"James Hogan" <jhogan@kernel.org>,
linux-kernel@vger.kernel.org,
"Paul Mackerras" <paulus@ozlabs.org>,
kvmarm@lists.cs.columbia.edu,
"Janosch Frank" <frankja@linux.ibm.com>,
"Marc Zyngier" <maz@kernel.org>, "Joerg Roedel" <joro@8bytes.org>,
"David Hildenbrand" <david@redhat.com>,
"Julien Thierry" <julien.thierry.kdev@gmail.com>,
"Christoffer Dall" <christoffer.dall@arm.com>,
kvm-ppc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Jim Mattson" <jmattson@google.com>,
"Cornelia Huck" <cohuck@redhat.com>,
linux-mips@vger.kernel.org, "James Morse" <james.morse@arm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>
Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays
Date: Tue, 17 Dec 2019 09:55:08 -0800 [thread overview]
Message-ID: <20191217175507.GA8052@linux.intel.com> (raw)
In-Reply-To: <ca928a38-4bc0-88cd-dc70-62aec8695c77@de.ibm.com>
On Mon, Dec 16, 2019 at 09:25:24AM +0100, Christian Borntraeger wrote:
>
> On 13.12.19 21:01, Sean Christopherson wrote:
> > Applies cleanly on the current kvm/queue and nothing caught fire in
> > testing (though I only re-tested the series as a whole).
>
> Do you have the latest version somewhere on a branch? The version on the
> list no longer applies cleanly.
Ah, I only tested with my sparse x86-only tree. The result with three-way
merging, i.e. 'git am -3', looks correct at a glance.
Regardless, I need to spin a new version to handle a conflict with an
unrelated in-flight memslots bug fix, I'll get that sent out today.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "James Hogan" <jhogan@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Marc Zyngier" <maz@kernel.org>,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Wanpeng Li" <wanpengli@tencent.com>,
"Jim Mattson" <jmattson@google.com>,
"Joerg Roedel" <joro@8bytes.org>,
"James Morse" <james.morse@arm.com>,
"Julien Thierry" <julien.thierry.kdev@gmail.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
"Christoffer Dall" <christoffer.dall@arm.com>
Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays
Date: Tue, 17 Dec 2019 17:55:08 +0000 [thread overview]
Message-ID: <20191217175507.GA8052@linux.intel.com> (raw)
In-Reply-To: <ca928a38-4bc0-88cd-dc70-62aec8695c77@de.ibm.com>
On Mon, Dec 16, 2019 at 09:25:24AM +0100, Christian Borntraeger wrote:
>
> On 13.12.19 21:01, Sean Christopherson wrote:
> > Applies cleanly on the current kvm/queue and nothing caught fire in
> > testing (though I only re-tested the series as a whole).
>
> Do you have the latest version somewhere on a branch? The version on the
> list no longer applies cleanly.
Ah, I only tested with my sparse x86-only tree. The result with three-way
merging, i.e. 'git am -3', looks correct at a glance.
Regardless, I need to spin a new version to handle a conflict with an
unrelated in-flight memslots bug fix, I'll get that sent out today.
next prev parent reply other threads:[~2019-12-17 17:55 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 23:07 [PATCH v3 00/15] KVM: Dynamically size memslot arrays Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 01/15] KVM: Reinstall old memslots if arch preparation fails Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 02/15] KVM: Don't free new memslot if allocation of said memslot fails Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 03/15] KVM: PPC: Move memslot memory allocation into prepare_memory_region() Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 04/15] KVM: x86: Allocate memslot resources during prepare_memory_region() Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 05/15] KVM: Drop kvm_arch_create_memslot() Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-12-16 8:04 ` Christian Borntraeger
2019-12-16 8:04 ` Christian Borntraeger
2019-12-16 8:04 ` Christian Borntraeger
2019-12-16 8:04 ` Christian Borntraeger
2019-10-24 23:07 ` [PATCH v3 06/15] KVM: Explicitly free allocated-but-unused dirty bitmap Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 07/15] KVM: Refactor error handling for setting memory region Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-12-05 9:49 ` Philippe Mathieu-Daudé
2019-12-05 9:49 ` Philippe Mathieu-Daudé
2019-12-05 9:49 ` Philippe Mathieu-Daudé
2019-12-05 9:49 ` Philippe Mathieu-Daudé
2019-10-24 23:07 ` [PATCH v3 08/15] KVM: Move setting of memslot into helper routine Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-12-05 9:54 ` Philippe Mathieu-Daudé
2019-12-05 9:54 ` Philippe Mathieu-Daudé
2019-12-05 9:54 ` Philippe Mathieu-Daudé
2019-12-05 9:54 ` Philippe Mathieu-Daudé
2019-10-24 23:07 ` [PATCH v3 09/15] KVM: Move memslot deletion to helper function Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 10/15] KVM: Simplify kvm_free_memslot() and all its descendents Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 11/15] KVM: Clean up local variable usage in __kvm_set_memory_region() Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 12/15] KVM: Provide common implementation for generic dirty log functions Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 13/15] KVM: Ensure validity of memslot with respect to kvm_get_dirty_log() Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 14/15] KVM: Terminate memslot walks via used_slots Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` [PATCH v3 15/15] KVM: Dynamically size memslot array based on number of used slots Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-24 23:07 ` Sean Christopherson
2019-10-25 13:28 ` [PATCH v3 00/15] KVM: Dynamically size memslot arrays Christoffer Dall
2019-10-25 13:28 ` Christoffer Dall
2019-10-25 13:28 ` Christoffer Dall
2019-10-25 13:28 ` Christoffer Dall
2019-10-25 16:30 ` Marc Zyngier
2019-10-25 16:30 ` Marc Zyngier
2019-10-25 16:30 ` Marc Zyngier
2019-10-25 16:30 ` Marc Zyngier
2019-12-03 22:14 ` Sean Christopherson
2019-12-03 22:14 ` Sean Christopherson
2019-12-03 22:14 ` Sean Christopherson
2019-12-03 22:14 ` Sean Christopherson
2019-12-13 20:01 ` Sean Christopherson
2019-12-13 20:01 ` Sean Christopherson
2019-12-13 20:01 ` Sean Christopherson
2019-12-13 20:01 ` Sean Christopherson
2019-12-16 8:25 ` Christian Borntraeger
2019-12-16 8:25 ` Christian Borntraeger
2019-12-16 8:25 ` Christian Borntraeger
2019-12-16 8:25 ` Christian Borntraeger
2019-12-17 17:55 ` Sean Christopherson [this message]
2019-12-17 17:55 ` Sean Christopherson
2019-12-17 17:55 ` Sean Christopherson
2019-12-17 17:55 ` Sean Christopherson
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=20191217175507.GA8052@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@arm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=james.morse@arm.com \
--cc=jhogan@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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.