From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "James Hogan" <jhogan@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.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
Subject: Re: [PATCH v2 14/15] KVM: Terminate memslot walks via used_slots
Date: Thu, 24 Oct 2019 12:42:14 -0700 [thread overview]
Message-ID: <20191024194214.GB28043@linux.intel.com> (raw)
In-Reply-To: <20191024193856.GA28043@linux.intel.com>
On Thu, Oct 24, 2019 at 12:38:56PM -0700, Sean Christopherson wrote:
> On Tue, Oct 22, 2019 at 05:53:27PM +0200, Paolo Bonzini wrote:
> > On 22/10/19 17:52, Sean Christopherson wrote:
> > >
> > > Anyways, I'm not at all opposed to adding comments, just want to make sure
> > > I'm not forgetting something. If it's ok with you, I'll comment the code
> > > and/or functions and reply here to refine them without having to respin
> > > the whole series.
> >
> > Yes, I agree this is better.
>
> Here's what I ended up with. I also added kvm_memslot_insert_back() to
> help document the purpose of incrementing used_slots, and renamed
> kvm_shift_memslots_forward()->kvm_memslot_move_backward() and
> kvm_shift_memslots_backward()->kvm_memslot_move_forward() because I was
> having trouble reconciling having the comments focus on the changed
> memslot while the names of the functions reflected what happens to the
> other memslots.
Oh, and I need to respin the series to fix build bugs on MIPS and PPC,
I'll wait to do that until I get a thumbs up on this code.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org, James Hogan <jhogan@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
David Hildenbrand <david@redhat.com>,
linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@ozlabs.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
kvmarm@lists.cs.columbia.edu, Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH v2 14/15] KVM: Terminate memslot walks via used_slots
Date: Thu, 24 Oct 2019 12:42:14 -0700 [thread overview]
Message-ID: <20191024194214.GB28043@linux.intel.com> (raw)
In-Reply-To: <20191024193856.GA28043@linux.intel.com>
On Thu, Oct 24, 2019 at 12:38:56PM -0700, Sean Christopherson wrote:
> On Tue, Oct 22, 2019 at 05:53:27PM +0200, Paolo Bonzini wrote:
> > On 22/10/19 17:52, Sean Christopherson wrote:
> > >
> > > Anyways, I'm not at all opposed to adding comments, just want to make sure
> > > I'm not forgetting something. If it's ok with you, I'll comment the code
> > > and/or functions and reply here to refine them without having to respin
> > > the whole series.
> >
> > Yes, I agree this is better.
>
> Here's what I ended up with. I also added kvm_memslot_insert_back() to
> help document the purpose of incrementing used_slots, and renamed
> kvm_shift_memslots_forward()->kvm_memslot_move_backward() and
> kvm_shift_memslots_backward()->kvm_memslot_move_forward() because I was
> having trouble reconciling having the comments focus on the changed
> memslot while the names of the functions reflected what happens to the
> other memslots.
Oh, and I need to respin the series to fix build bugs on MIPS and PPC,
I'll wait to do that until I get a thumbs up on this code.
_______________________________________________
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Cornelia Huck" <cohuck@redhat.com>,
"Wanpeng Li" <wanpengli@tencent.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"James Hogan" <jhogan@kernel.org>,
"Joerg Roedel" <joro@8bytes.org>,
"David Hildenbrand" <david@redhat.com>,
linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Paul Mackerras" <paulus@ozlabs.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"James Morse" <james.morse@arm.com>,
linux-arm-kernel@lists.infradead.org,
"Marc Zyngier" <maz@kernel.org>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
kvmarm@lists.cs.columbia.edu,
"Julien Thierry" <julien.thierry.kdev@gmail.com>,
"Jim Mattson" <jmattson@google.com>
Subject: Re: [PATCH v2 14/15] KVM: Terminate memslot walks via used_slots
Date: Thu, 24 Oct 2019 12:42:14 -0700 [thread overview]
Message-ID: <20191024194214.GB28043@linux.intel.com> (raw)
In-Reply-To: <20191024193856.GA28043@linux.intel.com>
On Thu, Oct 24, 2019 at 12:38:56PM -0700, Sean Christopherson wrote:
> On Tue, Oct 22, 2019 at 05:53:27PM +0200, Paolo Bonzini wrote:
> > On 22/10/19 17:52, Sean Christopherson wrote:
> > >
> > > Anyways, I'm not at all opposed to adding comments, just want to make sure
> > > I'm not forgetting something. If it's ok with you, I'll comment the code
> > > and/or functions and reply here to refine them without having to respin
> > > the whole series.
> >
> > Yes, I agree this is better.
>
> Here's what I ended up with. I also added kvm_memslot_insert_back() to
> help document the purpose of incrementing used_slots, and renamed
> kvm_shift_memslots_forward()->kvm_memslot_move_backward() and
> kvm_shift_memslots_backward()->kvm_memslot_move_forward() because I was
> having trouble reconciling having the comments focus on the changed
> memslot while the names of the functions reflected what happens to the
> other memslots.
Oh, and I need to respin the series to fix build bugs on MIPS and PPC,
I'll wait to do that until I get a thumbs up on this code.
_______________________________________________
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: "James Hogan" <jhogan@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.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
Subject: Re: [PATCH v2 14/15] KVM: Terminate memslot walks via used_slots
Date: Thu, 24 Oct 2019 19:42:14 +0000 [thread overview]
Message-ID: <20191024194214.GB28043@linux.intel.com> (raw)
In-Reply-To: <20191024193856.GA28043@linux.intel.com>
On Thu, Oct 24, 2019 at 12:38:56PM -0700, Sean Christopherson wrote:
> On Tue, Oct 22, 2019 at 05:53:27PM +0200, Paolo Bonzini wrote:
> > On 22/10/19 17:52, Sean Christopherson wrote:
> > >
> > > Anyways, I'm not at all opposed to adding comments, just want to make sure
> > > I'm not forgetting something. If it's ok with you, I'll comment the code
> > > and/or functions and reply here to refine them without having to respin
> > > the whole series.
> >
> > Yes, I agree this is better.
>
> Here's what I ended up with. I also added kvm_memslot_insert_back() to
> help document the purpose of incrementing used_slots, and renamed
> kvm_shift_memslots_forward()->kvm_memslot_move_backward() and
> kvm_shift_memslots_backward()->kvm_memslot_move_forward() because I was
> having trouble reconciling having the comments focus on the changed
> memslot while the names of the functions reflected what happens to the
> other memslots.
Oh, and I need to respin the series to fix build bugs on MIPS and PPC,
I'll wait to do that until I get a thumbs up on this code.
next prev parent reply other threads:[~2019-10-24 19:42 UTC|newest]
Thread overview: 150+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 0:35 [PATCH v2 00/15] KVM: Dynamically size memslot arrays Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 01/15] KVM: Reinstall old memslots if arch preparation fails Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-22 0:35 ` [PATCH v2 02/15] KVM: Don't free new memslot if allocation of said memslot fails Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-22 0:35 ` [PATCH v2 03/15] KVM: PPC: Move memslot memory allocation into prepare_memory_region() Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-24 11:55 ` kbuild test robot
2019-10-24 11:55 ` kbuild test robot
2019-10-24 11:55 ` kbuild test robot
2019-10-24 11:55 ` kbuild test robot
2019-10-24 11:55 ` kbuild test robot
2019-10-22 0:35 ` [PATCH v2 04/15] KVM: x86: Allocate memslot resources during prepare_memory_region() Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 05/15] KVM: Drop kvm_arch_create_memslot() Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 06/15] KVM: Explicitly free allocated-but-unused dirty bitmap Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 07/15] KVM: Refactor error handling for setting memory region Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 08/15] KVM: Move setting of memslot into helper routine Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 09/15] KVM: Move memslot deletion to helper function Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-22 0:35 ` [PATCH v2 10/15] KVM: Simplify kvm_free_memslot() and all its descendents Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 11/15] KVM: Clean up local variable usage in __kvm_set_memory_region() Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 12/15] KVM: Provide common implementation for generic dirty log functions Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-23 9:29 ` Christoffer Dall
2019-10-24 10:28 ` kbuild test robot
2019-10-24 10:28 ` kbuild test robot
2019-10-24 10:28 ` kbuild test robot
2019-10-24 10:28 ` kbuild test robot
2019-10-24 10:28 ` kbuild test robot
2019-10-22 0:35 ` [PATCH v2 13/15] KVM: Ensure validity of memslot with respect to kvm_get_dirty_log() Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 14/15] KVM: Terminate memslot walks via used_slots Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 15:28 ` Sean Christopherson
2019-10-22 15:28 ` Sean Christopherson
2019-10-22 15:28 ` Sean Christopherson
2019-10-22 15:28 ` Sean Christopherson
2019-10-22 15:30 ` Paolo Bonzini
2019-10-22 15:30 ` Paolo Bonzini
2019-10-22 15:30 ` Paolo Bonzini
2019-10-22 15:30 ` Paolo Bonzini
2019-10-22 15:52 ` Sean Christopherson
2019-10-22 15:52 ` Sean Christopherson
2019-10-22 15:52 ` Sean Christopherson
2019-10-22 15:52 ` Sean Christopherson
2019-10-22 15:53 ` Paolo Bonzini
2019-10-22 15:53 ` Paolo Bonzini
2019-10-22 15:53 ` Paolo Bonzini
2019-10-22 15:53 ` Paolo Bonzini
2019-10-24 19:38 ` Sean Christopherson
2019-10-24 19:38 ` Sean Christopherson
2019-10-24 19:38 ` Sean Christopherson
2019-10-24 19:38 ` Sean Christopherson
2019-10-24 19:42 ` Sean Christopherson [this message]
2019-10-24 19:42 ` Sean Christopherson
2019-10-24 19:42 ` Sean Christopherson
2019-10-24 19:42 ` Sean Christopherson
2019-10-24 20:24 ` Paolo Bonzini
2019-10-24 20:24 ` Paolo Bonzini
2019-10-24 20:24 ` Paolo Bonzini
2019-10-24 20:24 ` Paolo Bonzini
2019-10-24 20:48 ` Sean Christopherson
2019-10-24 20:48 ` Sean Christopherson
2019-10-24 20:48 ` Sean Christopherson
2019-10-24 20:48 ` Sean Christopherson
2019-10-22 0:35 ` [PATCH v2 15/15] KVM: Dynamically size memslot array based on number of used slots Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 0:35 ` Sean Christopherson
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 15:22 ` Sean Christopherson
2019-10-22 15:22 ` Sean Christopherson
2019-10-22 15:22 ` Sean Christopherson
2019-10-22 15:22 ` Sean Christopherson
2019-10-22 13:59 ` [PATCH v2 00/15] KVM: Dynamically size memslot arrays Paolo Bonzini
2019-10-22 13:59 ` Paolo Bonzini
2019-10-22 13:59 ` Paolo Bonzini
2019-10-22 13:59 ` Paolo Bonzini
2019-10-23 18:56 ` Christian Borntraeger
2019-10-23 18:56 ` Christian Borntraeger
2019-10-23 18:56 ` Christian Borntraeger
2019-10-23 18:56 ` Christian Borntraeger
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-22 14:04 ` Paolo Bonzini
2019-10-23 9:39 ` Christoffer Dall
2019-10-23 9:39 ` Christoffer Dall
2019-10-23 9:39 ` Christoffer Dall
2019-10-23 9:39 ` Christoffer Dall
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=20191024194214.GB28043@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=borntraeger@de.ibm.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.