All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>,
	Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
	xen-devel@lists.xen.org, Stefano.Stabellini@citrix.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [RFC PATCH 11/13] cpufreq: add xen-cpufreq driver
Date: Fri, 10 Oct 2014 16:19:13 +0100	[thread overview]
Message-ID: <1412954353.27111.50.camel@citrix.com> (raw)
In-Reply-To: <5437F25A020000780003DB8D@mail.emea.novell.com>

On Fri, 2014-10-10 at 13:51 +0100, Jan Beulich wrote:
> >>> On 10.10.14 at 11:59, <Ian.Campbell@citrix.com> wrote:
> > A simple i2c driver (without all the generic framework/bus
> > infrastructure which Linux has) is pretty simple.
> > 
> > I think the biggest complexity would come from i2c busses with both
> > cpufreq and other devices on them and managing the potentially shared
> > accesses.
> 
> And the recently added XENPF_resource_op would seem a pretty
> good candidate for this (except that it requires the Dom0 kernel
> code to stop accessing hardware directly, and instead go through
> this hypercall).

We'd need to introduce a dtb binding for a "pv i2c host controller"
which we would use to replace the actual one for dom0. That might be
doable I think, so long as we take care to preserve the relationships
with other nodes which might reference it.

Ian.

  parent reply	other threads:[~2014-10-10 15:19 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 14:19 [RFC PATCH 00/13] xen_cpufreq implementation in Xen hypervisor Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 01/13] cpufreq: move cpufreq.h file to the xen/include/cpufreq location Oleksandr Dmytryshyn
2014-10-07 14:22   ` Andrew Cooper
2014-10-07 14:27     ` Oleksandr Dmytryshyn
2014-10-07 14:35   ` Jan Beulich
2014-10-09  6:04     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 02/13] pm: move processor_perf.h " Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 03/13] pmstat: move pmstat.c file to the xen/drivers/pm location Oleksandr Dmytryshyn
2014-10-07 14:38   ` Jan Beulich
2014-10-09  6:05     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 04/13] cpufreq: use turbo settings only for x86 architecture Oleksandr Dmytryshyn
2014-10-07 14:39   ` Jan Beulich
2014-10-09  6:05     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 05/13] pmstat: make pmstat functions more generalizable Oleksandr Dmytryshyn
2014-10-07 14:40   ` Jan Beulich
2014-10-09  6:06     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 06/13] cpufreq: make cpufreq driver " Oleksandr Dmytryshyn
2014-10-07 14:42   ` Jan Beulich
2014-10-09  6:06     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 07/13] xen/arm: enable cpu hotplug Oleksandr Dmytryshyn
2014-10-07 15:15   ` Julien Grall
2014-10-09  6:07     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 08/13] xen/dts: make the dt_find_property function to be global Oleksandr Dmytryshyn
2014-10-07 15:09   ` Julien Grall
2014-10-09  6:09     ` Oleksandr Dmytryshyn
2014-10-09 11:15       ` Julien Grall
2014-10-09 11:40         ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 09/13] arch/arm: create device tree nodes for Dom0 cpufreq cpu driver Oleksandr Dmytryshyn
2014-10-07 15:26   ` Julien Grall
2014-10-09  6:10     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 10/13] xen: arm: implement platform hypercall Oleksandr Dmytryshyn
2014-10-07 15:39   ` Julien Grall
2014-10-09  6:11     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 11/13] cpufreq: add xen-cpufreq driver Oleksandr Dmytryshyn
2014-10-07 14:44   ` Jan Beulich
2014-10-08 13:51     ` Stefano Stabellini
2014-10-10  9:00       ` Jan Beulich
2014-10-10  9:04         ` Stefano Stabellini
2014-10-10  9:39       ` Jan Beulich
2014-10-10  9:39         ` Stefano Stabellini
2014-10-10  9:46           ` Jan Beulich
2014-10-10  9:54             ` Stefano Stabellini
2014-10-10  9:59               ` Ian Campbell
2014-10-10 12:51                 ` Jan Beulich
2014-10-10 14:42                   ` Stefano Stabellini
2014-10-13  8:56                     ` Oleksandr Dmytryshyn
2014-10-13  9:39                       ` Jan Beulich
2014-10-13 11:59                         ` Oleksandr Dmytryshyn
2014-10-13 12:28                           ` Jan Beulich
2014-10-13 13:38                             ` Andrii Tseglytskyi
2014-10-13 14:11                               ` Jan Beulich
2014-10-13 14:29                                 ` Andrii Tseglytskyi
2014-10-14 12:20                                   ` Jan Beulich
2014-10-14 12:39                                     ` Andrii Tseglytskyi
2014-10-14 12:51                                     ` Stefano Stabellini
2014-10-14 12:58                                       ` Andrii Tseglytskyi
2014-10-14 13:00                                         ` Andrii Tseglytskyi
2014-10-14 13:05                                           ` Ian Campbell
2014-10-14 13:07                                             ` Andrii Tseglytskyi
2014-10-15 10:55                                               ` Stefano Stabellini
2014-10-15 11:17                                                 ` Andrii Tseglytskyi
2014-10-15 12:34                                                   ` Ian Campbell
2014-10-15 16:26                                                   ` Jan Beulich
2014-10-10 15:19                   ` Ian Campbell [this message]
2014-10-10 10:40               ` Jan Beulich
2014-10-09  6:13     ` Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 12/13] xen: arm: implement XEN_SYSCTL_cpufreq_op Oleksandr Dmytryshyn
2014-10-07 14:19 ` [RFC PATCH 13/13] xen/arm: enable cpufreq functionality for ARM Oleksandr Dmytryshyn
2014-10-07 14:34 ` [RFC PATCH 00/13] xen_cpufreq implementation in Xen hypervisor Jan Beulich

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=1412954353.27111.50.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@citrix.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.