Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Avi Kivity <avi@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	kvm@vger.kernel.org, kexec@lists.infradead.org,
	Haren Myneni <hbabu@us.ibm.com>,
	Simon Horman <horms@verge.net.au>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 0/2] kvm: disable virtualization on kdump
Date: Mon, 27 Oct 2008 08:05:50 -0700	[thread overview]
Message-ID: <m1skqi9iy9.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <49058645.9010005@redhat.com> (Avi Kivity's message of "Mon, 27 Oct 2008 11:13:41 +0200")

Avi Kivity <avi@redhat.com> writes:

> There's no way to query whether vmx is enabled or disabled, AFAICT.  So we have
> to execute vmxoff and ignore possible #UDs.
>
> If we trust the exception handlers, there's no problem.  Otherwise we need to
> replace the current #UD handler with an iret (perhaps switching temporarily to
> another IDT).

Ugh.  We already change the IDT on that code path so that
may be a way to go.

> The general kexec path also wants this fixed.

It looks like someone hooked the reboot notifier which should
be called on the normal kexec path.

Eric

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

  parent reply	other threads:[~2008-10-27 15:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 15:01 [PATCH 0/2] kvm: disable virtualization on kdump Eduardo Habkost
2008-10-20 15:01 ` [PATCH 1/2] kdump: crash-time CPU halt notifier interface Eduardo Habkost
2008-10-20 15:01 ` [PATCH 2/2] kvm: disable virtualization when halting CPUs on crash Eduardo Habkost
2008-10-22 23:28 ` [PATCH 0/2] kvm: disable virtualization on kdump Simon Horman
2008-10-23 19:41   ` Eduardo Habkost
2008-10-23 22:29     ` Simon Horman
2008-10-24  1:00       ` Eric W. Biederman
2008-10-26 12:49         ` Avi Kivity
2008-10-26 14:46           ` Eric W. Biederman
2008-10-26 15:07             ` Avi Kivity
2008-10-26 21:39               ` Eduardo Habkost
2008-10-27  2:08                 ` Eric W. Biederman
2008-10-27  9:13                   ` Avi Kivity
2008-10-27 12:28                     ` Eduardo Habkost
2008-10-27 14:02                       ` Avi Kivity
2008-10-27 17:32                         ` Eric W. Biederman
2008-10-28 19:45                           ` Eduardo Habkost
2008-10-28 20:13                             ` Eric W. Biederman
2008-10-29  9:41                               ` Avi Kivity
2008-10-29 14:54                                 ` Eric W. Biederman
2008-10-29 17:03                                   ` Avi Kivity
2008-10-30  1:33                                     ` Eric W. Biederman
2008-10-30  7:35                                       ` Chris Lalancette
2008-10-30  7:43                                         ` Avi Kivity
2008-10-30  7:52                                       ` Avi Kivity
2008-10-29  9:31                             ` Avi Kivity
2008-10-27 15:05                     ` Eric W. Biederman [this message]
2008-10-27 15:50                       ` Eduardo Habkost
2008-10-27  8:54                 ` Avi Kivity
2008-10-27 13:09                   ` Vivek Goyal
2008-10-27 14:04                     ` Avi Kivity
2008-10-29 20:10                     ` Eduardo Habkost
2008-10-29 20:29                       ` Avi Kivity
2008-10-29 21:05                       ` Vivek Goyal
2008-10-30  0:58                         ` Eric W. Biederman
2008-10-26 21:47               ` Eric W. Biederman
2008-10-27  8:59                 ` Avi Kivity
2008-10-27 15:02                   ` Eric W. Biederman
2008-10-27 15:38                     ` Eduardo Habkost
2008-10-26 12:46     ` Avi Kivity

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=m1skqi9iy9.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=avi@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=hbabu@us.ibm.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=vgoyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox