From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 1/9] Update shim.config
Date: Thu, 18 Jan 2018 18:26:02 +0000 [thread overview]
Message-ID: <22985ed2-5c6c-0eb0-5245-23c67eac28c8@citrix.com> (raw)
In-Reply-To: <20180118181652.26397-2-wei.liu2@citrix.com>
On 18/01/18 18:16, Wei Liu wrote:
> To avoid having it changed every time the shim is built.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
One downside of having a this config in-tree is that it needs
regenerating every time the Kconfig logic changes.
OTOH, I did deliberately wire up all the config options, so
make -C tools/firmware/xen-dir shim-olddefconfig
or shim-menuconfig etc do work as expected.
Do we know why this line is disappearing? I presume it is some change
in the Kconfig logic, but I can't spot which changeset.
~Andrew
> ---
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> tools/firmware/xen-dir/shim.config | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/firmware/xen-dir/shim.config b/tools/firmware/xen-dir/shim.config
> index 78b965f4c7..d5bd516632 100644
> --- a/tools/firmware/xen-dir/shim.config
> +++ b/tools/firmware/xen-dir/shim.config
> @@ -68,7 +68,6 @@ CONFIG_HAS_EHCI=y
> CONFIG_HAS_CPUFREQ=y
> CONFIG_HAS_PASSTHROUGH=y
> CONFIG_HAS_PCI=y
> -# CONFIG_VGA is not set
> CONFIG_DEFCONFIG_LIST="$ARCH_DEFCONFIG"
> CONFIG_ARCH_SUPPORTS_INT128=y
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-18 18:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 18:16 [PATCH 0/9] Fix and improvements to pvshim Wei Liu
2018-01-18 18:16 ` [PATCH 1/9] Update shim.config Wei Liu
2018-01-18 18:26 ` Andrew Cooper [this message]
2018-01-18 18:28 ` Wei Liu
2018-01-18 18:30 ` Andrew Cooper
2018-01-19 10:16 ` Roger Pau Monné
2018-01-18 18:16 ` [PATCH 2/9] libxl: remove whitespaces introduced in 62982da926 Wei Liu
2018-01-19 10:18 ` Roger Pau Monné
2018-01-18 18:16 ` [PATCH 3/9] x86/guest: clean up guest/xen.h Wei Liu
2018-01-18 18:26 ` Andrew Cooper
2018-01-19 10:21 ` Roger Pau Monné
2018-01-19 12:22 ` Wei Liu
2018-01-19 12:29 ` Roger Pau Monné
2018-01-19 12:34 ` Wei Liu
2018-01-18 18:16 ` [PATCH 4/9] Remove sched=null from shim cmdline and doc Wei Liu
2018-01-18 18:27 ` Andrew Cooper
2018-01-19 10:28 ` Roger Pau Monné
2018-01-19 11:40 ` Wei Liu
2018-01-18 18:16 ` [PATCH 5/9] x86: relocate pvh_info Wei Liu
2018-01-19 10:07 ` Jan Beulich
2018-01-19 10:10 ` Andrew Cooper
2018-01-19 10:20 ` Jan Beulich
2018-01-19 10:53 ` Roger Pau Monné
2018-01-19 11:48 ` Jan Beulich
2018-01-18 18:16 ` [PATCH 6/9] Revert "x86/boot: Map more than the first 16MB" Wei Liu
2018-01-19 10:07 ` Jan Beulich
2018-01-18 18:16 ` [PATCH 7/9] libxl: lower shim related message to level info Wei Liu
2018-01-19 10:57 ` Roger Pau Monné
2018-01-18 18:16 ` [PATCH 8/9] xen/consoled: discard NUL from guest Wei Liu
2018-01-19 11:03 ` Roger Pau Monné
2018-01-19 15:25 ` Wei Liu
2018-01-18 18:16 ` [PATCH 9/9] x86/shim: pass through vcpu runstate to L0 Xen Wei Liu
2018-01-19 11:18 ` Roger Pau Monné
2018-01-19 15:18 ` Wei Liu
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=22985ed2-5c6c-0eb0-5245-23c67eac28c8@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--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 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.