From: Vitaly Chernooky <vitalii.chernookyi@globallogic.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Vitaly V. Ch" <vitaly.v.ch@chernooky.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: cpufreq implementation for OMAP under xen hypervisor.
Date: Fri, 22 Aug 2014 17:21:34 +0300 [thread overview]
Message-ID: <CANZZXhA9PM6yJNT+uoJJ7XbAtBiBnBq0NSoh3uSevH2FWsP_rQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408220003520.8032@kaball.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2517 bytes --]
On Fri, Aug 22, 2014 at 2:05 AM, Stefano Stabellini <
stefano.stabellini@eu.citrix.com> wrote:
> It is not stupid, it is actually possible to do it that way.
>
> It would be similar to do cpufreq in dom0: anything you can run in Dom0,
> you can also run separately in a little stubdom.
>
> However I think that it would be best to do it in Xen.
>
Ok, what the reason is to prefer to do cpufreq in Xen?
With driver domain we can once provide stable binary ABI for cpufreq and do
not have any confusion with sources, patches and branches. If we will do
cpufreq in Xen I expect in the nearest future large amount of patches for
cpufreq for wide variety of ARM platforms.
With best regards,
>
> On Tue, 19 Aug 2014, Vitaly V. Ch wrote:
> > Hi Stefano,
> >
> > What do you think about implementation cpufreq driver as stub driver
> domain?
> >
> > Just now I'm not familar enought with latest XEN fetures so my question
> can be a little stupid :)
> >
> > With best regards,
> >
> > Vitaly
> >
> >
> > On Tue, Aug 12, 2014 at 3:15 PM, Stefano Stabellini <
> stefano.stabellini@eu.citrix.com> wrote:
> > On Tue, 12 Aug 2014, Oleksandr Dmytryshyn wrote:
> > > Hi to all.
> > >
> > > I want to implement an cpufreq support for OMAP processors in
> xen. I
> > > use the Linux kernel as Dom0.
> > >
> > > I know that there are 2 implementations of cpufreq: Domain0 based
> > > cpufreq and Hypervisor based cpufreq. But those implementations
> are
> > > made only for x86 architecture, not for the ARM architecture.
> > >
> > > Could anybody give me an advise how to do that?
> >
> > I think that the best way would be to introduce cpufreq support directly
> > in the Xen hypervisor. I would:
> >
> > 1) get cpufreq (xen/drivers/cpufreq) to build and run on ARM, with a
> dummy driver
> > although the cpufreq infrastructure has been written with x86 in mind,
> > it should be generalizable
> >
> > 2) write a cpufreq driver for OMAP
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >
> >
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
--
*Vitaly Chernooky | Senior Developer - Product Engineering and Development*
GlobalLogic
P *+380.44.4929695 ext.1136* M *+380.98.7920568* S cvv_2k
www.globallogic.com
http://www.globallogic.com/email_disclaimer.txt
[-- Attachment #1.2: Type: text/html, Size: 4038 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-08-22 14:21 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 10:57 cpufreq implementation for OMAP under xen hypervisor Oleksandr Dmytryshyn
2014-08-12 12:15 ` Stefano Stabellini
2014-08-12 12:19 ` Oleksandr Dmytryshyn
2014-08-19 14:02 ` Vitaly V. Ch
2014-08-21 23:05 ` Stefano Stabellini
2014-08-22 14:21 ` Vitaly Chernooky [this message]
2014-08-22 16:20 ` Stefano Stabellini
2014-08-21 11:00 ` Oleksandr Dmytryshyn
2014-08-21 23:31 ` Stefano Stabellini
2014-08-22 9:02 ` Oleksandr Dmytryshyn
2014-08-22 16:31 ` Stefano Stabellini
2014-08-22 16:51 ` Ian Campbell
2014-08-29 13:25 ` Oleksandr Dmytryshyn
2014-08-29 15:08 ` Andrii Tseglytskyi
2014-09-02 1:00 ` Stefano Stabellini
2014-09-02 9:06 ` Vitaly Chernooky
2014-09-02 15:43 ` Andrii Tseglytskyi
2014-09-02 18:39 ` Stefano Stabellini
2014-09-02 18:46 ` Andrii Tseglytskyi
2014-09-04 14:43 ` Oleksandr Dmytryshyn
2014-09-04 21:56 ` Stefano Stabellini
2014-09-09 10:19 ` Oleksandr Dmytryshyn
2014-09-09 21:52 ` Stefano Stabellini
2014-09-09 10:32 ` Ian Campbell
2014-09-09 21:41 ` Stefano Stabellini
2014-09-10 9:42 ` Ian Campbell
2014-09-10 10:19 ` Andrii Tseglytskyi
2014-09-10 18:35 ` Stefano Stabellini
2014-09-10 19:31 ` Konrad Rzeszutek Wilk
2014-09-16 13:49 ` Oleksandr Dmytryshyn
2014-09-17 17:06 ` Konrad Rzeszutek Wilk
2014-09-18 9:38 ` Oleksandr Dmytryshyn
2014-09-18 14:59 ` Konrad Rzeszutek Wilk
2014-09-19 9:38 ` Oleksandr Dmytryshyn
2014-09-24 14:36 ` Stefano Stabellini
2014-09-24 14:46 ` Konrad Rzeszutek Wilk
2014-09-25 9:13 ` Oleksandr Dmytryshyn
2014-09-25 9:08 ` Oleksandr Dmytryshyn
2014-09-25 10:14 ` Stefano Stabellini
2014-09-25 11:15 ` Oleksandr Dmytryshyn
2014-09-26 18:13 ` Konrad Rzeszutek Wilk
2014-09-29 9:45 ` Oleksandr Dmytryshyn
2014-09-29 15:18 ` Konrad Rzeszutek Wilk
2014-09-30 10:28 ` Oleksandr Dmytryshyn
2014-09-30 17:37 ` Konrad Rzeszutek Wilk
2014-09-11 9:43 ` Ian Campbell
2014-09-09 13:25 ` Vitaly Chernooky
2014-09-09 21:58 ` Stefano Stabellini
2014-09-10 10:15 ` Andrii Tseglytskyi
2014-09-10 10:24 ` Vitaly Chernooky
2014-09-10 11:18 ` Andrii Tseglytskyi
2014-09-10 18:37 ` Stefano Stabellini
2014-09-11 7:51 ` Vitaly Chernooky
2014-09-10 11:24 ` Vitaly Chernooky
2014-09-10 14:28 ` Vitaly Chernooky
2014-09-10 18:41 ` Stefano Stabellini
2014-09-11 7:48 ` Vitaly Chernooky
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=CANZZXhA9PM6yJNT+uoJJ7XbAtBiBnBq0NSoh3uSevH2FWsP_rQ@mail.gmail.com \
--to=vitalii.chernookyi@globallogic.com \
--cc=Ian.Campbell@citrix.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vitaly.v.ch@chernooky.com \
--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 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).