From: Eduardo Habkost <ehabkost@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@osdl.org>,
kvm@vger.kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Haren Myneni <hbabu@us.ibm.com>,
Simon Horman <horms@verge.net.au>, Avi Kivity <avi@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Andrey Borzenkov <arvidjaar@mail.ru>,
mingo@redhat.com, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 15/16] kvm: x86: set kdump virt_disable function on initialization
Date: Wed, 5 Nov 2008 15:50:05 -0200 [thread overview]
Message-ID: <20081105175004.GI5247@blackpad> (raw)
In-Reply-To: <m1od0u3wyq.fsf@frodo.ebiederm.org>
On Wed, Nov 05, 2008 at 09:26:53AM -0800, Eric W. Biederman wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
>
> > Finally implement the virt_disable function for kdump. It will call
> > kvm_x86_ops->crash_hardware_disable(), that will disable virtualization
> > extensions on the CPU if it is not disabled yet.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > arch/x86/kvm/x86.c | 19 ++++++++++++++++++-
> > 1 files changed, 18 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index 049c6a0..9e61baf 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -40,6 +40,7 @@
> > #include <asm/msr.h>
> > #include <asm/desc.h>
> > #include <asm/mtrr.h>
> > +#include <asm/virtext.h>
> >
> > #define MAX_IO_MSRS 256
> > #define CR0_RESERVED_BITS \
> > @@ -2581,6 +2582,13 @@ int kvm_emulate_pio_string(struct kvm_vcpu *vcpu, struct
> > kvm_run *run, int in,
> > }
> > EXPORT_SYMBOL_GPL(kvm_emulate_pio_string);
> >
> > +/* Called at crash time, so we can disable virtualization if needed
> > + */
> > +static void crash_hardware_disable(void)
> > +{
> > + kvm_x86_ops->crash_hardware_disable(NULL);
> > +}
> > +
> > int kvm_arch_init(void *opaque)
> > {
> > int r;
> > @@ -2605,9 +2613,15 @@ int kvm_arch_init(void *opaque)
> >
> > kvm_x86_ops = ops;
> >
> > + r = set_virt_disable_func(crash_hardware_disable);
>
> Can we make this say:
> set_virt_disable_func(kvm_x86_ops->crash_hardware_disable);
>
> So we can avoid going through 2 levels of function pointers?
> I find that a little scary in code that might be running
> at the edge of stack overflow.
When I've checked this (on x86_64), gcc did tail recursion optimization
and the call was just a jump to the function, so stack usage shouldn't
be a problem.
But I am inclined to agree with you about the excess of abstraction.
--
Eduardo
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Avi Kivity <avi@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Simon Horman <horms@verge.net.au>, Andrew Morton <akpm@osdl.org>,
Vivek Goyal <vgoyal@redhat.com>, Haren Myneni <hbabu@us.ibm.com>,
Andrey Borzenkov <arvidjaar@mail.ru>,
mingo@redhat.com, "Rafael J. Wysocki" <rjw@sisk.pl>,
kexec@lists.infradead.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 15/16] kvm: x86: set kdump virt_disable function on initialization
Date: Wed, 5 Nov 2008 15:50:05 -0200 [thread overview]
Message-ID: <20081105175004.GI5247@blackpad> (raw)
In-Reply-To: <m1od0u3wyq.fsf@frodo.ebiederm.org>
On Wed, Nov 05, 2008 at 09:26:53AM -0800, Eric W. Biederman wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
>
> > Finally implement the virt_disable function for kdump. It will call
> > kvm_x86_ops->crash_hardware_disable(), that will disable virtualization
> > extensions on the CPU if it is not disabled yet.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > arch/x86/kvm/x86.c | 19 ++++++++++++++++++-
> > 1 files changed, 18 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index 049c6a0..9e61baf 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -40,6 +40,7 @@
> > #include <asm/msr.h>
> > #include <asm/desc.h>
> > #include <asm/mtrr.h>
> > +#include <asm/virtext.h>
> >
> > #define MAX_IO_MSRS 256
> > #define CR0_RESERVED_BITS \
> > @@ -2581,6 +2582,13 @@ int kvm_emulate_pio_string(struct kvm_vcpu *vcpu, struct
> > kvm_run *run, int in,
> > }
> > EXPORT_SYMBOL_GPL(kvm_emulate_pio_string);
> >
> > +/* Called at crash time, so we can disable virtualization if needed
> > + */
> > +static void crash_hardware_disable(void)
> > +{
> > + kvm_x86_ops->crash_hardware_disable(NULL);
> > +}
> > +
> > int kvm_arch_init(void *opaque)
> > {
> > int r;
> > @@ -2605,9 +2613,15 @@ int kvm_arch_init(void *opaque)
> >
> > kvm_x86_ops = ops;
> >
> > + r = set_virt_disable_func(crash_hardware_disable);
>
> Can we make this say:
> set_virt_disable_func(kvm_x86_ops->crash_hardware_disable);
>
> So we can avoid going through 2 levels of function pointers?
> I find that a little scary in code that might be running
> at the edge of stack overflow.
When I've checked this (on x86_64), gcc did tail recursion optimization
and the call was just a jump to the function, so stack usage shouldn't
be a problem.
But I am inclined to agree with you about the excess of abstraction.
--
Eduardo
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Habkost <ehabkost-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
Haren Myneni <hbabu-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
Andrey Borzenkov <arvidjaar-JGs/UdohzUI@public.gmane.org>,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 15/16] kvm: x86: set kdump virt_disable function on initialization
Date: Wed, 5 Nov 2008 15:50:05 -0200 [thread overview]
Message-ID: <20081105175004.GI5247@blackpad> (raw)
In-Reply-To: <m1od0u3wyq.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
On Wed, Nov 05, 2008 at 09:26:53AM -0800, Eric W. Biederman wrote:
> Eduardo Habkost <ehabkost-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
>
> > Finally implement the virt_disable function for kdump. It will call
> > kvm_x86_ops->crash_hardware_disable(), that will disable virtualization
> > extensions on the CPU if it is not disabled yet.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > ---
> > arch/x86/kvm/x86.c | 19 ++++++++++++++++++-
> > 1 files changed, 18 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index 049c6a0..9e61baf 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -40,6 +40,7 @@
> > #include <asm/msr.h>
> > #include <asm/desc.h>
> > #include <asm/mtrr.h>
> > +#include <asm/virtext.h>
> >
> > #define MAX_IO_MSRS 256
> > #define CR0_RESERVED_BITS \
> > @@ -2581,6 +2582,13 @@ int kvm_emulate_pio_string(struct kvm_vcpu *vcpu, struct
> > kvm_run *run, int in,
> > }
> > EXPORT_SYMBOL_GPL(kvm_emulate_pio_string);
> >
> > +/* Called at crash time, so we can disable virtualization if needed
> > + */
> > +static void crash_hardware_disable(void)
> > +{
> > + kvm_x86_ops->crash_hardware_disable(NULL);
> > +}
> > +
> > int kvm_arch_init(void *opaque)
> > {
> > int r;
> > @@ -2605,9 +2613,15 @@ int kvm_arch_init(void *opaque)
> >
> > kvm_x86_ops = ops;
> >
> > + r = set_virt_disable_func(crash_hardware_disable);
>
> Can we make this say:
> set_virt_disable_func(kvm_x86_ops->crash_hardware_disable);
>
> So we can avoid going through 2 levels of function pointers?
> I find that a little scary in code that might be running
> at the edge of stack overflow.
When I've checked this (on x86_64), gcc did tail recursion optimization
and the call was just a jump to the function, so stack usage shouldn't
be a problem.
But I am inclined to agree with you about the excess of abstraction.
--
Eduardo
next prev parent reply other threads:[~2008-11-05 17:50 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 14:52 [PATCH 00/14] x86: disable virt on kdump and emergency_restart Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 01/16] x86 kdump: Extract kdump-specific code from crash_nmi_callback() Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 02/16] x86 kdump: Move crashing_cpu assignment to nmi_shootdown_cpus() Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 03/16] x86 kdump: Create kdump_nmi_shootdown_cpus() Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 04/16] x86 kdump: Make kdump_nmi_callback() a function ptr on crash_nmi_callback() Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 05/16] x86 kdump: Make nmi_shootdown_cpus() non-static Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 06/16] x86: Move nmi_shootdown_cpus() to reboot.c Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 07/16] x86: Make nmi_shootdown_cpus() available on !SMP and !X86_LOCAL_APIC Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 18:15 ` Eduardo Habkost
2008-11-04 18:15 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 08/16] x86: Emergency virtualization disable function Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-05 17:33 ` Eric W. Biederman
2008-11-05 17:33 ` Eric W. Biederman
2008-11-05 17:52 ` Eduardo Habkost
2008-11-05 17:52 ` Eduardo Habkost
2008-11-05 17:52 ` Eduardo Habkost
2008-11-06 9:48 ` Avi Kivity
2008-11-06 9:48 ` Avi Kivity
2008-11-06 10:22 ` Eric W. Biederman
2008-11-06 10:22 ` Eric W. Biederman
2008-11-06 10:30 ` Avi Kivity
2008-11-06 10:30 ` Avi Kivity
2008-11-06 10:30 ` Avi Kivity
2008-11-06 17:45 ` Eduardo Habkost
2008-11-06 17:45 ` Eduardo Habkost
2008-11-06 17:45 ` Eduardo Habkost
2008-11-09 11:23 ` Avi Kivity
2008-11-09 11:23 ` Avi Kivity
2008-11-09 11:23 ` Avi Kivity
2008-11-04 14:52 ` [PATCH 09/16] kdump: Hook emergency_virt_disable() on crash shutdown code Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-05 14:41 ` Vivek Goyal
2008-11-05 14:41 ` Vivek Goyal
2008-11-05 14:41 ` Vivek Goyal
2008-11-05 15:07 ` Eduardo Habkost
2008-11-05 15:07 ` Eduardo Habkost
2008-11-05 15:07 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 10/16] x86: disable virtualization on all CPUs if needed, on emergency_restart Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 11/16] kvm_x86_ops: crash_hardware_disable() operation Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 12/16] kvm: svm: set crash_hardware_disable to svm_hardware_disable Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 13/16] kvm: vmx: crash_hardware_disable function Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 14/16] kvmx: x86: set kvm_x86_ops earlier on kvm_arch_init() Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 14:52 ` [PATCH 15/16] kvm: x86: set kdump virt_disable function on initialization Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-05 17:26 ` Eric W. Biederman
2008-11-05 17:26 ` Eric W. Biederman
2008-11-05 17:50 ` Eduardo Habkost [this message]
2008-11-05 17:50 ` Eduardo Habkost
2008-11-05 17:50 ` Eduardo Habkost
2008-11-06 9:44 ` Avi Kivity
2008-11-06 9:44 ` Avi Kivity
2008-11-06 9:44 ` Avi Kivity
2008-11-04 14:52 ` [PATCH 16/16] Revert "x86: default to reboot via ACPI" Eduardo Habkost
2008-11-04 14:52 ` Eduardo Habkost
2008-11-04 16:54 ` [PATCH 00/14] x86: disable virt on kdump and emergency_restart Avi Kivity
2008-11-04 16:54 ` Avi Kivity
2008-11-04 16:54 ` Avi Kivity
2008-11-05 14:44 ` Vivek Goyal
2008-11-05 14:44 ` Vivek Goyal
2008-11-05 15:04 ` Eduardo Habkost
2008-11-05 15:04 ` Eduardo Habkost
2008-11-06 9:52 ` Avi Kivity
2008-11-06 9:52 ` Avi Kivity
2008-11-05 16:33 ` Ingo Molnar
2008-11-05 16:33 ` Ingo Molnar
2008-11-05 16:33 ` Ingo Molnar
2008-11-06 9:49 ` Avi Kivity
2008-11-06 9:49 ` Avi Kivity
2008-11-06 9:49 ` Avi Kivity
2008-11-06 12:28 ` Eduardo Habkost
2008-11-06 12:28 ` Eduardo Habkost
2008-11-06 12:28 ` Eduardo Habkost
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=20081105175004.GI5247@blackpad \
--to=ehabkost@redhat.com \
--cc=akpm@osdl.org \
--cc=arvidjaar@mail.ru \
--cc=avi@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--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 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.