All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCH] x86: kvm: reset the bootstrap processor when it gets an INIT
Date: Mon, 11 Mar 2013 20:01:30 +0100	[thread overview]
Message-ID: <513E2A0A.3080008@siemens.com> (raw)
In-Reply-To: <20130311185132.GB14689@redhat.com>

On 2013-03-11 19:51, Gleb Natapov wrote:
>>> On Intel:
>>> CPU 1                          CPU 2 in a guest mode
>>> send INIT
>>> send SIPI
>>>                                 INIT vmexit
>>>                                 vmxoff
>>>                                 reset and start from SIPI vector
>>
>> Is SIPI sticky as well, even if the CPU is not in the wait-for-SIPI
>> state (but runnable and in vmxon) while receiving it?
>>
> That what they seams to be saying:
>  However, an INIT and SIPI interrupts sent to a CPU during time when
>  it is in a VMX mode are remembered and delivered, perhaps hours later,
>  when the CPU exits the VMX mode
> 
> Otherwise their exploit will not work.

Very weird, specifically as SIPI is not just a binary event but carries
payload. Will another SIPI event overwrite the previously "saved"
vector? We are deep into an underspecified area...

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-03-11 19:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09  6:48 [PATCH] x86: kvm: reset the bootstrap processor when it gets an INIT Paolo Bonzini
2013-03-10 11:46 ` Gleb Natapov
2013-03-10 14:53   ` Paolo Bonzini
2013-03-10 15:35     ` Gleb Natapov
2013-03-10 17:19       ` Paolo Bonzini
2013-03-10 18:10         ` Gleb Natapov
2013-03-11 10:14           ` Paolo Bonzini
2013-03-11 10:28             ` Gleb Natapov
2013-03-11 11:25               ` Paolo Bonzini
2013-03-11 11:51                 ` Gleb Natapov
2013-03-11 13:31                   ` Paolo Bonzini
2013-03-11 13:54                     ` Gleb Natapov
2013-03-11 14:01                       ` Jan Kiszka
2013-03-11 14:05                         ` Gleb Natapov
2013-03-11 14:06                           ` Jan Kiszka
2013-03-11 14:09                             ` Gleb Natapov
2013-03-11 14:10                               ` Jan Kiszka
2013-03-11 14:12                                 ` Gleb Natapov
2013-03-11 14:19                                   ` Jan Kiszka
2013-03-11 14:23                           ` Paolo Bonzini
2013-03-11 15:36                             ` Jan Kiszka
2013-03-11 17:23                               ` Gleb Natapov
2013-03-11 17:34                                 ` Jan Kiszka
2013-03-11 17:38                                   ` Jan Kiszka
2013-03-11 17:41                                   ` Gleb Natapov
2013-03-11 18:05                                     ` Jan Kiszka
2013-03-11 18:13                                       ` Gleb Natapov
2013-03-11 18:27                                         ` Jan Kiszka
2013-03-11 18:39                                           ` Gleb Natapov
2013-03-11 18:47                                             ` Jan Kiszka
2013-03-11 18:51                                               ` Gleb Natapov
2013-03-11 19:01                                                 ` Jan Kiszka [this message]
2013-03-11 19:30                                                   ` Gleb Natapov
2013-03-12  9:25                                                     ` Jan Kiszka
2013-03-12 11:28                                                       ` Gleb Natapov
2013-03-11 14:28                       ` Paolo Bonzini
2013-03-11 17:20                         ` Gleb Natapov
2013-03-11 17:39                           ` Paolo Bonzini
2013-03-11 18:04                             ` Gleb Natapov

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=513E2A0A.3080008@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.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 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.