From: Sheng Yang <sheng@linux.intel.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: VMX: Disable unrestricted guest when EPT disabled
Date: Thu, 18 Mar 2010 13:57:48 +0800 [thread overview]
Message-ID: <201003181357.48777.sheng@linux.intel.com> (raw)
In-Reply-To: <4035AF34-DD16-4C0B-B394-220282F1B705@suse.de>
On Thursday 18 March 2010 13:51:41 Alexander Graf wrote:
> On 18.03.2010, at 02:50, Sheng Yang wrote:
> > On Thursday 18 March 2010 02:37:10 Alexander Graf wrote:
> >> Marcelo Tosatti wrote:
> >>> On Fri, Nov 27, 2009 at 04:46:26PM +0800, Sheng Yang wrote:
> >>>> Otherwise would cause VMEntry failure when using ept=0 on unrestricted
> >>>> guest supported processors.
> >>>>
> >>>> Signed-off-by: Sheng Yang <sheng@linux.intel.com>
> >>>
> >>> Applied, thanks.
> >>
> >> So without this patch kvm breaks with ept=0? Sounds like a stable
> >> candidate to me.
> >
> > Seems unrestricted guest code isn't in v2.6.31-stable, and v2.6.32 had
> > already fixed this issue. So it should be fine.
>
> Are you sure? I don't see the patch in 2.6.32-stable git.
Yes, you are right. Found it not in 2.6.32-stable...
Would post a patch for stable.
Thanks
--
regards
Yang, Sheng
next prev parent reply other threads:[~2010-03-18 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 8:46 [PATCH] KVM: VMX: Disable unrestricted guest when EPT disabled Sheng Yang
2009-11-30 22:02 ` Marcelo Tosatti
2010-03-17 18:37 ` Alexander Graf
2010-03-18 1:50 ` Sheng Yang
2010-03-18 5:51 ` Alexander Graf
2010-03-18 5:57 ` Sheng Yang [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 6:11 Sheng Yang
2010-04-07 21:49 ` Greg KH
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=201003181357.48777.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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.