From: Simon Martin <furryfuttock@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Consuming PCI device in PV kernel
Date: Tue, 15 Jul 2014 09:37:56 +0100 [thread overview]
Message-ID: <1803824698.20140715093756@gmail.com> (raw)
In-Reply-To: <1405097274.29306.545.camel@Solace>
Hello Dario,
> BTW, how's this going (if I can ask)? Any exciting news about this you
> can share with the community? :-)
Nothing exciting I'm afraid, just lots of donkey work. The
micropv project (similar to the Xen mini-os but a LOT lighter with no
dynamic memory, paging etc) is coming along nicely. Lots of
improvements about talking to the hypervisor and xenstore and
making it more implementation agnostic. The mirage-os guys seemed to
be interested in this when I first mentioned it. No idea if they still
are, it's been a while. Too many projects, too little time ;-)
My PV OS is sitting quite nicely in the hypervisor and I have my
context switch running nicely within the micropv. One problem I
haven't been able to work around so far is implementing lazy FP
context recovery, I do it on every context switch. This is crazy but I
get FP exceptions if I don't. As I have larger fish to fry, this one
is just flagged as something to come back to.
I had to modify one of the existing Linux kernel drivers (gntalloc) to
provide more functionality. I got it to a state in which it was
accepted by Daniel De Graaf the original implementor. I now have to
push it upstream the Linux kernel maintainers.
As a general comment I find that the existing Xen documentation is
fine for handling existing HVM/PV domain implementations, but you are
on your own when it comes to implementing your own PV. If it wasn't
for the good will of the people on this mailing list I would never
have been able to get where I am now. I know that I am in a small
niche here, and the existing documentation is fine for 99% of people
who are using Xen. If this is something that should be documented then
I would be willing to have a stab at writing some wiki pages if
someone can clean up the things that I have misunderstood.
Regards, and once again, a big thanks to everyone
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-07-15 8:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 11:13 Consuming PCI device in PV kernel Simon Martin
2014-07-03 18:09 ` Konrad Rzeszutek Wilk
2014-07-07 8:21 ` Simon Martin
2014-07-07 11:22 ` Simon Martin
2014-07-07 12:21 ` Realtime access to PCI NIC Simon Martin
2014-07-08 14:46 ` Ian Campbell
2014-07-10 7:47 ` Simon Martin
2014-07-08 15:01 ` Consuming PCI device in PV kernel Konrad Rzeszutek Wilk
2014-07-10 7:54 ` Simon Martin
2014-07-11 16:47 ` Dario Faggioli
2014-07-15 8:37 ` Simon Martin [this message]
2014-07-15 14:56 ` Konrad Rzeszutek Wilk
2014-07-18 14:37 ` Simon Martin
2014-07-18 19:09 ` Konrad Rzeszutek Wilk
2014-07-21 10:13 ` Simon Martin
2014-07-21 10:53 ` Ian Campbell
2014-07-25 12:56 ` Simon Martin
2014-07-25 13:10 ` Ian Campbell
2014-07-25 13:21 ` Simon Martin
2014-07-25 13:37 ` Ian Campbell
2014-07-25 13:50 ` Andrew Cooper
2014-07-25 14:20 ` Simon Martin
2014-07-25 14:25 ` Andrew Cooper
2014-07-25 14:30 ` Simon Martin
2014-07-25 14:33 ` Ian Campbell
2014-07-25 14:36 ` Simon Martin
2014-07-25 14:28 ` Simon Martin
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=1803824698.20140715093756@gmail.com \
--to=furryfuttock@gmail.com \
--cc=dario.faggioli@citrix.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).