From: Daniel Castro <evil.dani@gmail.com>
To: xen-devel@lists.xensource.com
Cc: Daniel Castro <evil.dani@gmail.com>
Subject: [PATCH 00/10] Xenstore communication support for Seabios
Date: Fri, 19 Aug 2011 01:03:17 +0900 [thread overview]
Message-ID: <1313683408-32306-1-git-send-email-evil.dani@gmail.com> (raw)
As part of Google Summer of Code we are in the process to add Block PV-drivers to
Seabios, in order to this, first we have to be able to communicate with xenstore
so we can exchange information before the front and back ends connect. To communicate
with xenstore we need to make seabios Xen-friendly so support for hypercalls has been
added to Seabios. In the next month, Seabios will become a front-end for the block devices,
connecting to dom0 back-end block device when used with Xen.
There is an issue, if you issue a query and the ring did not prepare the answer
fast enough, after the event signal hypercall, the ring will force a ring wait for
an event that will never arrive. For now this is solved by doing a dprintf after the
hypercall, this gives enough time to the ring.
This patch should be applied to Seabios and must be used with qemu-upstream with
xen4.1, please follow this guide for this:
http://wiki.xensource.com/xenwiki/QEMUUpstream
Some more documentation on this can be found here:
http://wiki.xensource.com/xenwiki/SeaBIOS
Daniel Castro (10):
Xen: Guest Handlers and Copyrights
Move PAGE_SHIFT to memmap.h
Xen: Use PAGE_SHIFT as a constant
Xen: Support for interdomain event channel
Xen: Support for HVM_op Hypercall
Xen: Support for memory_op Hypercall
Xen: Support for sched_op hypercall
Xen: Shared info for CPU yield support and xenbus protocol
Xen: Xenstore communication via xenbus
Xen: Xenstore example -do not apply
Makefile | 2 +-
src/bitops.h | 14 ++
src/memmap.h | 2 +
src/post.c | 2 +
src/virtio-ring.h | 2 +-
src/xen-xs.c | 251 +++++++++++++++++++++++++++++++++++++
src/xen-xs.h | 9 ++
src/xen.c | 20 +++-
src/xen.h | 357 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
9 files changed, 653 insertions(+), 6 deletions(-)
create mode 100644 src/bitops.h
create mode 100644 src/xen-xs.c
create mode 100644 src/xen-xs.h
--
1.7.4.1
next reply other threads:[~2011-08-18 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 16:03 Daniel Castro [this message]
2011-08-18 16:03 ` [PATCH 01/10] Xen: Guest Handlers and Copyrights Daniel Castro
2011-08-18 16:03 ` [PATCH 02/10] Move PAGE_SHIFT to memmap.h Daniel Castro
2011-08-24 17:51 ` Konrad Rzeszutek Wilk
2011-08-24 21:08 ` Ian Campbell
2011-08-18 16:03 ` [PATCH 03/10] Xen: Use PAGE_SHIFT as a constant Daniel Castro
2011-08-18 16:03 ` [PATCH 04/10] Xen: Support for interdomain event channel Daniel Castro
2011-08-18 16:03 ` [PATCH 05/10] Xen: Support for HVM_op Hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 06/10] Xen: Support for memory_op Hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 07/10] Xen: Support for sched_op hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 08/10] Xen: Shared info for CPU yield support and xenbus protocol Daniel Castro
2011-08-18 16:03 ` [PATCH 09/10] Xen: Xenstore communication via xenbus Daniel Castro
2011-08-18 16:03 ` [PATCH 10/10] Xen: Xenstore example -do not apply Daniel Castro
2011-08-18 16:03 ` [PATCH 10/10] Xen: Xenstore example Daniel Castro
2011-08-24 17:56 ` [PATCH 00/10] Xenstore communication support for Seabios Konrad Rzeszutek Wilk
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=1313683408-32306-1-git-send-email-evil.dani@gmail.com \
--to=evil.dani@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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).