From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] ppc: Generalize the kvmppc_get_clockfreq() function
Date: Wed, 12 Oct 2011 16:19:16 +0200 [thread overview]
Message-ID: <4E95A1E4.1060000@suse.de> (raw)
In-Reply-To: <1318307461-9817-1-git-send-email-david@gibson.dropbear.id.au>
On 10/11/2011 06:31 AM, David Gibson wrote:
> Currently the kvmppc_get_clockfreq() function reads the host's clock
> frequency from /proc/device-tree, which is useful to past to the guest
> in KVM setups. However, there are some other host properties
> advertised in the device tree which can also be relevant to the
> guests.
>
> This patch, therefore, replaces kvmppc_get_clockfreq() which can
> retrieve any named, single integer property from the host device
> tree's CPU node.
>
> Signed-off-by: David Gibson<david@gibson.dropbear.id.au>
Thanks, applied both patches to ppc-next.
Alex
prev parent reply other threads:[~2011-10-12 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 4:31 [Qemu-devel] [PATCH 1/2] ppc: Generalize the kvmppc_get_clockfreq() function David Gibson
2011-10-11 4:31 ` [Qemu-devel] [PATCH 2/2] pseries: Add device tree properties for VMX/VSX and DFP under kvm David Gibson
2011-10-12 14:17 ` Alexander Graf
2011-10-12 14:19 ` Alexander Graf [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=4E95A1E4.1060000@suse.de \
--to=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.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).