From: Steven Smith <sos22-xen@srcf.ucam.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori <aliguori@mail.utexas.edu>,
Ewan Mellor <ewan@xensource.com>,
xen-devel <xen-devel@lists.xensource.com>,
Jeremy Katz <katzj@redhat.com>
Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support [1/5]
Date: Fri, 3 Nov 2006 17:01:35 +0000 [thread overview]
Message-ID: <20061103170135.GA5457@cam.ac.uk> (raw)
In-Reply-To: <87mz78wr4v.fsf@pike.pond.sub.org>
[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]
> I created a trivial xend/server/vfbif.py:
Looks plausible. You probably want to have a createDevice method
which calls DevController.createDevice and then spawns the backend,
but that can come later.
> I added it to xend/XendDomainInfo.py, as follows:
I think this bit is correct.
I think this should work if your SXP includes an entry for the
backend. Adding something like ``(device (vfb ()))'' to the end of
the (vm) section should work.
``xm create -n'' will convert an ordinary xm configuration file to SXP
format, and ``xm create -C'' can create a domain directly from the
SXP. Eventually, you'll want to add something to the xm parser which
makes it possible to do this without directly editting the SXP, but
that can wait for a bit.
Steven.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-11-03 17:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 19:58 [PATCH] Paravirt framebuffer frontend kernel support [1/5] Jeremy Katz
2006-09-04 9:00 ` Steven Smith
2006-09-04 14:03 ` Keir Fraser
2006-09-05 16:11 ` Jeremy Katz
2006-09-06 9:11 ` Steven Smith
2006-09-06 15:56 ` Keir Fraser
2006-09-21 18:41 ` Markus Armbruster
2006-09-21 19:29 ` Keir Fraser
2006-09-21 19:33 ` Steven Smith
2006-09-10 7:39 ` Markus Armbruster
2006-09-10 9:38 ` Steven Smith
2006-09-30 8:52 ` Markus Armbruster
2006-11-02 10:10 ` Markus Armbruster
2006-11-02 10:36 ` Ewan Mellor
2006-11-02 12:34 ` Markus Armbruster
2006-11-02 16:19 ` Steven Smith
2006-11-02 16:31 ` Ewan Mellor
2006-11-03 14:18 ` Markus Armbruster
2006-11-03 17:01 ` Steven Smith [this message]
2006-11-02 15:02 ` Markus Armbruster
2006-11-02 15:38 ` Ewan Mellor
2006-11-02 7:53 ` Markus Armbruster
2006-11-02 7:58 ` Keir Fraser
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=20061103170135.GA5457@cam.ac.uk \
--to=sos22-xen@srcf.ucam.org \
--cc=aliguori@mail.utexas.edu \
--cc=armbru@redhat.com \
--cc=ewan@xensource.com \
--cc=katzj@redhat.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 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.