public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Julian Stecklina <js@alien8.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Don't mistreat edge-triggered INIT IPI as INIT de-assert. (LAPIC)
Date: Fri, 23 Dec 2011 15:07:21 +0100	[thread overview]
Message-ID: <1324649241.15135.19.camel@tabernacle.lan> (raw)
In-Reply-To: <20111223104031.GB24308@amt.cnet>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

On Fr, 2011-12-23 at 08:40 -0200, Marcelo Tosatti wrote:
> On Mon, Dec 19, 2011 at 02:14:27AM +0100, Julian Stecklina wrote:
> > If the guest programs an IPI with level=0 (de-assert) and trig_mode=0 (edge),
> > it is erroneously treated as INIT de-assert and ignored, but to quote the
> > spec: "For this delivery mode [INIT de-assert], the level flag must be set to
> > 0 and trigger mode flag to 1."
> 
> Yes, the implementation ignores INIT de-assert. Quoting the spec:
> 
> "(INIT Level De-assert) (Not supported in the Pentium 4 and Intel Xeon
> processors.)"
> 
> Your patch below is not improving the implementation to be closer to the
> spec: it'll trigger the INIT state initialization with trig_mode == 0
> (which is not in accordance with your spec quote above).

I think our code that triggers this does weird things. Let me check
that. Until then ignore that patch and sorry for the noise. :) At least
it seems as if real hardware is interpreting the spec in a slightly
different way...

Regards, Julian


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-12-23 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19  1:14 [PATCH] KVM: Don't mistreat edge-triggered INIT IPI as INIT de-assert. (LAPIC) Julian Stecklina
2011-12-23 10:40 ` Marcelo Tosatti
2011-12-23 14:07   ` Julian Stecklina [this message]
2012-01-12 17:07   ` Julian Stecklina
2012-01-13 10:52     ` Marcelo Tosatti
2012-01-13 11:46       ` Julian Stecklina
2012-01-16 10:18         ` Marcelo Tosatti
2012-01-16 13:02           ` js
2012-01-24 11:09             ` Marcelo Tosatti

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=1324649241.15135.19.camel@tabernacle.lan \
    --to=js@alien8.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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