From: Gleb Natapov <gleb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Marcelo Tosatti
<mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Zhang Yanfei
<zhangyanfei-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Subject: Re: [PATCH v8 1/2] x86/kexec: add a new atomic notifier list for kdump
Date: Mon, 26 Nov 2012 19:53:27 +0200 [thread overview]
Message-ID: <20121126175327.GG12969@redhat.com> (raw)
In-Reply-To: <87fw3wuuoh.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
On Mon, Nov 26, 2012 at 11:43:10AM -0600, Eric W. Biederman wrote:
> Gleb Natapov <gleb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
>
> > On Mon, Nov 26, 2012 at 09:08:54AM -0600, Eric W. Biederman wrote:
> >> Zhang Yanfei <zhangyanfei-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> writes:
> >>
> >> > This patch adds an atomic notifier list named crash_notifier_list.
> >> > Currently, when loading kvm-intel module, a notifier will be registered
> >> > in the list to enable vmcss loaded on all cpus to be VMCLEAR'd if
> >> > needed.
> >>
> >> crash_notifier_list ick gag please no. Effectively this makes the kexec
> >> on panic code path undebuggable.
> >>
> >> Instead we need to use direct function calls to whatever you are doing.
> >>
> > The code walks linked list in kvm-intel module and calls vmclear on
> > whatever it finds there. Since the function have to resides in kvm-intel
> > module it cannot be called directly. Is callback pointer that is set
> > by kvm-intel more acceptable?
>
> Yes a specific callback function is more acceptable. Looking a little
> deeper vmclear_local_loaded_vmcss is not particularly acceptable. It is
> doing a lot of work that is unnecessary to save the virtual registers
> on the kexec on panic path.
>
What work are you referring to in particular that may not be acceptable?
> In fact I wonder if it might not just be easier to call vmcs_clear to a
> fixed per cpu buffer.
>
There may be more than one vmcs loaded on a cpu, hence the list.
> Performing list walking in interrupt context without locking in
> vmclear_local_loaded vmcss looks a bit scary. Not that locking would
> make it any better, as locking would simply add one more way to deadlock
> the system. Only an rcu list walk is at all safe. A list walk that
> modifies the list as vmclear_local_loaded_vmcss does is definitely not safe.
>
The list vmclear_local_loaded walks is per cpu. Zhang's kvm patch
disables kexec callback while list is modified.
--
Gleb.
next prev parent reply other threads:[~2012-11-26 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:22 [PATCH v8 0/2] x86: vmclear vmcss on all cpus when doing kdump if necessary Zhang Yanfei
[not found] ` <50ADE0C2.1000106-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-11-22 8:23 ` [PATCH v8 1/2] x86/kexec: add a new atomic notifier list for kdump Zhang Yanfei
2012-11-26 15:08 ` Eric W. Biederman
[not found] ` <87ip8sxuyh.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-11-26 17:20 ` Gleb Natapov
[not found] ` <20121126172054.GF12969-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-11-26 17:43 ` Eric W. Biederman
[not found] ` <87fw3wuuoh.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-11-26 17:53 ` Gleb Natapov [this message]
2012-11-26 18:18 ` Eric W. Biederman
2012-11-27 1:32 ` Zhang Yanfei
2012-11-27 1:49 ` Eric W. Biederman
2012-11-27 1:53 ` Zhang Yanfei
2012-11-22 8:25 ` [PATCH v8 2/2] KVM-INTEL: add a notifier and a bitmap to support VMCLEAR in kdump Zhang Yanfei
2012-11-25 14:26 ` [PATCH v8 0/2] x86: vmclear vmcss on all cpus when doing kdump if necessary Gleb Natapov
[not found] ` <20121125142642.GC25516-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-11-26 1:50 ` Zhang Yanfei
2012-11-26 1:55 ` 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=20121126175327.GG12969@redhat.com \
--to=gleb-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=zhangyanfei-BthXqXjhjHXQFUHtdCDX3A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).