All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: kvm@vger.kernel.org, bgardon@google.com, andrew.jones@linux.dev,
	dmatlack@google.com, will@kernel.org, shan.gavin@gmail.com,
	catalin.marinas@arm.com, kvmarm@lists.linux.dev,
	pbonzini@redhat.com, zhenyzha@redhat.com, shuah@kernel.org,
	kvmarm@lists.cs.columbia.edu, ajones@ventanamicro.com
Subject: Re: [PATCH v9 3/7] KVM: Support dirty ring in conjunction with bitmap
Date: Thu, 10 Nov 2022 10:25:57 +0000	[thread overview]
Message-ID: <86sfirp0lm.wl-maz@kernel.org> (raw)
In-Reply-To: <672eb11b-19db-9a9f-1898-8d2af0d45724@redhat.com>

Hi Gavin,

On Wed, 09 Nov 2022 00:51:21 +0000,
Gavin Shan <gshan@redhat.com> wrote:
> 
> On 11/9/22 8:32 AM, Sean Christopherson wrote:
> > That said, there're no remaining issues that can't be sorted out
> > on top, so don't hold up v10 if I don't look at it in a timely
> > manner for whatever reason.  I agree with Marc that it'd be good
> > to get this in -next sooner than later.
> > 
> 
> Sure. I would give v9 a few days, prior to posting v10. I'm not sure
> if other people still have concerns. If there are more comments, I
> want to address all of them in v10 :)

Please post v10 ASAP. I'm a bit behind on queuing stuff, and I'll be
travelling next week, making it a bit more difficult to be on top of
things. So whatever I can put into -next now is good.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
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: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
	kvm@vger.kernel.org, shuah@kernel.org, catalin.marinas@arm.com,
	andrew.jones@linux.dev, ajones@ventanamicro.com,
	bgardon@google.com, dmatlack@google.com, will@kernel.org,
	suzuki.poulose@arm.com, alexandru.elisei@arm.com,
	pbonzini@redhat.com, peterx@redhat.com, oliver.upton@linux.dev,
	zhenyzha@redhat.com, shan.gavin@gmail.com
Subject: Re: [PATCH v9 3/7] KVM: Support dirty ring in conjunction with bitmap
Date: Thu, 10 Nov 2022 10:25:57 +0000	[thread overview]
Message-ID: <86sfirp0lm.wl-maz@kernel.org> (raw)
Message-ID: <20221110102557.Ulu6ucKOg_CDxp9BLoUMqTfFhrEU6aQMZqBqhezMbvY@z> (raw)
In-Reply-To: <672eb11b-19db-9a9f-1898-8d2af0d45724@redhat.com>

Hi Gavin,

On Wed, 09 Nov 2022 00:51:21 +0000,
Gavin Shan <gshan@redhat.com> wrote:
> 
> On 11/9/22 8:32 AM, Sean Christopherson wrote:
> > That said, there're no remaining issues that can't be sorted out
> > on top, so don't hold up v10 if I don't look at it in a timely
> > manner for whatever reason.  I agree with Marc that it'd be good
> > to get this in -next sooner than later.
> > 
> 
> Sure. I would give v9 a few days, prior to posting v10. I'm not sure
> if other people still have concerns. If there are more comments, I
> want to address all of them in v10 :)

Please post v10 ASAP. I'm a bit behind on queuing stuff, and I'll be
travelling next week, making it a bit more difficult to be on top of
things. So whatever I can put into -next now is good.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2022-11-10 10:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  4:10 [PATCH v9 0/7] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan
2022-11-08  4:10 ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 1/7] KVM: x86: Introduce KVM_REQ_DIRTY_RING_SOFT_FULL Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 2/7] KVM: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 3/7] KVM: Support dirty ring in conjunction with bitmap Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08 16:25   ` Sean Christopherson
2022-11-08 16:25     ` Sean Christopherson
2022-11-08 22:19     ` Gavin Shan
2022-11-08 22:19       ` Gavin Shan
2022-11-09  0:05       ` Sean Christopherson
2022-11-09  0:05         ` Sean Christopherson
2022-11-09  0:17         ` Gavin Shan
2022-11-09  0:17           ` Gavin Shan
2022-11-09  0:32           ` Sean Christopherson
2022-11-09  0:32             ` Sean Christopherson
2022-11-09  0:51             ` Gavin Shan
2022-11-09  0:51               ` Gavin Shan
2022-11-10 10:25               ` Marc Zyngier [this message]
2022-11-10 10:25                 ` Marc Zyngier
2022-11-10 10:56                 ` Gavin Shan
2022-11-10 10:56                   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 4/7] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 5/7] KVM: selftests: Use host page size to map ring buffer in dirty_log_test Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 6/7] KVM: selftests: Clear dirty ring states between two modes " Gavin Shan
2022-11-08  4:10   ` Gavin Shan
2022-11-08  4:10 ` [PATCH v9 7/7] KVM: selftests: Automate choosing dirty ring size " Gavin Shan
2022-11-08  4:10   ` Gavin Shan

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=86sfirp0lm.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=andrew.jones@linux.dev \
    --cc=bgardon@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=dmatlack@google.com \
    --cc=gshan@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=kvmarm@lists.linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=shan.gavin@gmail.com \
    --cc=shuah@kernel.org \
    --cc=will@kernel.org \
    --cc=zhenyzha@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.