From: Juergen Gross <jgross@suse.com>
To: minios-devel@lists.xenproject.org, xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
	samuel.thibault@ens-lyon.org, wei.liu2@citrix.com
Subject: [PATCH 0/2] mini-os: repair stubdom build
Date: Mon, 29 Aug 2016 13:01:07 +0200	[thread overview]
Message-ID: <1472468469-11560-1-git-send-email-jgross@suse.com> (raw)
The patch series adding HVMlite support for Mini-OS unfortunately
broke building Xen's stubdoms. This small series repairs the broken
bits again.
Please note that there is still some action required in Xen:
ioemu and grub stubdom minios.cfg files need CONFIG_KEEP_STARTINFO=y
to be added. I'm sending out a patch for Xen to do this in parallel.
Juergen Gross (2):
  mini-os: support keeping start_info structure conditionally
  mini-os: don't get xenbus parameters if xenbus is disabled
 Config.mk            |  2 ++
 arch/x86/setup.c     | 12 ++++++++++++
 include/hypervisor.h | 13 +++++++++++++
 include/xenbus.h     |  5 ++++-
 4 files changed, 31 insertions(+), 1 deletion(-)
-- 
2.6.6
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next             reply	other threads:[~2016-08-29 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 11:01 Juergen Gross [this message]
2016-08-29 11:01 ` [PATCH 1/2] mini-os: support keeping start_info structure conditionally Juergen Gross
2016-08-29 11:09   ` Wei Liu
2016-08-29 11:17     ` [Minios-devel] " Juergen Gross
2016-08-29 11:47       ` Andrew Cooper
2016-08-29 12:28         ` Juergen Gross
2016-08-29 12:32           ` Andrew Cooper
2016-08-29 13:09             ` Juergen Gross
2016-08-29 12:03       ` Wei Liu
2016-08-29 11:01 ` [PATCH 2/2] mini-os: don't get xenbus parameters if xenbus is disabled Juergen Gross
2016-08-29 11:11   ` Wei Liu
2016-08-29 20:42     ` Samuel Thibault
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=1472468469-11560-1-git-send-email-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=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).