From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ben Guthro <benjamin.guthro@citrix.com>,
mirageos-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
lars.kurth@xen.org, Paul Durrant <paul.durrant@citrix.com>,
Santosh Jodh <Santosh.Jodh@citrix.com>,
"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014
Date: Wed, 5 Feb 2014 14:49:01 +0000 [thread overview]
Message-ID: <52F24F5D.7020207@citrix.com> (raw)
In-Reply-To: <1391611558.23098.2.camel@kazak.uk.xensource.com>
On 05/02/14 14:45, Ian Campbell wrote:
> On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
>> On 05/02/14 14:09, Ian Campbell wrote:
>>> Andy:
>>>
>>> * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>>> allocations
>>>
>>> Sounds too hard for a GSoC to me. Would need fleshing out in any
>>> case.
>> Malcolm made a prototype for this on the first day of the Hackathon. It
>> can disappear.
> Removed.
>
>>> * CPU/RAM/PCI diagram tool
>>>
>>> Does this not already exist somewhere?
>> Not as far as I (or my ability to google) am aware.
>>
>> My furrowing into hwloc interacting with Xen and libxc is a start to all
>> of this, but it is still very much in my copious free time and there is
>> more than enough other work which could be done if someone were interested.
> OK, left in place.
>
> This could conceivably be done under another umbrella such as the Linux
> one too, since it seems generic.
>
> Ian.
>
>
For native Linux, hwloc kinda already does this already - certainly the
CPU and PCI bits. Under Xen there are quite a few areas needing
improvement, which will require active development work.
~Andrew
next prev parent reply other threads:[~2014-02-05 14:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52DCE9FA.6010400@xen.org>
2014-01-28 13:54 ` Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Lars Kurth
[not found] ` <52E7B6AF.3050604@xen.org>
2014-02-05 14:09 ` Ian Campbell
2014-02-05 14:18 ` Ben Guthro
2014-02-05 14:29 ` Konrad Rzeszutek Wilk
2014-02-05 14:30 ` Ian Campbell
2014-02-05 14:34 ` Konrad Rzeszutek Wilk
2014-02-05 14:42 ` Ian Campbell
2014-02-05 14:40 ` Andrew Cooper
2014-02-05 14:45 ` Ian Campbell
2014-02-05 14:49 ` Andrew Cooper [this message]
2014-02-05 14:52 ` Ian Campbell
2014-02-14 1:35 ` Lars Kurth
2014-02-06 11:15 ` George Dunlap
2014-02-06 16:44 ` Santosh Jodh
2014-02-06 17:43 ` Paul Durrant
2014-02-06 17:44 ` Ian Campbell
2014-02-06 17:47 ` Paul Durrant
2014-02-12 16:37 ` Roger Pau Monné
2014-02-13 17:13 ` Ian Jackson
2014-02-17 15:15 ` Lars Kurth
2014-02-17 15:39 ` Lars Kurth
2014-02-13 16:11 ` [MirageOS-devel] " David Scott
[not found] ` <CAG_esB0qq7G41GTX08n7g2Y+YXxtrLULftmvcTML-ueu9WP7yA@mail.gmail.com>
2014-02-13 19:41 ` Lars Kurth
[not found] <mailman.8661.1392343770.24322.xen-devel@lists.xen.org>
[not found] ` <B00D7549-3E17-4A58-924B-7C640EA70755@gridcentric.ca>
2014-02-14 23:43 ` Lars Kurth
2014-01-20 9:18 Lars Kurth
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=52F24F5D.7020207@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Santosh.Jodh@citrix.com \
--cc=benjamin.guthro@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=lars.kurth@xen.org \
--cc=mirageos-devel@lists.xenproject.org \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-api@lists.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.