From: Rik van Riel <riel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Radim Krcmar <rkrcmar@redhat.com>
Subject: Re: [patch 1/2] KVM: x86: add method to test PIR bitmap vector
Date: Wed, 10 Dec 2014 12:10:04 -0500 [thread overview]
Message-ID: <54887E6C.8060708@redhat.com> (raw)
In-Reply-To: <20141210170617.793497193@redhat.com>
On 12/10/2014 12:06 PM, Marcelo Tosatti wrote:
> kvm_x86_ops->test_posted_interrupt() returns true/false depending
> whether 'vector' is set.
Is that good? Bad? How does this patch address the issue?
next prev parent reply other threads:[~2014-12-10 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:06 [patch 0/2] KVM: add option to advance tscdeadline hrtimer expiration (v2) Marcelo Tosatti
2014-12-10 17:06 ` [patch 1/2] KVM: x86: add method to test PIR bitmap vector Marcelo Tosatti
2014-12-10 17:10 ` Rik van Riel [this message]
2014-12-10 17:27 ` Marcelo Tosatti
2014-12-10 17:50 ` Rik van Riel
2014-12-10 17:57 ` Marcelo Tosatti
2014-12-10 17:06 ` [patch 2/2] KVM: x86: add option to advance tscdeadline hrtimer expiration Marcelo Tosatti
2014-12-10 17:11 ` Rik van Riel
2014-12-10 17:10 ` [patch 0/2] KVM: add option to advance tscdeadline hrtimer expiration (v2) Paolo Bonzini
2014-12-10 17:27 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 20:57 [patch 0/2] KVM: add option to advance tscdeadline hrtimer expiration (v3) Marcelo Tosatti
2014-12-10 20:57 ` [patch 1/2] KVM: x86: add method to test PIR bitmap vector Marcelo Tosatti
2014-12-10 16:53 [patch 0/2] KVM: add option to advance tscdeadline hrtimer expiration Marcelo.Tosatti
2014-12-10 16:53 ` [patch 1/2] KVM: x86: add method to test PIR bitmap vector 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=54887E6C.8060708@redhat.com \
--to=riel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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.