From: Avi Kivity <avi@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, Zachary Amsden <zach@vmware.com>,
Eduardo Habkost <ehabkost@redhat.com>,
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>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrey Borzenkov <arvidjaar@mail.ru>,
mingo@redhat.com, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 00/12] x86: disable virt on kdump and emergency_restart (v4)
Date: Fri, 21 Nov 2008 18:07:36 +0200 [thread overview]
Message-ID: <4926DCC8.1040500@redhat.com> (raw)
In-Reply-To: <20081118081501.GF17838@elte.hu>
Ingo Molnar wrote:
> * Eduardo Habkost <ehabkost@redhat.com> wrote:
>
>
>> Hi, Ingo,
>>
>> This is yet another spin of the series to disable vmx on kdump and
>> on emergency_restart, after some feedback from Avi.
>>
>
> this is going to interact with the KVM tree, wont it?
>
> i think the best way forward would be to keep your changes in the KVM
> tree.
>
> Lets try a Git trick for that. Avi could do that by pulling your other
> x86 changes from the x86 topic tree into the kvm tree. They are
> reviewed, acked and well-tested now, and kept in a separate tree so no
> other x86 change will be pulled in via them.
>
> We can do this if Avi can guarantee that these commits wont ever be
> rebased within KVM - then the two trees will merge up just fine in
> linux-next (and later in v2.6.29 as well), without any awkward merge
> dependencies or merge conflicts.
>
I never rebase kvm.git master, so I pulled the x86 changes and applied
all. Ingo, this will mean you have to push x86 before kvm.git, but as
you're generally faster than me there shouldn't be a problem.
Eduardo, please check the merge (there was a small conflict in reboot.c
which I fixed) once I push it. Also, when generating patches that move
files, use the -M switch: this makes it easier to review, and also
handles files that change better.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
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>,
Zachary Amsden <zach@vmware.com>,
kexec@lists.infradead.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/12] x86: disable virt on kdump and emergency_restart (v4)
Date: Fri, 21 Nov 2008 18:07:36 +0200 [thread overview]
Message-ID: <4926DCC8.1040500@redhat.com> (raw)
In-Reply-To: <20081118081501.GF17838@elte.hu>
Ingo Molnar wrote:
> * Eduardo Habkost <ehabkost@redhat.com> wrote:
>
>
>> Hi, Ingo,
>>
>> This is yet another spin of the series to disable vmx on kdump and
>> on emergency_restart, after some feedback from Avi.
>>
>
> this is going to interact with the KVM tree, wont it?
>
> i think the best way forward would be to keep your changes in the KVM
> tree.
>
> Lets try a Git trick for that. Avi could do that by pulling your other
> x86 changes from the x86 topic tree into the kvm tree. They are
> reviewed, acked and well-tested now, and kept in a separate tree so no
> other x86 change will be pulled in via them.
>
> We can do this if Avi can guarantee that these commits wont ever be
> rebased within KVM - then the two trees will merge up just fine in
> linux-next (and later in v2.6.29 as well), without any awkward merge
> dependencies or merge conflicts.
>
I never rebase kvm.git master, so I pulled the x86 changes and applied
all. Ingo, this will mean you have to push x86 before kvm.git, but as
you're generally faster than me there shouldn't be a problem.
Eduardo, please check the merge (there was a small conflict in reboot.c
which I fixed) once I push it. Also, when generating patches that move
files, use the -M switch: this makes it easier to review, and also
handles files that change better.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
Eduardo Habkost
<ehabkost-H+wXaHxf7aLQT0dZR+AlfA@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>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@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 00/12] x86: disable virt on kdump and emergency_restart (v4)
Date: Fri, 21 Nov 2008 18:07:36 +0200 [thread overview]
Message-ID: <4926DCC8.1040500@redhat.com> (raw)
In-Reply-To: <20081118081501.GF17838-X9Un+BFzKDI@public.gmane.org>
Ingo Molnar wrote:
> * Eduardo Habkost <ehabkost-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>
>
>> Hi, Ingo,
>>
>> This is yet another spin of the series to disable vmx on kdump and
>> on emergency_restart, after some feedback from Avi.
>>
>
> this is going to interact with the KVM tree, wont it?
>
> i think the best way forward would be to keep your changes in the KVM
> tree.
>
> Lets try a Git trick for that. Avi could do that by pulling your other
> x86 changes from the x86 topic tree into the kvm tree. They are
> reviewed, acked and well-tested now, and kept in a separate tree so no
> other x86 change will be pulled in via them.
>
> We can do this if Avi can guarantee that these commits wont ever be
> rebased within KVM - then the two trees will merge up just fine in
> linux-next (and later in v2.6.29 as well), without any awkward merge
> dependencies or merge conflicts.
>
I never rebase kvm.git master, so I pulled the x86 changes and applied
all. Ingo, this will mean you have to push x86 before kvm.git, but as
you're generally faster than me there shouldn't be a problem.
Eduardo, please check the merge (there was a small conflict in reboot.c
which I fixed) once I push it. Also, when generating patches that move
files, use the -M switch: this makes it easier to review, and also
handles files that change better.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-11-21 16:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 21:03 [PATCH 00/12] x86: disable virt on kdump and emergency_restart (v4) Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 01/12] kvm: vmx: move vmx.h to include/asm Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 02/12] kvm: svm: move svm.h " Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 03/12] kvm: vmx: move ASM_VMX_* definitions from asm/kvm_host.h to asm/vmx.h Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 04/12] kvm: vmx: move cpu_has_kvm_support() to an inline on asm/virtext.h Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 05/12] x86: asm/virtext.h: add cpu_vmxoff() inline function Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 06/12] kvm: vmx: extract kvm_cpu_vmxoff() from hardware_disable() Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 07/12] x86: cpu_emergency_vmxoff() function Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 08/12] kvm: svm: move has_svm() code to asm/virtext.h Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 09/12] kvm: svm: move svm_hardware_disable() " Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 10/12] x86: cpu_emergency_svm_disable() function Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 11/12] kdump: forcibly disable VMX and SVM on machine_crash_shutdown() Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-17 21:03 ` [PATCH 12/12] x86: disable VMX on all CPUs on reboot Eduardo Habkost
2008-11-17 21:03 ` Eduardo Habkost
2008-11-18 8:15 ` [PATCH 00/12] x86: disable virt on kdump and emergency_restart (v4) Ingo Molnar
2008-11-18 8:15 ` Ingo Molnar
2008-11-18 8:15 ` Ingo Molnar
2008-11-21 16:07 ` Avi Kivity [this message]
2008-11-21 16:07 ` Avi Kivity
2008-11-21 16:07 ` Avi Kivity
2008-11-21 16:18 ` Ingo Molnar
2008-11-21 16:18 ` Ingo Molnar
2008-11-21 16:18 ` Ingo Molnar
2008-11-24 14:58 ` Eduardo Habkost
2008-11-24 14:58 ` Eduardo Habkost
2008-11-24 14:58 ` 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=4926DCC8.1040500@redhat.com \
--to=avi@redhat.com \
--cc=akpm@osdl.org \
--cc=arvidjaar@mail.ru \
--cc=ebiederm@xmission.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=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=vgoyal@redhat.com \
--cc=zach@vmware.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.