xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: [HACKATHON] libxl refactoring session note
Date: Wed, 20 Apr 2016 18:35:36 +0100	[thread overview]
Message-ID: <20160420173536.GD11151@citrix.com> (raw)

* Auto generate device handling routines

Libxl has a lot of PV drivers. And the number is  increasing at the moment.

GlobalLogic has some customised drivers. The code plumbing is painful.

Libxl already has IDL to describe the device interface and uses
scripts to generate a lot of files.

Propose to auto-generate device handling routines.

All: Good idea.

* Allow to mark some devices non-critical

You might want domain creation continues even if some devices fail to
initialise. Example: a guest can continue to function without a sound
card.

Ian: Classify devices as critical and non-critical. Add a field in
IDL. All devices critical by default.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

                 reply	other threads:[~2016-04-20 17:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160420173536.GD11151@citrix.com \
    --to=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 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).