Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: madhuparnabhowmik10@gmail.com,
	"Dexuan-Linux Cui" <dexuan.linux@gmail.com>,
	"Josh Triplett" <josh@joshtriplett.org>,
	"Joel Fernandes" <joel@joelfernandes.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	rcu@vger.kernel.org, "open list" <linux-kernel@vger.kernel.org>,
	"X86 ML" <x86@kernel.org>, "kvm list" <kvm@vger.kernel.org>,
	frextrite@gmail.com, lkft-triage@lists.linaro.org,
	"Dexuan Cui" <decui@microsoft.com>,
	juhlee@microsoft.com, "Daniel Díaz" <daniel.diaz@linaro.org>
Subject: Re: [PATCH 2/2] kvm: mmu: page_track: Fix RCU list API usage
Date: Mon, 20 Jul 2020 16:31:13 -0700	[thread overview]
Message-ID: <20200720233113.GZ9247@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CA+G9fYueEA0g4arZYQpZo803FHsYvh3WCq=PhYGULHEDa86pSg@mail.gmail.com>

On Mon, Jul 20, 2020 at 07:43:50PM +0530, Naresh Kamboju wrote:
> On Sun, 19 Jul 2020 at 21:38, Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > On Sun, Jul 19, 2020 at 05:52:44PM +0530, Naresh Kamboju wrote:
> > > On Sat, 18 Jul 2020 at 05:43, Paul E. McKenney <paulmck@kernel.org> wrote:
> > > >
> > > > On Sat, Jul 18, 2020 at 12:35:12AM +0530, Naresh Kamboju wrote:
> > > > > Hi Paul,
> > > > >
> > > > > > I am not seeing this here.
> > > > >
> > > > > Do you notice any warnings while building linux next master
> > > > > for x86_64 architecture ?
> > > >
> > > > Idiot here was failing to enable building of KVM.  With that, I do see
> > > > the error.  The patch resolves it for me.  Does it help for you?
> > >
> > > yes.
> > > The below patch applied on top of linux -next 20200717 tag
> > > and build pass.
> >
> > Thank you!  May I add your Tested-by?
> 
> That would be great please add
> Tested-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> 
> Thank you !

Done, and thank you for spotting this!

							Thanx, Paul

      reply	other threads:[~2020-07-20 23:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 13:10 [PATCH 1/2] rculist : Introduce list/hlist_for_each_entry_srcu() macros madhuparnabhowmik10
2020-07-12 13:10 ` [PATCH 2/2] kvm: mmu: page_track: Fix RCU list API usage madhuparnabhowmik10
2020-07-12 16:08   ` Paul E. McKenney
2020-07-16 14:44     ` Naresh Kamboju
2020-07-17  0:19       ` Dexuan-Linux Cui
2020-07-17 17:07         ` Paul E. McKenney
2020-07-17 18:03           ` Daniel Díaz
2020-07-17 18:25             ` Daniel Díaz
2020-07-17 19:05           ` Naresh Kamboju
2020-07-18  0:12             ` Paul E. McKenney
2020-07-19 12:22               ` Naresh Kamboju
2020-07-19 16:08                 ` Paul E. McKenney
2020-07-20 14:13                   ` Naresh Kamboju
2020-07-20 23:31                     ` Paul E. McKenney [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=20200720233113.GZ9247@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=decui@microsoft.com \
    --cc=dexuan.linux@gmail.com \
    --cc=frextrite@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=juhlee@microsoft.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=madhuparnabhowmik10@gmail.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=rcu@vger.kernel.org \
    --cc=x86@kernel.org \
    /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