From: Marcelo Tosatti <mtosatti@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: kvm@vger.kernel.org, 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 15:27:30 -0200 [thread overview]
Message-ID: <20141210172730.GB20568@amt.cnet> (raw)
In-Reply-To: <54887E6C.8060708@redhat.com>
On Wed, Dec 10, 2014 at 12:10:04PM -0500, Rik van Riel wrote:
> 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?
What issue?
next prev parent reply other threads:[~2014-12-10 17:27 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
2014-12-10 17:27 ` Marcelo Tosatti [this message]
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=20141210172730.GB20568@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox