From: Gleb Natapov <gleb@redhat.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Sanjay Lal <sanjayl@kymasys.com>
Subject: Re: Q: What is the struct kvm srcu protecting?
Date: Sun, 5 May 2013 10:37:54 +0300 [thread overview]
Message-ID: <20130505073754.GG22125@redhat.com> (raw)
In-Reply-To: <5183F205.40006@gmail.com>
On Fri, May 03, 2013 at 10:21:09AM -0700, David Daney wrote:
> On 05/03/2013 03:51 AM, Gleb Natapov wrote:
> >Hi David,
> >
> >On Thu, May 02, 2013 at 10:48:36PM -0300, Marcelo Tosatti wrote:
> >>On Thu, May 02, 2013 at 11:22:52AM -0700, David Daney wrote:
> >>>Hi,
> >>>
> >>>I am working on the MIPS KVM port, and am trying to figure out under
> >>>which circumstances do I need to srcu_read_lock()/srcu_read_unlock()
> >>>the kvm->srcu.
> >>
> >Is your work somehow related to the work of Sanjay Lal that can be found
> >here: https://git.linux-mips.org/?p=ralf/upstream-sfr.git;a=summary?
> >
>
> It is related in that a single asm/uaip/kvm.h must be shared between
> the implementations. It differs in that it is based on the MIPS-VZ
> hardware virtualization feature, where as Sanjay's code is a pure
> software solution.
>
> If possible some code might be shared between the two, but it may
> end up looking somewhat like the x86 implementation where there are
> separate VMX and SVM implementations.
>
Sanjay code already has such design and the reason he gave for it was upcoming
HW virtualization support.
--
Gleb.
prev parent reply other threads:[~2013-05-05 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 18:22 Q: What is the struct kvm srcu protecting? David Daney
2013-05-03 1:48 ` Marcelo Tosatti
2013-05-03 10:51 ` Gleb Natapov
2013-05-03 17:21 ` David Daney
2013-05-05 7:37 ` Gleb Natapov [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=20130505073754.GG22125@redhat.com \
--to=gleb@redhat.com \
--cc=ddaney.cavm@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sanjayl@kymasys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox