kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Arthur Chunqi Li <yzt356@gmail.com>,
	kvm@vger.kernel.org, gleb@redhat.com, "Zhang,
	Yang Z" <yang.z.zhang@intel.com>
Subject: Re: [PATCH v5] KVM: nVMX: Fully support of nested VMX preemption timer
Date: Fri, 25 Oct 2013 10:56:35 +0100	[thread overview]
Message-ID: <526A4053.50500@redhat.com> (raw)
In-Reply-To: <5256D3DB.7090107@redhat.com>

Il 10/10/2013 17:20, Paolo Bonzini ha scritto:
>> > Arthur, find some fix-ups for your test case below. It avoids printing
>> > from within L2 as this could deadlock when the timer fires and L1 then
>> > tries to print something. Also, it disables the preemption timer on
>> > leave so that it cannot fire later on again. If you want to fold this
>> > into your patch, feel free. Otherwise I can post a separate patch on
>> > top.
> Is that a Signed-off-by? :)

Ping?

Paolo

  reply	other threads:[~2013-10-25  9:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16  8:11 [PATCH v5] KVM: nVMX: Fully support of nested VMX preemption timer Arthur Chunqi Li
2013-09-22  7:47 ` Gleb Natapov
2013-09-25 13:58 ` Paolo Bonzini
2013-09-26 15:04 ` Paolo Bonzini
2013-09-26 17:19   ` Jan Kiszka
2013-09-26 17:47     ` Paolo Bonzini
2013-09-26 20:44       ` Paolo Bonzini
2013-09-27  6:37         ` Jan Kiszka
2013-09-29 16:24           ` Jan Kiszka
2013-09-29 11:30       ` Gleb Natapov
2013-09-30  9:08   ` Jan Kiszka
2013-10-02 18:47     ` Jan Kiszka
2013-10-10 16:12       ` Jan Kiszka
2013-10-10 16:20         ` Paolo Bonzini
2013-10-25  9:56           ` Paolo Bonzini [this message]
2013-10-25  9:59             ` Jan Kiszka
2013-10-11  8:17         ` Arthur Chunqi Li
2013-10-03  8:09     ` 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=526A4053.50500@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=yang.z.zhang@intel.com \
    --cc=yzt356@gmail.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;
as well as URLs for NNTP newsgroup(s).