From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] x86: kvm: reset the bootstrap processor when it gets an INIT Date: Mon, 11 Mar 2013 15:06:18 +0100 Message-ID: <513DE4DA.4050009@siemens.com> References: <20130310153540.GL24444@redhat.com> <513CC08B.2040800@redhat.com> <20130310181035.GM24444@redhat.com> <513DAE8F.3050102@redhat.com> <20130311102852.GE31619@redhat.com> <513DBF45.9030803@redhat.com> <20130311115144.GG31619@redhat.com> <513DDCC2.9070807@redhat.com> <20130311135441.GN31619@redhat.com> <513DE3C4.5000503@siemens.com> <20130311140503.GO31619@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "mtosatti@redhat.com" To: Gleb Natapov Return-path: In-Reply-To: <20130311140503.GO31619@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 2013-03-11 15:05, Gleb Natapov wrote: > On Mon, Mar 11, 2013 at 03:01:40PM +0100, Jan Kiszka wrote: >>> We are not moving away from mp_state, we are moving away from using >>> mp_state for signaling because with nested virt INIT does not always >>> change mp_state, not only that it can change mp_state long after signal >>> is received after vmx off is done. >> >> Right. >> >> BTW, for that to happen, we will also need to influence the INIT level. >> Unless I misread the spec, INIT is blocked while in root mode, and if >> you deassert INIT before leaving root (vmxoff, vmenter), nothing >> actually happens. So what matters is the INIT signal level at the exit >> of root mode. >> > You are talking about INIT# signal received via CPU pin, right? I think > INIT send by IPI cannot go away. Why shouldn't it? Besides edge, there is also level-triggered INIT. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux