From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: Nathan Whitehorn <nwhitehorn@freebsd.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: H_CLEAR_REF and H_CLEAR_MOD
Date: Thu, 19 Feb 2015 09:00:01 +1100 [thread overview]
Message-ID: <20150218220001.GA24858@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <880391F8-5AD9-4A9A-A868-B8BEB1B1BA92@suse.de>
On Wed, Feb 18, 2015 at 09:34:54AM +0100, Alexander Graf wrote:
>
> > Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn <nwhitehorn@freebsd.org>:
> >
> > It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD hypervisor calls, which are absolutely critical for memory management in the FreeBSD kernel (and are marked "mandatory" in the PAPR manual). It seems some patches have been contributed already in https://lists.ozlabs.org/pipermail/linuxppc-dev/2011-December/095013.html, so it would be fantastic if these could end up upstream.
>
> Paul, I guess we never included this because there was no user. If FreeBSD does use it though, I think it makes a lot of sense to resend it for inclusion.
I agree. I just need to check the locking and synchronization around
the reference and change bit recording, then I'll resend it.
> >
> > I'm going to try to get some kind of workaround in the meantime so we can at least run on existing kernels.
>
> Please don't add hacks in FreeBSD only because kvm is missing a feature. Let's just get this done properly :).
Right.
Paul.
next prev parent reply other threads:[~2015-02-18 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54E42D5F.9080303@freebsd.org>
2015-02-18 8:34 ` H_CLEAR_REF and H_CLEAR_MOD Alexander Graf
2015-02-18 22:00 ` Paul Mackerras [this message]
2015-02-18 23:33 ` Nathan Whitehorn
2015-04-11 19:57 ` Nathan Whitehorn
2015-04-14 11:50 ` Paul Mackerras
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=20150218220001.GA24858@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=nwhitehorn@freebsd.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