From: Peng Fan <van.freenix@gmail.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Ian Campbell <ian.campbell@citrix.com>,
Michael Turquette <mturquette@baylibre.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Julien Grall <julien.grall@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-clk@vger.kernel.org
Subject: Re: [Xen-devel] [RFC/WIP] xen: clk: introudce pvclk for device passthrough
Date: Tue, 19 Jan 2016 09:18:08 +0800 [thread overview]
Message-ID: <20160119011806.GA12932@linux-7smt.suse> (raw)
In-Reply-To: <CAFLBxZa9W6At5M_fFy17u__C_AGHRAdYHebOzymnb1su715jzA@mail.gmail.com>
Hello George,
On Mon, Jan 18, 2016 at 11:22:44AM +0000, George Dunlap wrote:
>On Sat, Jan 16, 2016 at 5:22 AM, Peng Fan <van.freenix@gmail.com> wrote:
>> This patch was just a initial patch, not sure whether this way
>> is ok from you side for handlding clk when doing platform device
>> passhthrough. Any comments are appreciated, and your comments may
>> give me a better direction.
>
>Hey Peng,
>
>Just speaking from the perspective of a Xen dev who's not an ARM dev:
>a few more words on the relationship between pvclk and
>device-passthrough would be helpful to set the context. It sounds
>like:
>
>* On ARM, passing through a device requires a clocksource (at least
>for many devices)
>
>* dom0 has the hardware clocksource, but at the moment domUs don't
>have a suitable clocksource
>
>* This patch implements pvclk front/backend suitable for such devices
>
>Is that right? In which case something like the following would be helpful:
Yeah. right. You have a better explaination than me :)
>
>"This patch introduces pvclk, a paravirtualized clock source suitable
>for devices to use when passing through to domUs on ARM systems."
>
>(Obviously change it as necessary to make it accurate.)
I'll add your words into the commit log.
Thanks,
Peng.
>
>Thanks,
> -George
next prev parent reply other threads:[~2016-01-19 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 5:22 [RFC/WIP] xen: clk: introudce pvclk for device passthrough Peng Fan
2016-01-18 11:22 ` [Xen-devel] " George Dunlap
2016-01-19 1:18 ` Peng Fan [this message]
2016-01-18 11:24 ` David Vrabel
2016-01-18 12:41 ` Ian Campbell
2016-01-19 2:43 ` Peng Fan
2016-01-19 10:06 ` Ian Campbell
2016-01-19 1:33 ` Peng Fan
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=20160119011806.GA12932@linux-7smt.suse \
--to=van.freenix@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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