From: Sean Christopherson <sean.j.christopherson@intel.com>
To: nadav.amit@gmail.com
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] x86: Fix INIT during boot
Date: Mon, 15 Apr 2019 13:17:12 -0700 [thread overview]
Message-ID: <20190415201712.GM24010@linux.intel.com> (raw)
In-Reply-To: <20190415191120.9472-1-nadav.amit@gmail.com>
On Mon, Apr 15, 2019 at 12:11:20PM -0700, nadav.amit@gmail.com wrote:
> From: Nadav Amit <nadav.amit@gmail.com>
>
> INIT is a level event and the trigger mode should be marked as such. In
> addition, the SDM says that INIT deassertion should specify the "all
> including-self" shorthand.
>
> Signed-off-by: Nadav Amit <nadav.amit@gmail.com>
> ---
> x86/cstart64.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/x86/cstart64.S b/x86/cstart64.S
> index 21db10f..57c3552 100644
> --- a/x86/cstart64.S
> +++ b/x86/cstart64.S
> @@ -284,8 +284,8 @@ smp_init:
> mov $(sipi_end - sipi_entry), %rcx
> rep/movsb
> mov $APIC_DEFAULT_PHYS_BASE, %eax
> - movl $(APIC_DEST_ALLBUT | APIC_DEST_PHYSICAL | APIC_DM_INIT | APIC_INT_ASSERT), APIC_ICR(%rax)
> - movl $(APIC_DEST_ALLBUT | APIC_DEST_PHYSICAL | APIC_DM_INIT), APIC_ICR(%rax)
> + movl $(APIC_DEST_ALLBUT | APIC_DEST_PHYSICAL | APIC_DM_INIT | APIC_INT_ASSERT | APIC_INT_LEVELTRIG), APIC_ICR(%rax)
> + movl $(APIC_DEST_ALLINC | APIC_DEST_PHYSICAL | APIC_DM_INIT | APIC_INT_LEVELTRIG), APIC_ICR(%rax)
Level vs. Edge is ignored for everything except the de-assert IPI, i.e. it's
just as wrong to send the INIT as level triggered.
Selects the trigger mode when using the INIT level de-assert delivery mode:
edge (0) or level (1). It is ignored for all other delivery modes. (This flag
has no meaning in Pentium 4 and Intel Xeon processors, and will always be
issued as a 0.)
And KVM simply ignores the de-assert IPI (when it's correctly formed). In
other words, we can simply remove the malformed de-assert IPI.
> movl $(APIC_DEST_ALLBUT | APIC_DEST_PHYSICAL | APIC_DM_STARTUP), APIC_ICR(%rax)
> call fwcfg_get_nb_cpus
> 1: pause
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-04-15 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 19:11 [kvm-unit-tests PATCH] x86: Fix INIT during boot nadav.amit
2019-04-15 20:17 ` Sean Christopherson [this message]
2019-04-15 21:48 ` Nadav Amit
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=20190415201712.GM24010@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@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