xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [RFC v1] x86, platform, xen, kconfig: add xen	defconfig helpers
Date: Sat, 7 Jun 2014 00:41:15 +0200	[thread overview]
Message-ID: <20140606224115.GJ22052@wotan.suse.de> (raw)
In-Reply-To: <53903BED.3070407@citrix.com>

On Thu, Jun 05, 2014 at 10:44:13AM +0100, David Vrabel wrote:
> On 05/06/14 01:48, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@suse.com>
> > 
> > Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
> > ---
> > 
> > Hey folks, shiny kvm has a shortcut 'make kvmconfig' on the
> > kernel, and I thought this was a good idea so wanted to add a
> > respective helper for xen. Contrary to kvm though we can have
> > a dom0 and a guest kernel configuration. As it is right now this
> > patch bundles the same exact options for both, but figured
> > folks might already have special configs for both different
> > types. What options would we want as default *upstream* for each
> > of these ?
> 
> This looks like a good idea but I would only have one Xen option.  There
> are so few options that only apply to dom0 that it doesn't make sense to
> have a dom0 option.

OK thanks for the feedback I've merged them.

> > --- /dev/null
> > +++ b/arch/x86/configs/xen_dom0.config
> 
> Make this xen.config

Done.

> > @@ -0,0 +1,37 @@
> > +CONFIG_XEN=y
> > +CONFIG_XEN_DOM0=y
> > +CONFIG_XEN_PVHVM=y
> > +CONFIG_XEN_MAX_DOMAIN_MEMORY=500
> > +CONFIG_XEN_SAVE_RESTORE=y
> > +# CONFIG_XEN_DEBUG_FS is not set
> > +CONFIG_XEN_PVH=y
> > +CONFIG_PCI_XEN=y
> > +CONFIG_XEN_PCIDEV_FRONTEND=m
> > +CONFIG_XEN_BLKDEV_FRONTEND=m
> > +CONFIG_XEN_BLKDEV_BACKEND=m
> > +CONFIG_NETXEN_NIC=m
> 
> Remove this as it isn't a Xen related option, but an ethernet driver.

OK.

> > +CONFIG_XEN_NETDEV_FRONTEND=m
> > +CONFIG_XEN_NETDEV_BACKEND=m
> > +CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y
> > +CONFIG_HVC_XEN=y
> > +CONFIG_HVC_XEN_FRONTEND=y
> > +# CONFIG_TCG_XEN is not set
> 
> Enable as a module.

Done.

  Luis

  parent reply	other threads:[~2014-06-06 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  0:48 [RFC v1] x86, platform, xen, kconfig: add xen defconfig helpers Luis R. Rodriguez
2014-06-05  9:44 ` David Vrabel
2014-06-06  9:56   ` Ian Campbell
2014-06-06 18:49     ` Luis R. Rodriguez
2014-06-09  8:45       ` Ian Campbell
2014-06-06 22:41   ` Luis R. Rodriguez [this message]
2014-06-05 17:14 ` Konrad Rzeszutek Wilk
2014-06-06 22:38   ` Luis R. Rodriguez

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=20140606224115.GJ22052@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=mcgrof@do-not-panic.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).