public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: "Nadav Har'El" <nyh@math.technion.ac.il>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion
Date: Wed, 27 Feb 2013 12:23:27 +0100	[thread overview]
Message-ID: <512DECAF.7020600@siemens.com> (raw)
In-Reply-To: <20130227112052.GG26252@8bytes.org>

On 2013-02-27 12:20, Joerg Roedel wrote:
> On Mon, Feb 25, 2013 at 10:04:50AM +0100, Jan Kiszka wrote:
>> Is the nested-related state already saved on AMD, Jörg? If not, adding
>> this one would not make things worse at least. Still, missing user space
>> save/restore already breaks reset, not only migration (dunno if this is
>> better on AMD).
> 
> Not sure if this is what you are asking for, but nested state is at not
> saved/restored for migration or anything. This is a long-standing issue
> which needs to be fixed at some point.

As I suspected. That needs to be solved at some point, but for now it
would not cause any regression to add another unsaved nested-related
state (here: "INIT asserted"). That was my questions.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-02-27 11:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-24 14:08 [PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion Jan Kiszka
2013-02-25  8:00 ` Nadav Har'El
2013-02-25  9:04   ` Jan Kiszka
2013-02-27 11:20     ` Joerg Roedel
2013-02-27 11:23       ` Jan Kiszka [this message]
2013-02-27 11:17 ` Joerg Roedel
2013-02-27 11:22   ` Jan Kiszka

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=512DECAF.7020600@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=joro@8bytes.org \
    --cc=jun.nakajima@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=nyh@math.technion.ac.il \
    /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