All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
To: x86@kernel.org, kexec@lists.infradead.org,
	linux-doc@vger.kernel.org, Avi Kivity <avi@redhat.com>,
	mtosatti@redhat.com
Cc: linux-kernel@vger.kernel.org,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [PATCH 0/3] x86: clear vmcss on all cpus when doing kdump if necessary
Date: Fri, 12 Oct 2012 14:40:59 +0800	[thread overview]
Message-ID: <5077BB7B.4030203@cn.fujitsu.com> (raw)

Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active on the logical processors may
be corrupted. But, sometimes, we need the VMCSs to debug guest images contained
in the host vmcore. To prevent the corruption, we should VMCLEAR the VMCSs before
executing the VMXOFF instruction.

The patch set provides an alternative way to clear VMCSs related to guests
on all cpus when host is doing kdump.

zhangyanfei (3):
  x86/kexec: clear vmcss on all cpus if necessary
  KVM: make crash_clear_loaded_vmcss valid when kvm_intel is loaded
  sysctl: introduce a new interface to control kdump-vmcs-clear
    behaviour

 Documentation/sysctl/kernel.txt |    8 ++++++++
 arch/x86/include/asm/kexec.h    |    3 +++
 arch/x86/kernel/crash.c         |   23 +++++++++++++++++++++++
 arch/x86/kvm/vmx.c              |    9 +++++++++
 kernel/sysctl.c                 |   10 ++++++++++
 5 files changed, 53 insertions(+), 0 deletions(-)

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
To: x86@kernel.org, kexec@lists.infradead.org,
	linux-doc@vger.kernel.org, Avi Kivity <avi@redhat.com>,
	mtosatti@redhat.com
Cc: linux-kernel@vger.kernel.org,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [PATCH 0/3] x86: clear vmcss on all cpus when doing kdump if necessary
Date: Fri, 12 Oct 2012 14:40:59 +0800	[thread overview]
Message-ID: <5077BB7B.4030203@cn.fujitsu.com> (raw)

Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active on the logical processors may
be corrupted. But, sometimes, we need the VMCSs to debug guest images contained
in the host vmcore. To prevent the corruption, we should VMCLEAR the VMCSs before
executing the VMXOFF instruction.

The patch set provides an alternative way to clear VMCSs related to guests
on all cpus when host is doing kdump.

zhangyanfei (3):
  x86/kexec: clear vmcss on all cpus if necessary
  KVM: make crash_clear_loaded_vmcss valid when kvm_intel is loaded
  sysctl: introduce a new interface to control kdump-vmcs-clear
    behaviour

 Documentation/sysctl/kernel.txt |    8 ++++++++
 arch/x86/include/asm/kexec.h    |    3 +++
 arch/x86/kernel/crash.c         |   23 +++++++++++++++++++++++
 arch/x86/kvm/vmx.c              |    9 +++++++++
 kernel/sysctl.c                 |   10 ++++++++++
 5 files changed, 53 insertions(+), 0 deletions(-)

             reply	other threads:[~2012-10-12  6:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  6:40 Zhang Yanfei [this message]
2012-10-12  6:40 ` [PATCH 0/3] x86: clear vmcss on all cpus when doing kdump if necessary Zhang Yanfei
2012-10-12  6:43 ` [PATCH 1/3] x86/kexec: clear vmcss on all cpus " Zhang Yanfei
2012-10-12  6:43   ` Zhang Yanfei
2012-10-12  6:44 ` [PATCH 2/3] KVM: make crash_clear_loaded_vmcss valid when kvm_intel is loaded Zhang Yanfei
2012-10-12  6:44   ` Zhang Yanfei
2012-10-12  6:45 ` [PATCH 3/3] sysctl: introduce a new interface to control kdump-vmcs-clear behaviour Zhang Yanfei
2012-10-12  6:45   ` Zhang Yanfei
2012-10-15 15:43 ` [PATCH 0/3] x86: clear vmcss on all cpus when doing kdump if necessary Avi Kivity
2012-10-15 15:43   ` Avi Kivity
2012-10-15 15:43   ` Avi Kivity
2012-10-17  2:28   ` Zhang Yanfei
2012-10-17  2:28     ` Zhang Yanfei
2012-10-17 10:16     ` Avi Kivity
2012-10-17 10:16       ` Avi Kivity
2012-10-18  1:12       ` Zhang Yanfei
2012-10-18  1:12         ` Zhang Yanfei
2012-10-18 10:55         ` Avi Kivity
2012-10-18 10:55           ` Avi Kivity
2012-10-19  4:51           ` Zhang Yanfei
2012-10-19  4:51             ` Zhang Yanfei

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=5077BB7B.4030203@cn.fujitsu.com \
    --to=zhangyanfei@cn.fujitsu.com \
    --cc=avi@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=x86@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 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.