From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
AndrewCooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: xen/arm: Domain not fully destroyed when using credit2
Date: Thu, 30 Mar 2017 09:38:44 +0200 [thread overview]
Message-ID: <1490859524.25397.15.camel@citrix.com> (raw)
In-Reply-To: <2a851699-f9ff-bcba-56b5-564f10e52866@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]
On Tue, 2017-03-28 at 19:30 +0100, Julien Grall wrote:
> Hi Dario,
>
Hey,
> On 02/02/17 13:32, Dario Faggioli wrote:
> > On Thu, 2017-02-02 at 13:26 +0000, Julien Grall wrote:
> > >
> > Ok, sign me up for it then. We absolutely want it for 4.9, I agree.
>
> Do you have any update on this? This would allow us to use credit 2
> on
> ARM when physical processor are idle.
>
Yes, sorry for the delay. I've started working on this, and I have it
half done, but then had to switch to something else. I most likely will
be able to get back to it tomorrow, and finish and send something soon.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-30 7:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 19:42 xen/arm: Domain not fully destroyed when using credit2 Julien Grall
2017-01-24 0:16 ` Stefano Stabellini
2017-01-24 12:52 ` Julien Grall
2017-01-24 8:20 ` Jan Beulich
2017-01-24 10:50 ` Julien Grall
2017-01-24 11:02 ` Jan Beulich
2017-01-24 12:30 ` Julien Grall
2017-01-24 12:53 ` Dario Faggioli
2017-01-24 13:04 ` Julien Grall
2017-01-24 13:05 ` Julien Grall
2017-01-24 13:19 ` Dario Faggioli
2017-01-24 13:24 ` Julien Grall
2017-01-24 13:40 ` Dario Faggioli
2017-01-24 13:49 ` Julien Grall
2017-01-24 14:16 ` Dario Faggioli
2017-01-24 15:06 ` Julien Grall
2017-01-25 11:10 ` Dario Faggioli
2017-01-25 12:38 ` Julien Grall
2017-01-25 12:40 ` Andrew Cooper
2017-01-25 14:23 ` Julien Grall
2017-01-25 16:00 ` Dario Faggioli
2017-01-31 16:30 ` Julien Grall
2017-01-31 22:10 ` Stefano Stabellini
2017-02-01 18:21 ` Wei Liu
2017-02-02 11:22 ` Jan Beulich
2017-02-02 11:53 ` Wei Liu
2017-02-02 12:18 ` Julien Grall
2017-02-02 12:51 ` Dario Faggioli
2017-02-02 13:26 ` Julien Grall
2017-02-02 13:32 ` Dario Faggioli
2017-03-28 18:30 ` Julien Grall
2017-03-30 7:38 ` Dario Faggioli [this message]
2017-02-02 12:01 ` Dario Faggioli
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=1490859524.25397.15.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@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 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.