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 v2] x86: Remove INIT deassertg
Date: Mon, 15 Apr 2019 15:27:21 -0700 [thread overview]
Message-ID: <20190415222721.GN24010@linux.intel.com> (raw)
In-Reply-To: <20190415221421.20903-1-nadav.amit@gmail.com>
On Mon, Apr 15, 2019 at 03:14:21PM -0700, nadav.amit@gmail.com wrote:
> From: Nadav Amit <nadav.amit@gmail.com>
>
> Currently, the INIT deassert is marked as an edge event instead of a
> level, which is wrong. The deassert is actually not needed, as the
> arbitration ID should have already been set after boot, and is not
> affected by further INIT IPIs.
>
> Remove the INIT deassert for these reasons.
>
> Cc: Sean Christopherson <sean.j.christopherson@intel.com>
> Signed-off-by: Nadav Amit <nadav.amit@gmail.com>
> ---
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
next prev parent reply other threads:[~2019-04-15 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 22:14 [kvm-unit-tests PATCH v2] x86: Remove INIT deassert nadav.amit
2019-04-15 22:27 ` Sean Christopherson [this message]
2019-04-16 8:28 ` [kvm-unit-tests PATCH v2] x86: Remove INIT deassertg Paolo Bonzini
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=20190415222721.GN24010@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