From: Nathan Whitehorn <nwhitehorn@freebsd.org>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 3/3] KVM: PPC: Book3S HV: Implement H_CLEAR_REF and H_CLEAR_MOD
Date: Sat, 12 Sep 2015 09:47:21 -0700 [thread overview]
Message-ID: <55F45719.4000302@freebsd.org> (raw)
In-Reply-To: <20150906235243.GB2974@fergus.ozlabs.ibm.com>
On 09/06/15 16:52, Paul Mackerras wrote:
> On Sun, Sep 06, 2015 at 12:47:12PM -0700, Nathan Whitehorn wrote:
>> Anything I can do to help move these along? It's a big performance
>> improvement for FreeBSD guests.
> These patches are in Paolo's kvm-ppc-next branch and should go into
> Linus' tree in the next couple of days.
>
> Paul.
>
One additional question. What is your preferred way to enable these?
Since these are part of the mandatory part of the PAPR spec, I think
there's an argument to add them to the default_hcall_list? Otherwise,
they should be enabled by default in QEMU (I can take care of sending
that patch if you prefer this route).
-Nathan
next prev parent reply other threads:[~2015-09-12 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 5:39 [PATCH 0/3] PPC HV bug fixes + hcalls for FreeBSD Paul Mackerras
2015-04-24 5:39 ` [PATCH 1/3] KVM: PPC: Book3S HV: Fix race in reading change bit when removing HPTE Paul Mackerras
2015-04-28 5:06 ` Aneesh Kumar K.V
2015-04-28 9:10 ` Paul Mackerras
2015-04-24 5:39 ` [PATCH 2/3] KVM: PPC: Book3S HV: Fix bug in dirty page tracking Paul Mackerras
2015-04-24 5:39 ` [PATCH 3/3] KVM: PPC: Book3S HV: Implement H_CLEAR_REF and H_CLEAR_MOD Paul Mackerras
2015-07-27 17:31 ` Nathan Whitehorn
2015-09-06 19:47 ` Nathan Whitehorn
2015-09-06 23:52 ` Paul Mackerras
2015-09-07 0:46 ` Nathan Whitehorn
2015-09-12 16:47 ` Nathan Whitehorn [this message]
2015-09-12 16:51 ` Alexander Graf
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=55F45719.4000302@freebsd.org \
--to=nwhitehorn@freebsd.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@ozlabs.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;
as well as URLs for NNTP newsgroup(s).