From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] expose async pf through our standard mechanism
Date: Thu, 24 Mar 2011 12:41:06 +0200 [thread overview]
Message-ID: <4D8B1FC2.8050305@redhat.com> (raw)
In-Reply-To: <1300898442-13704-1-git-send-email-glommer@redhat.com>
On 03/23/2011 06:40 PM, Glauber Costa wrote:
> As Avi recently mentioned, the new standard mechanism for exposing features
> is KVM_GET_SUPPORTED_CPUID, not spanning CAPs. For some reason async pf missed that.
>
> So expose async_pf here.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-03-24 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 16:40 [PATCH] expose async pf through our standard mechanism Glauber Costa
2011-03-24 10:41 ` Avi Kivity [this message]
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=4D8B1FC2.8050305@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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