kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoffer Dall <c.dall@virtualopensystems.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [kvmarm] [PATCH] KVM: Take kvm instead of vcpu to mmu_notifier_retry
Date: Tue, 23 Oct 2012 13:36:17 +0200	[thread overview]
Message-ID: <50868131.2090208@redhat.com> (raw)
In-Reply-To: <1350270618-9712-1-git-send-email-c.dall@virtualopensystems.com>

On 10/15/2012 05:10 AM, Christoffer Dall wrote:
> The mmu_notifier_retry is not specific to any vcpu (and never will be)
> so only take struct kvm as a parameter.
> 
> The motivation is the ARM mmu code that needs to call this from
> somewhere where we long let go of the vcpu pointer.

Applied, thanks.


-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2012-10-23 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  3:10 [PATCH] KVM: Take kvm instead of vcpu to mmu_notifier_retry Christoffer Dall
2012-10-23 11:36 ` Avi Kivity [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=50868131.2090208@redhat.com \
    --to=avi@redhat.com \
    --cc=c.dall@virtualopensystems.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    /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;
as well as URLs for NNTP newsgroup(s).