public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	avi@redhat.com, glommer@redhat.com
Subject: Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests
Date: Thu, 16 Jul 2009 11:09:50 -0500	[thread overview]
Message-ID: <4A5F50CE.1060808@us.ibm.com> (raw)
In-Reply-To: <4A5F4B96.6050409@novell.com>

Gregory Haskins wrote:
> That said, I think the assumption that was made when I was using this
> was that a proper ref for the page was acquired by the gfn_to_page() and
> dropped by the caller.  This was always used in the context of a
> hypercall/vmexit so presumably the gpa should be considered stable
> across that call.  Is that not true?
>   

If you're in kvm.ko, then yes, that's a safe assumption to make because 
the guest VCPU cannot run while you are running.

But you're opening this interface to any caller so the VCPU is likely to 
be running while someone calls this function

> Regards,
> -Greg
>
>
>   


-- 
Regards,

Anthony Liguori


  reply	other threads:[~2009-07-16 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 15:19 [KVM PATCH] xinterface Gregory Haskins
2009-07-16 15:19 ` [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests Gregory Haskins
2009-07-16 15:30   ` Sam Ravnborg
2009-07-16 15:31     ` Gregory Haskins
2009-07-16 15:37   ` Anthony Liguori
2009-07-16 15:47     ` Gregory Haskins
2009-07-16 16:09       ` Anthony Liguori [this message]
2009-07-16 16:52   ` Arnd Bergmann
2009-07-16 18:22     ` Gregory Haskins
2009-07-16 18:53       ` Gregory Haskins
2009-07-16 19:38         ` Zan Lynx
2009-07-16 19:48           ` Gregory Haskins
2009-07-16 19:46       ` Arnd Bergmann
2009-07-17  0:25         ` Gregory Haskins

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=4A5F50CE.1060808@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=ghaskins@novell.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.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